[Bug]: Release action doesn't bump versions package versions in npm workspace

[th0r]

Would you like to work on a fix?

• Check this if you would like to implement a PR, we are more than happy to help you go through the process.

Current and expected behavior

I have an npm workspace with multiple packages stored under packages directory. Let's say there is a foo package there with version 1.0.0.

Here is my .simple-release.json config:

{
  "project": [
    "@simple-release/npm#NpmWorkspacesProject",
    {
      "mode": "independent"
    }
  ],
  "publish": {
    "skip": true
  },
  "bump": {
    "extraScopes": ["deps", "dev-deps"]
  }
}

When I push the following commit to the master fix(foo) blah blah simple-release-action creates a release PR with a proper changelog item, but doesn't bump foo's version to 1.0.1 neither in the changelog nor in the foo's package.json.

Reproduction

package version

Latest v1

Possible solution

No response

[dangreen]

Thanks for the report.

I can't reliably reproduce this from the current description alone. In independent monorepo mode, fix(foo): ... should bump the package whose resolved release scope is foo, so we need a bit more context to understand where it diverges in your repository.

Could you please provide a minimal reproduction repository, or at least:

• root package.json with the workspaces field;
• packages/foo/package.json;
• the exact workflow file using simple-release-action;
• the full release PR diff generated by the action;
• the existing git tags before the action runs, especially whether foo@1.0.0 exists;
• the exact commit message, including body/footer;
• the exact action ref/version you use.

Also, if your workspace config uses globs like "packages/*", please mention that explicitly.