`nx run workspace:version` does not generate changelog
See original GitHub issueRunning nx run workspace:version does not generate changelog or updates the package.json files inside the repo.
If I delete https://github.com/jscutlery/semver/blob/main/packages/semver/src/executors/version/version.ts#L34 till https://github.com/jscutlery/semver/blob/main/packages/semver/src/executors/version/version.ts#L45 it works as expected.
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (11 by maintainers)
Top Results From Across the Web
jscutlery/semver: Nx plugin to automate semantic ... - GitHub
Nx plugin to automate semantic versioning and CHANGELOG generation. ... This way you release only what you want and consumers don't get updates...
Read more >@nrwl/workspace | Nx
Running nx g @nrwl/nx-plugin:plugin feature will create a local plugin with a generator which is written the same way generators are written for...
Read more >Using Nx Workspace generators to scaffold new blog posts
As you can see, Nx generators not only scaffold files but are able to generate entire folder structures, register new Nx libraries or...
Read more >Setting Up A DevOps Pipeline With Nx - Christian Lüdemann
Nx is a build system with best-in-class support for monorepos. ... instant as Nx will detect that there is no change between the...
Read more >Getting Started with Monorepo with Nx Nrwl - Rupesh Tiwari
This will solve the problem and you will not have many Git projects ... In order to create your first Nx Monorepo workspace...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

This issues happens again in the latest release. Can we reopen @edbzn?
@edbzn I indeed was the latest version
2.23.4, rolling back to2.22.0solved it.