ci: use corrected trusted npm publisher (QQQ #915) #46

Merged
KofTwentyTwo merged 2 commits from feature/GH-915-publisher-pin into develop 2026-09-29 20:22:10 +00:00
2 changed files with 2 additions and 2 deletions

No files matched your search

+1 -1
View File
@@ -3,7 +3,7 @@
version: 2.1
orbs:
qqq-orb: kingsrook/qqq-orb@0.6.7
qqq-orb: kingsrook/qqq-orb@0.6.8
workflows:
+1 -1
View File
@@ -1,6 +1,6 @@
# 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.
CircleCI publishes `@qrunio/qqq-frontend-core` with npm Trusted Publishing using `kingsrook/qqq-orb@0.6.8` 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 |
| --- | --- |