wayback
wayback copied to clipboard
chore(deps): update semantic-release monorepo
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| @semantic-release/npm | 11.0.2 -> 11.0.3 |
||||
| semantic-release | 23.0.2 -> 23.1.1 |
Release Notes
semantic-release/npm (@semantic-release/npm)
v11.0.3
Bug Fixes
- deps: raised the minimum accepted range of npm to v10.5.0 (#759) (a0313f8), closes semantic-release/semantic-release#3202
even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully
semantic-release/semantic-release (semantic-release)
v23.1.1
v23.1.0
v23.0.8
Bug Fixes
- deps: rename read-pkg-up -> read-package-up (4980cba)
- deps: rename read-pkg-up -> read-package-up (#3249) (95a8b9e)
v23.0.7
v23.0.6
Bug Fixes
- deps: update dependency @semantic-release/release-notes-generator to v13 (#3237) (b7e08fc)
v23.0.5
v23.0.4
v23.0.3
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Branch automerge failure
This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
- Branch has one or more failed status checks