Coordination
Closed this issue · 5 comments
Pre-Checks
- Follow our Code of Conduct.
- Read the Contributing Guidelines.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Make sure this is a multi-semantic-release issue and not related to a combination with another package.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion.
- The provided reproduction is a minimal reproducible example of the bug.
- I am willing to provide a PR.
Describe the bug
Hi,
In my monorepos I have two sub package and I want them to be coodinated on their versionning, unfortunately this is not the case see the example below:
Also why it always make a new release like 1.1.0-rec.17 => 1.1.0-rec.18 instead of changing the semver version ?
Can anyone help me with this ?
Thank you
Minimal reproduction code
No response
Additional Context
No response
Environment Info
System:
OS: Linux 6.2 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
CPU: (8) x64 Intel(R) Core(TM) i5-10310U CPU @ 1.70GHz
Memory: 51.67 GB / 62.57 GB
Container: Yes
Shell: 5.1.4 - /bin/bash
Binaries:
Node: 18.18.0 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 10.2.0 - /workspaces/rl-idle/node_modules/.bin/npm
pnpm: 8.8.0 - /usr/local/share/npm-global/bin/pnpm
bun: 1.0.7 - ~/.bun/bin/bun
Monorepos:
Yarn Workspaces: 1.22.19
npmPackages:
@semantic-release/changelog: ^6.0.3 => 6.0.3
@semantic-release/commit-analyzer: ^11.0.0 => 11.0.0
@semantic-release/git: ^10.0.1 => 10.0.1
@semantic-release/github: ^9.0.4 => 9.2.1
@semantic-release/npm: ^11.0.0 => 11.0.1
@semantic-release/release-notes-generator: ^12.0.0 => 12.0.1
semantic-release: ^22.0.5 => 22.0.7
Which module system do you use?
- CJS
- ESM
Used Package Manager
npm
Awesome! Thank you for taking the time to create your first issue!
Could you post you repo, semantic-config file and your pipeline?
Yes there is it: https://github.com/rl-IDLE/rl-idle
Im sorry, but i cant find any branch or code that use @anolilab/multi-semantic-release
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using our GitHub Discussions tab for questions.