@postman-cse/onboarding-bootstrap 2.1.1 → 2.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -0
- package/dist/action.cjs +393 -175
- package/dist/cli.cjs +411 -193
- package/dist/index.cjs +393 -175
- package/package.json +6 -5
package/README.md
CHANGED
|
@@ -6,6 +6,8 @@ Provisions a [Postman workspace](https://learning.postman.com/docs/collaborating
|
|
|
6
6
|
|
|
7
7
|
Part of the [Postman API Onboarding suite](https://github.com/postman-cs/postman-api-onboarding-action).
|
|
8
8
|
|
|
9
|
+
> **Standards-grounded assertion generation.** Every collection this action generates ships with executable contract tests compiled from your spec: JSON Schema (draft-07 / 2020-12) body validation with RFC-checked formats (RFC 3339 timestamps, RFC 4122 UUIDs, RFC 3986 URIs, and more), RFC 9110 `Authorization` scheme checks plus status-code requirement checks (`WWW-Authenticate` on 401, `Allow` on 405, no body on 304, `Content-Range` on 206), RFC 9457 `application/problem+json` error-body validation with RFC 8259 encoding and RFC 8288 `Link` checks, canonical proto3 JSON well-known-type validation for gRPC, version-aware SOAP 1.1/1.2 media-type and Fault-status checks, and GraphQL-over-HTTP media-type/status discipline. The full test inventory and the standard behind each check: [Generated assertions](docs/generated-assertions.md).
|
|
10
|
+
|
|
9
11
|
## Which action should I use?
|
|
10
12
|
|
|
11
13
|
| Need | Use |
|
|
@@ -303,6 +305,8 @@ Before any durable contract collection is overwritten, the action hardens the ge
|
|
|
303
305
|
|
|
304
306
|
Full pipeline, validation scope, OpenAPI semantics, limits, and rollback behavior are documented in [Dynamic Contract Tests](docs/dynamic-contract-tests.md).
|
|
305
307
|
|
|
308
|
+
The user-facing inventory of everything above — the exact test names per protocol, the RFC or specification each check enforces, and what to do when one fails — is in [Generated Assertions](docs/generated-assertions.md).
|
|
309
|
+
|
|
306
310
|
## Errors
|
|
307
311
|
|
|
308
312
|
Dynamic contract failures and warnings use `CONTRACT_` error codes. Remediation guidance for each code:
|