-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update semantic-release monorepo (major) #220
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-semantic-release-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
September 20, 2021 22:16
31290a2
to
b66ee77
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v18
chore(deps): update semantic-release monorepo (major)
Sep 20, 2021
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
6 times, most recently
from
September 27, 2021 19:18
a590800
to
c725a8d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
October 5, 2021 23:57
1a57c5d
to
f85cb02
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
11 times, most recently
from
October 14, 2021 20:19
2e43f7f
to
7711dfb
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
7 times, most recently
from
October 23, 2021 01:35
93a7741
to
2e4e036
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
March 18, 2024 14:16
4c1462d
to
924a159
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 24, 2024 16:51
924a159
to
6cdef79
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
April 10, 2024 03:57
96b430b
to
00a4611
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
May 10, 2024 22:42
d3c6daf
to
2bd6cf1
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 1, 2024 03:10
2bd6cf1
to
a23ea52
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
10 times, most recently
from
July 10, 2024 08:36
b72b96a
to
5413ca4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
August 17, 2024 12:32
5413ca4
to
8c11dcd
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 11, 2024 07:25
8c11dcd
to
0d3dee4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 27, 2024 18:51
0d3dee4
to
832771a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
October 25, 2024 19:29
938e502
to
7b5ddd7
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
November 8, 2024 03:23
72b7e07
to
8025848
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 9, 2024 08:46
8025848
to
d2d5fd9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 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:
5.0.1
->6.0.3
9.0.1
->10.0.1
17.4.7
->24.2.0
Release Notes
semantic-release/changelog (@semantic-release/changelog)
v6.0.3
Compare Source
Bug Fixes
v6.0.2
Compare Source
Bug Fixes
v6.0.1
Compare Source
Bug Fixes
v6.0.0
Compare Source
Features
BREAKING CHANGES
semantic-release/git (@semantic-release/git)
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
Features
BREAKING CHANGES
semantic-release/semantic-release (semantic-release)
v24.2.0
Compare Source
Features
v24.1.3
Compare Source
Bug Fixes
v24.1.2
Compare Source
Bug Fixes
@semantic-release/github
tov11.0.0
(#3460) (43df51b)v24.1.1
Compare Source
v24.1.0
Compare Source
v24.0.0
Compare Source
Bug Fixes
BREAKING CHANGES
conventional-changelog packages. if you are installing any of these packages in addition to
semantic-release, be sure to update them as well
versions of conventional-changelog packages. if you are installing any of these packages in addition
to semantic-release, be sure to update them as well
v23.1.1
Compare Source
v23.1.0
Compare Source
v23.0.8
Compare Source
Bug Fixes
v23.0.7
Compare Source
v23.0.6
Compare Source
Bug Fixes
v23.0.5
Compare Source
v23.0.4
Compare Source
v23.0.3
Compare Source
v23.0.2
Compare Source
Bug Fixes
v23.0.1
Compare Source
Bug Fixes
v23.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
https://github.com/semantic-release/env-ci/releases/tag/v11.0.0 for more information
related to https://github.com/semantic-release/semantic-release/discussions/3088
release.config.js
as the name of your config file, it needs to be moved to a.config/
directory. see https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0 for more detailv22.0.12
Compare Source
Bug Fixes
v22.0.11
Compare Source
Bug Fixes
v22.0.10
Compare Source
Bug Fixes
v22.0.9
Compare Source
Bug Fixes
v22.0.8
Compare Source
Bug Fixes
v22.0.7
Compare Source
Bug Fixes
Features
v22.0.6
Compare Source
Bug Fixes
v22.0.5
Compare Source
Bug Fixes
v22.0.4
Compare Source
Bug Fixes
v22.0.3
Compare Source
Bug Fixes
exports
definition for the time being (561e2d6), closes #2968. see https://github.com/semantic-release/semantic-release/issues/2978 for more information.v22.0.2
Compare Source
Bug Fixes
v22.0.1
Compare Source
Bug Fixes
release-notes-generator
andcommit-analyzer
plugins to stable versions (041e4f7), closes #2934v22.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
v20.6.1 to avoid a known node bug
v21.1.2
Compare Source
Bug Fixes
v21.1.1
Compare Source
Bug Fixes
v21.1.0
Compare Source
Features
v21.0.9
Compare Source
Bug Fixes
v21.0.8
Compare Source
Bug Fixes
v21.0.7
Compare Source
Bug Fixes
v21.0.6
Compare Source
Bug Fixes
v21.0.5
Compare Source
Bug Fixes
v21.0.4
Compare Source
Bug Fixes
v21.0.3
Compare Source
Bug Fixes
@semantic-release/commit-analyzer
tov10.0.0-beta.1
(4a6b31f)@semantic-release/github
to9.0.0-beta.2
(#2818) (6f19d77)v21.0.2
Compare Source
Bug Fixes
v21.0.1
Compare Source
Bug Fixes
v21.0.0
Compare Source
BREAKING CHANGES
NPM_USERNAME
andNPM_PASSWORD
is no longer supported. UseNPM_TOKEN
instead.Bug Fixes
@semantic-release/npm
to^10.0.0
(d647433)v20.1.3
Compare Source
Bug Fixes
v20.1.2
Compare Source
Bug Fixes
v20.1.1
Compare Source
Bug Fixes
v20.1.0
Compare Source
Features
v20.0.4
Compare Source
Bug Fixes
v20.0.3
Compare Source
Reverts
v20.0.2
Compare Source
Bug Fixes
v20.0.1
Compare Source
Bug Fixes
v20.0.0
Compare Source
BREAKING CHANGES
Features
Bug Fixes
v19.0.5
Compare Source
Reverts
v19.0.4
Compare Source
Bug Fixes
v19.0.3
Compare Source
Bug Fixes
v19.0.2
Compare Source
Bug Fixes
v19.0.1
Compare Source
Bug Fixes
v19.0.0
Compare Source
Bug Fixes
marked
to resolve ReDos vulnerability (#2330) (d9e5bc0)BREAKING CHANGES
@semantic-release/npm
has also dropped support for node v15marked
andmarked-terminal
that resolved the ReDoS vulnerability. removal of support of this node version should be low since it was not an LTS version and has been EOL for several months already.v18.0.1
Compare Source
Bug Fixes
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-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-workflows
BREAKING CHANGES
node-version: the minimum required version of node is now v14.17
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.
This PR was generated by Mend Renovate. View the repository job log.