de
Default
GitHub
nxext
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
main
Runs and Agents
Configuration
Self-Healing CI
Project Graph
Circular Dependencies
Enterprise
Resource Usage
Analysis
Conformance
Enterprise
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
fix(release): restore 23.0.0 baseline after git-tag/npm desync The release job's first successful run in months resolved "current version" from stale git tags (stencil@20.1.0 etc.) instead of the already-published npm state (21.0.0) or the manifest (23.0.0, set manually during the Nx 23 upgrade but never tagged/published). It bumped all 9 packages down to ~20.x/21.x and pushed that to npm's latest tag, a real regression for consumers. Immediate npm dist-tags were already reverted to 21.0.0 by hand. This restores package.json versions (and inter-package @nxext/* deps) to 23.0.0 across all 9 packages, and drops the changelog entries generated for the bad versions. A follow-up commit tags this commit pkg@23.0.0 for each project so nx release's git-tag resolver has a correct baseline going forward.
nx affected --target build lint test e2e
⌘K
Succeeded
nx affected --target build lint test e2e
Click to copy
01a5b03c
main
81%
Cache hits
35 of 43 tasks used cache.
Protect cache integrity with sandboxing
63%
Distribution saved time
6m 12s instead of 16m 50s.
GitHub
nxext
Workspace