You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a workflow which takes a comma separated list of projects and a version specifier to manually release libraries, using the following nx commands:
However I get the following output when I provide "styles", which doesn’t identify it has generated a new version to release. Running it again will recognise "1.6.0" hasn't been published yet and continues to publish it to a private npm repo.
NX Your filter "styles" matched the following projects:
- styles
NX Running release version for project: styles
styles 🔍 Reading data for package "@(repo)/styles" from libs/styles/package.json
styles 📄 Resolved the current version as 1.5.0 from git tag "[email protected]".
styles 📄 Using the provided version specifier "minor".
styles ✍️ New version 1.6.0 written to libs/styles/package.json
UPDATE libs/styles/package.json
"name": "@(repo)/styles",
- "version": "1.5.0",
+ "version": "1.6.0",
"peerDependencies": {
NX Staging changed files with git
NX Committing changes with git
NX Tagging commit with git
NX Pushing to git remote "origin"
NX Creating GitHub Release
CREATE https://github.com/(repo)/common-ui/releases/tag/[email protected]
+ ## 1.6.0 (2025-02-25)
+
+ This was a version bump only for styles to align it with other projects, there were no code changes.
NX Skipped publishing packages.
NX Your filter "styles" matched the following projects:
- styles
NX Running target nx-release-publish for project styles:
- styles
> nx run styles:nx-release-publish
styles: Skipped package "@(repo)/styles" from project "styles" because v1.5.0 already exists in https://npm.pkg.github.com/ with tag "latest"
NX Successfully ran target nx-release-publish for project styles
Expected Behavior
I expect the command "nx run styles:nx-release-publish" to identify that v1.6.0 has just been released and to publish it correctly.
Current Behavior
I have a workflow which takes a comma separated list of projects and a version specifier to manually release libraries, using the following nx commands:
However I get the following output when I provide "styles", which doesn’t identify it has generated a new version to release. Running it again will recognise "1.6.0" hasn't been published yet and continues to publish it to a private npm repo.
Expected Behavior
I expect the command "nx run styles:nx-release-publish" to identify that v1.6.0 has just been released and to publish it correctly.
GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
Package Manager Version
pnpm 10.4.1
Operating System
Additional Information
My nx.json config:
The text was updated successfully, but these errors were encountered: