chore(deps): update semantic-release monorepo (major) #195
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.0.1
->6.0.0
8.0.1
->9.0.1
9.0.1
->10.0.0
7.2.3
->8.0.1
7.1.3
->8.0.0
9.0.3
->10.0.2
17.4.7
->18.0.0
Release Notes
semantic-release/changelog
v6.0.0
Compare Source
Features
BREAKING CHANGES
semantic-release/commit-analyzer
v9.0.1
Compare Source
Bug Fixes
v9.0.0
Compare Source
Features
BREAKING CHANGES
semantic-release/git
v10.0.0
Compare Source
Features
BREAKING CHANGES
semantic-release/github
v8.0.1
Compare Source
Bug Fixes
v8.0.0
Compare Source
BREAKING CHANGES
semantic-release/npm
v8.0.0
Compare Source
Features
BREAKING CHANGES
Co-authored-by: Matt Travi programmer@travi.org
semantic-release/release-notes-generator
v10.0.2
Compare Source
Bug Fixes
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
BREAKING CHANGES
Thanks
@abel-mak
semantic-release/semantic-release
v18.0.0
Compare Source
This is a maintenance release. An increasing amount of dependencies required a node version higher than the Node 10 version supported by
semantic-relase@17
. We decided to go straight to a recent Node LTS version because the release build is usually independent of others, requiring a higher node version is less disruptive to users, but helps us reduce the maintenance overhead.If you use GitHub Actions and need to bump the node version set up by
actions/node-setup
, you can useoctoherd-script-bump-node-version-in-workflows
BREAKING CHANGES
node-version: the minimum required version of node is now v14.17
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by WhiteSource Renovate. View repository job log here.