fix(ci): publish npm packages with CircleCI OIDC #44

Merged
KofTwentyTwo merged 2 commits from feature/GH-912-npm-trusted-publishing into develop 2026-09-29 19:52:15 +00:00
3 changed files with 25 additions and 2 deletions

No files matched your search

+12 -1
View File
@@ -3,13 +3,14 @@
version: 2.1
orbs:
qqq-orb: kingsrook/qqq-orb@0.6
qqq-orb: kingsrook/qqq-orb@0.6.7
workflows:
test_only:
jobs:
- qqq-orb/node_test_only:
node_version: "24.21"
context: [qqq-maven-registry-credentials, build-qqq-sample-app]
filters:
branches:
@@ -20,6 +21,8 @@ workflows:
publish_snapshot:
jobs:
- qqq-orb/node_publish:
node_version: "24.21"
npm_trusted_publishing: true
context: [qqq-maven-registry-credentials, build-qqq-sample-app]
branch_type: snapshot
filters:
@@ -30,6 +33,8 @@ workflows:
publish_feature:
jobs:
- qqq-orb/node_publish:
node_version: "24.21"
npm_trusted_publishing: true
context: [qqq-maven-registry-credentials, build-qqq-sample-app]
branch_type: feature
filters:
@@ -42,6 +47,8 @@ workflows:
publish_release_candidate:
jobs:
- qqq-orb/node_publish:
node_version: "24.21"
npm_trusted_publishing: true
context: [qqq-maven-registry-credentials, build-qqq-sample-app]
branch_type: release_candidate
filters:
@@ -52,6 +59,8 @@ workflows:
publish_release:
jobs:
- qqq-orb/node_publish:
node_version: "24.21"
npm_trusted_publishing: true
context: [qqq-maven-registry-credentials, build-qqq-sample-app]
branch_type: release
filters:
@@ -63,6 +72,8 @@ workflows:
publish_hotfix_release:
jobs:
- qqq-orb/node_publish:
node_version: "24.21"
npm_trusted_publishing: true
context: [qqq-maven-registry-credentials, build-qqq-sample-app]
branch_type: hotfix
filters:
+12
View File
@@ -0,0 +1,12 @@
# npm publishing
CircleCI publishes `@qrunio/qqq-frontend-core` with npm Trusted Publishing using `kingsrook/qqq-orb@0.6.7` and `cimg/node:24.21`. In the package Settings on npmjs.com, add a **CircleCI** trusted publisher with the values below and explicitly allow **npm publish** (the staged-only default does not run this pipeline). Existing workflow branch filters and dist-tags remain in place.
| npm field | Value |
| --- | --- |
| Organization ID | `bb329fea-03cd-4fb5-b530-15e85703598d` |
| Project ID | `5bd1e544-282a-4080-afc1-36ffdebf5487` |
| Pipeline definition ID | `3bd87740-26e6-5f18-8600-10685a13a81e` |
| VCS origin | `github.com/QRun-IO/qqq-frontend-core` |
These are public identifiers, not credentials. The job obtains a short-lived npm-audience OIDC identity only for publication, so no new `NPM_TOKEN` is needed. Do not use `npm whoami` or a publish dry run as proof: verify the real immutable version at npm and install it in a clean consumer. Once that succeeds, remove obsolete token access only after checking its other consumers. CircleCI Trusted Publishing currently does not attach npm provenance attestations. See [npm documentation](https://docs.npmjs.com/trusted-publishers/).
+1 -1
View File
@@ -27,7 +27,7 @@
"license": "ISC",
"repository": {
"type": "git",
"url": "https://github.com/Kingsrook/qqq-frontend-core"
"url": "https://github.com/QRun-IO/qqq-frontend-core"
},
"publishConfig": {
"registry": "https://registry.npmjs.org/"