Repository navigation
ci: publish packages via nx release and npm trusted publishing - #288
Open
ChristopherPHolder wants to merge 2 commits into
Open
ChristopherPHolder wants to merge 2 commits into
ChristopherPHolder wants to merge 2 commits into
Conversation
npm revoked the classic NPM_TOKEN, so cli 0.21.2/0.21.3 and nx-plugin 0.1.5
were tagged but never published. Replace @jscutlery/semver + ngx-deploy-npm
with nx release (independent versioning, existing {projectName}-{version} tags)
and split release/publish workflows: release versions, tags and creates GitHub
releases as the PushBased bot app; publish runs on the pushed tags and
publishes to npm via OIDC trusted publishing from the release environment.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The cli-e2e global setup publishes the cli to verdaccio via the cli:publish target and tools/scripts/publish.mjs.
ChristopherPHolder
force-pushed
the
fix-release-publishing
branch
from
October 21, 2026 18:52
2700a68 to
6a5ad06
Compare
❗❗❗ report generated by this PR ❗❗❗☕ Order Coffee ☕Date/Time: 2026-10-21 18:54
|
☕ Order Coffee ☕Date/Time: 2026-10-21 18:54
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The release workflow has been failing since npm revoked classic tokens: our
NPM_TOKEN(from 2022) no longer works.cli-0.21.2,cli-0.21.3andnx-plugin-0.1.5were tagged on GitHub but never reached npm (npm still has@push-based/user-flow@0.21.1and@push-based/user-flow-nx-plugin@0.1.4).What
Follows the PushBased package publishing setup (same as
zod2nx-schema):@jscutlery/semver+ngx-deploy-npmcliandnx-plugin{projectName}-{version}tag pattern, so versions resolve from current tagsCHANGELOG.md+ GitHub releaserelease.yml(push tomain): build, test, thennx release --skip-publishas the PushBased bot app (commits, tags, pushes, creates GitHub releases)publish.yml(oncli-*/nx-plugin-*tags, or manual):nx release publishvia npm trusted publishing (OIDC). No npm token. Runs on Node 24 because OIDC needs npm ≥ 11.5.1. Versions already on npm are skipped.repositoryto the nx-pluginpackage.json(npm provenance requires it)version/githubtargets and the@jscutlery/semver/ngx-deploy-npmdepsDry-run with #287's
fix:commit on top:cli→ 0.21.4,nx-plugin→ 0.1.6 (dependent bump). The first publish also catches upnx-plugin.Required repo / npm setup before merging
releaseenvironment with variableGH_APP_ID=2781189and secretGH_APP_PRIVATE_KEY@push-based/user-flowand@push-based/user-flow-nx-plugin: orgpush-based, repouser-flow, workflowpublish.yml, environmentreleaseNPM_TOKENrepo secret