@postman-cse/onboarding-repo-sync 1.0.2 → 1.0.3

package/README.md

@@ -1,9 +1,11 @@
-# Postman Repo Sync
+# Postman Onboarding: Repo Sync
 
-[![CI](https://github.com/postman-cs/postman-repo-sync-action/actions/workflows/ci.yml/badge.svg)](https://github.com/postman-cs/postman-repo-sync-action/actions/workflows/ci.yml) [![Release](https://img.shields.io/github/v/release/postman-cs/postman-repo-sync-action?sort=semver)](https://github.com/postman-cs/postman-repo-sync-action/releases) [![npm](https://img.shields.io/npm/v/%40postman-cse%2Fonboarding-repo-sync)](https://www.npmjs.com/package/@postman-cse/onboarding-repo-sync) [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) [![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/postman-cs/postman-repo-sync-action/badge)](https://scorecard.dev/viewer/?uri=github.com/postman-cs/postman-repo-sync-action)
+[![CI](https://github.com/postman-cs/postman-repo-sync-action/actions/workflows/ci.yml/badge.svg)](https://github.com/postman-cs/postman-repo-sync-action/actions/workflows/ci.yml) [![Release](https://img.shields.io/github/v/release/postman-cs/postman-repo-sync-action?sort=semver)](https://github.com/postman-cs/postman-repo-sync-action/releases) [![npm](https://img.shields.io/npm/v/%40postman-cse%2Fonboarding-repo-sync)](https://www.npmjs.com/package/@postman-cse/onboarding-repo-sync) [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 
 Exports Postman collections and environments into your repository and wires CI, mocks, and monitors around them.
 
+Part of the [Postman API Onboarding suite](https://github.com/postman-cs/postman-api-onboarding-action).
+
 ## Usage
 
 ```yaml
@@ -202,6 +204,18 @@ Deeper reference:
 
 ## Resources
 
+### The suite
+
+| Action | Role |
+| --- | --- |
+| [Postman API Onboarding](https://github.com/postman-cs/postman-api-onboarding-action) | Entry point: chains workspace bootstrap, repo sync, and optional Insights linking |
+| [Postman Onboarding: Service Token](https://github.com/postman-cs/postman-resolve-service-token-action) | Mints the service-account access token and team ID |
+| [Postman Onboarding: AWS Spec Discovery](https://github.com/postman-cs/postman-aws-spec-discovery-action) | Discovers and exports API specs from AWS services |
+| [Postman Onboarding: Workspace Bootstrap](https://github.com/postman-cs/postman-bootstrap-action) | Creates the workspace, uploads the spec, generates collections |
+| [Postman Onboarding: Smoke Flow](https://github.com/postman-cs/postman-smoke-flow-action) | Applies a curated flow.yaml to the Smoke collection |
+| [Postman Onboarding: Repo Sync](https://github.com/postman-cs/postman-repo-sync-action) | Exports artifacts into the repo and wires CI, mocks, and monitors |
+| [Postman Onboarding: Insights Linking](https://github.com/postman-cs/postman-insights-onboarding-action) | Links Insights discovered services to the workspace |
+
 - [postman-resolve-service-token-action](https://github.com/postman-cs/postman-resolve-service-token-action): mints a service-account access token and team ID.
 - [postman-api-onboarding-action](https://github.com/postman-cs/postman-api-onboarding-action): composite action that orchestrates the onboarding pipeline.
 - [postman-bootstrap-action](https://github.com/postman-cs/postman-bootstrap-action): workspace provisioning, spec upload, and collection generation.

package/action.yml

@@ -1,5 +1,5 @@
-name: Postman Repo Sync
-description: Export Postman collections and environments into your repo and wire CI, mocks, and monitors around them.
+name: 'Postman Onboarding: Repo Sync'
+description: Export Postman collections and environments into your repo with CI wiring. Part of the Postman API Onboarding suite.
 author: Postman
 branding:
   icon: refresh-cw

package/dist/action.cjs

@@ -25414,8 +25414,10 @@ var PostmanAssetsClient = class {
    * Monitor and mock creation reference a collection that may have been
    * created moments earlier; the Postman backend is eventually consistent
    * and can reject the reference with a 400 "Unable to load collection"
-   * until the collection becomes visible. Retry that specific 400 plus
-   * generic transient statuses with backoff.
+   * until the collection becomes visible. Retry only that specific 400 and
+   * 429 throttling: both guarantee nothing was created. A 5xx on these
+   * non-idempotent creates is ambiguous (the asset may exist server-side),
+   * so it is not retried to avoid duplicate mocks and monitors.
    */
   async requestWithCollectionRetry(path8, init) {
     return retry(() => this.request(path8, init), {
@@ -25428,7 +25430,7 @@ var PostmanAssetsClient = class {
         if (!(error2 instanceof HttpError)) {
           return false;
         }
-        if (error2.status >= 500 || error2.status === 429) {
+        if (error2.status === 429) {
           return true;
         }
         return error2.status === 400 && /unable to load collection/i.test(error2.responseBody);

package/dist/cli.cjs

@@ -23517,8 +23517,10 @@ var PostmanAssetsClient = class {
    * Monitor and mock creation reference a collection that may have been
    * created moments earlier; the Postman backend is eventually consistent
    * and can reject the reference with a 400 "Unable to load collection"
-   * until the collection becomes visible. Retry that specific 400 plus
-   * generic transient statuses with backoff.
+   * until the collection becomes visible. Retry only that specific 400 and
+   * 429 throttling: both guarantee nothing was created. A 5xx on these
+   * non-idempotent creates is ambiguous (the asset may exist server-side),
+   * so it is not retried to avoid duplicate mocks and monitors.
    */
   async requestWithCollectionRetry(path4, init) {
     return retry(() => this.request(path4, init), {
@@ -23531,7 +23533,7 @@ var PostmanAssetsClient = class {
         if (!(error instanceof HttpError)) {
           return false;
         }
-        if (error.status >= 500 || error.status === 429) {
+        if (error.status === 429) {
           return true;
         }
         return error.status === 400 && /unable to load collection/i.test(error.responseBody);

package/dist/index.cjs

@@ -25429,8 +25429,10 @@ var PostmanAssetsClient = class {
    * Monitor and mock creation reference a collection that may have been
    * created moments earlier; the Postman backend is eventually consistent
    * and can reject the reference with a 400 "Unable to load collection"
-   * until the collection becomes visible. Retry that specific 400 plus
-   * generic transient statuses with backoff.
+   * until the collection becomes visible. Retry only that specific 400 and
+   * 429 throttling: both guarantee nothing was created. A 5xx on these
+   * non-idempotent creates is ambiguous (the asset may exist server-side),
+   * so it is not retried to avoid duplicate mocks and monitors.
    */
   async requestWithCollectionRetry(path8, init) {
     return retry(() => this.request(path8, init), {
@@ -25443,7 +25445,7 @@ var PostmanAssetsClient = class {
         if (!(error2 instanceof HttpError)) {
           return false;
         }
-        if (error2.status >= 500 || error2.status === 429) {
+        if (error2.status === 429) {
           return true;
         }
         return error2.status === 400 && /unable to load collection/i.test(error2.responseBody);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@postman-cse/onboarding-repo-sync",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "Public customer preview Postman repo sync GitHub Action.",
   "type": "module",
   "main": "dist/index.cjs",