Newly added packages update all issues and prs in the history #7
Description
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
See dhoulb/multi-semantic-release#90
See qiwi/multi-semantic-release#82
See dhoulb/multi-semantic-release#41
Minimal reproduction code
No response
Additional Context
No response
Environment Info
System:
OS: Linux 6.1 EndeavourOS
CPU: (16) x64 AMD Ryzen 7 7700X 8-Core Processor
Memory: 4.47 GB / 30.51 GB
Container: Yes
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 20.6.1 - ~/.nvm/versions/node/v20.6.1/bin/node
npm: 9.8.1 - ~/.nvm/versions/node/v20.6.1/bin/npm
pnpm: 8.8.0 - ~/.nvm/versions/node/v20.6.1/bin/pnpm
npmPackages:
@semantic-release/changelog: ^6.0.3 => 6.0.3
@semantic-release/git: ^10.0.1 => 10.0.1
@semantic-release/github: ^9.2.0 => 9.2.0
@semantic-release/npm: ^11.0.0 => 11.0.0
semantic-release: ^22.0.5 => 22.0.5Which module system do you use?
- CJS
- ESM
Used Package Manager
pnpm