@postman-cse/onboarding-insights 0.8.0 → 0.9.1

package/README.md

@@ -29,7 +29,7 @@ jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
 
       # ... deploy your service to Kubernetes ...
 
@@ -52,7 +52,7 @@ jobs:
   provision:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
 
       - uses: postman-cs/postman-bootstrap-action@v0
         id: bootstrap
@@ -122,7 +122,7 @@ Output is JSON to stdout. Use `--result-json` to write the same payload to a fil
 
 ```yaml
 onboarding:
-  image: node:20
+  image: node:24
   script:
     - npm install -g postman-insights-onboarding-action
     - postman-insights-onboard --project-name af-cards-activation --workspace-id "$WORKSPACE_ID" --environment-id "$ENVIRONMENT_ID" --postman-access-token "$POSTMAN_ACCESS_TOKEN" --postman-api-key "$POSTMAN_API_KEY" --cluster-name "$CLUSTER_NAME" --repo-url "$CI_PROJECT_URL" --poll-timeout-seconds 180 --result-json insights-result.json --dotenv-path insights.env
@@ -131,7 +131,7 @@ onboarding:
 ### Bitbucket Pipelines
 
 ```yaml
-image: node:20
+image: node:24
 
 pipelines:
   default:
@@ -150,7 +150,7 @@ pool:
 steps:
   - task: NodeTool@0
     inputs:
-      versionSpec: '20.x'
+      versionSpec: '24.x'
   - script: |
       npm install -g postman-insights-onboarding-action
       postman-insights-onboard --project-name af-cards-activation --workspace-id "$(WORKSPACE_ID)" --environment-id "$(ENVIRONMENT_ID)" --postman-access-token "$(POSTMAN_ACCESS_TOKEN)" --postman-api-key "$(POSTMAN_API_KEY)" --cluster-name "$(CLUSTER_NAME)" --repo-url "$(BUILD_REPOSITORY_URI)" --poll-timeout-seconds 180 --result-json insights-result.json --dotenv-path insights.env
@@ -167,7 +167,7 @@ steps:
 | `system-environment-id` | No | | Postman system environment UUID for service-level Insights acknowledgment. Falls back to the value from the discovered service record. |
 | `cluster-name` | No | | Insights cluster name. When set, the action matches `{cluster-name}/{project-name}` exactly. When omitted, falls back to suffix matching. |
 | `repo-url` | No | Auto-detected from CI when available | Repository URL used for Git onboarding. |
-| `postman-access-token` | Yes | | Postman session token for Bifrost API calls. See [Obtaining postman-access-token](#obtaining-postman-access-token-open-alpha). |
+| `postman-access-token` | Yes | | Postman session token for Bifrost API calls. See [Obtaining postman-access-token](#obtaining-postman-access-token-customer-preview). |
 | `postman-team-id` | No | | Explicit Postman team ID for org-mode Bifrost requests. When omitted, the action leaves `x-entity-team-id` unset so Bifrost resolves team context from the access token. |
 | `github-token` | No | ambient `GITHUB_TOKEN` env when exported by the workflow | Optional GitHub token passed as `git_api_key` only when repository auth is required by the onboarding endpoint. |
 | `postman-api-key` | No | | Postman API key (`PMAK-*`) for the application binding call to the observability API. Auto-created from `postman-access-token` when omitted or invalid after a clear 401/403 validation failure. |
@@ -178,9 +178,9 @@ Supply `postman-team-id` only for org-mode tokens that require an explicit team
 
 If `postman-api-key` is omitted or the `/me` validation call returns `401` or `403`, the action creates a new API key via the Bifrost identity service using the `postman-access-token`. Network failures and unexpected validation responses fail the action instead of silently rotating credentials.
 
-### Obtaining `postman-access-token` (Open Alpha)
+### Obtaining `postman-access-token` (Customer Preview)
 
-> **Open-alpha limitation:** The `postman-access-token` input requires a manually-extracted session token. There is currently no public API to exchange a Postman API key (PMAK) for an access token programmatically. This manual step will be eliminated before GA.
+> **Customer Preview limitation:** The `postman-access-token` input requires a manually-extracted session token. There is currently no public API to exchange a Postman API key (PMAK) for an access token programmatically. This manual step will be eliminated before GA.
 
 The `postman-access-token` is a Postman session token (`x-access-token`) required for the Bifrost API Catalog onboarding endpoints. Without it, this action cannot function.
 
@@ -259,8 +259,8 @@ npm run build
 
 `npm run build` produces `dist/index.cjs`, the bundled action entrypoint referenced by `action.yml`.
 
-## Open-Alpha Release Strategy
+## Customer Preview Release Strategy
 
-- Open-alpha channel tags use `v0.x.y`.
+- Customer Preview channel tags use `v0.x.y`.
 - Consumers can pin immutable tags such as `v0.1.0` for reproducibility.
-- Moving tag `v0` is used as the rolling open-alpha channel.
+- Moving tag `v0` is used as the rolling customer preview channel.

package/action.yml

@@ -39,6 +39,10 @@ inputs:
     description: 'Seconds between discovery polling attempts'
     required: false
     default: '10'
+  postman-stack:
+    description: 'Postman stack profile.'
+    required: false
+    default: 'prod'
 outputs:
   discovered-service-id:
     description: 'Numeric ID from the API Catalog discovered-services list'
@@ -53,5 +57,5 @@ outputs:
   status:
     description: 'Onboarding result: success, not-found, or error'
 runs:
-  using: 'node20'
-  main: 'dist/index.cjs'
+  using: 'node24'
+  main: 'dist/action.cjs'