This repository was archived by the owner on Dec 6, 2023. It is now read-only.
chore(deps): update semantic-release monorepo (major)#958
Closed
renovate[bot] wants to merge 1 commit into
Closed
Conversation
renovate
Bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
27fe670 to
77749c9
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
6 times, most recently
from
0a07659 to
42504fa
Compare
renovate
Bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
9 times, most recently
from
7ce90b2 to
4beb13b
Compare
renovate
Bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
6 times, most recently
from
bb4d93f to
ec3738f
Compare
renovate
Bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
98eae40 to
99eacb7
Compare
renovate
Bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
8 times, most recently
from
0fa535f to
7120962
Compare
renovate
Bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
39f3f42 to
b6faa0e
Compare
renovate
Bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
5 times, most recently
from
08e56de to
50cf7ba
Compare
renovate
Bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
8 times, most recently
from
44b79f2 to
4164a2a
Compare
renovate
Bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
722939a to
f78a421
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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:
9.0.1->10.0.117.4.7->18.0.1Release Notes
semantic-release/git
v10.0.1Compare Source
Bug Fixes
v10.0.0Compare Source
Features
BREAKING CHANGES
semantic-release/semantic-release
v18.0.1Compare Source
Bug Fixes
v18.0.0Compare Source
This is a maintenance release. An increasing amount of dependencies required a node version higher than the Node 10 version supported by
semantic-release@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-workflowsBREAKING CHANGES
node-version: the minimum required version of node is now v14.17
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled due to failing status checks.
♻ 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.