-
Notifications
You must be signed in to change notification settings - Fork 8
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 dependency semantic-release to v24 #221
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
October 20, 2021 09:52
a948b1e
to
d8993d6
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 24, 2021 08:22
d8993d6
to
4c45e19
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 7, 2022 15:19
4c45e19
to
12d082b
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v18
chore(deps): update dependency semantic-release to v19
Mar 7, 2022
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
May 17, 2022 09:57
efa306e
to
89a11d9
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 26, 2022 10:08
89a11d9
to
6c7da8a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 9, 2022 02:52
6c7da8a
to
88b87cb
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 25, 2022 11:58
88b87cb
to
cd02b9b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 20, 2022 17:40
cd02b9b
to
a849daa
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19
chore(deps): update dependency semantic-release to v20
Mar 16, 2023
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 16, 2023 17:48
a849daa
to
8bebee1
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 24, 2023 23:20
8bebee1
to
e047cde
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v20
chore(deps): update dependency semantic-release to v21
Mar 24, 2023
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 3, 2023 10:03
e047cde
to
07fedf8
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
June 2, 2023 22:09
4eba38b
to
8f785a3
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 10, 2023 08:11
8f785a3
to
9bb9e9e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
July 5, 2023 01:48
72e2cdc
to
3672e16
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
August 24, 2023 17:28
76fe2d6
to
743889e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 15, 2023 08:53
743889e
to
7aac351
Compare
valerybugakov
force-pushed
the
master
branch
from
September 15, 2023 08:57
7f4aff7
to
010c032
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 15, 2023 09:00
7aac351
to
8fe5554
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
October 23, 2023 23:20
552110b
to
b83ea3a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
November 3, 2023 21:56
5c2f688
to
07a3cd3
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 17, 2023 03:28
07a3cd3
to
60a1bed
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
December 12, 2023 01:38
e4482c7
to
7ba444b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 12, 2023 07:19
7ba444b
to
676cb38
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 12, 2024 22:11
676cb38
to
637bc36
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v22
chore(deps): update dependency semantic-release to v23
Jan 12, 2024
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
February 7, 2024 16:48
fb51d63
to
6e359a4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
March 18, 2024 15:33
98408ac
to
a52c8dc
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 24, 2024 16:01
a52c8dc
to
4dc3230
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
April 9, 2024 22:35
929b7a2
to
172c57c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
May 11, 2024 02:44
17a1a0c
to
77a60a0
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 31, 2024 23:01
77a60a0
to
2af17b7
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v23
chore(deps): update dependency semantic-release to v24
May 31, 2024
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
August 17, 2024 14:28
2af17b7
to
29ece7d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 11, 2024 08:12
29ece7d
to
ce47882
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 27, 2024 20:05
ce47882
to
d924d6e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
October 25, 2024 22:24
798b3a7
to
71cb123
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 3, 2025 06:29
71cb123
to
d9a7c0c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^17.1.2
->^24.2.1
Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.
Release Notes
semantic-release/semantic-release (semantic-release)
v24.2.1
Compare Source
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
v17.4.7
Compare Source
Bug Fixes
v17.4.6
Compare Source
Bug Fixes
v17.4.5
Compare Source
Bug Fixes
v17.4.4
Compare Source
Bug Fixes
v17.4.3
Compare Source
Bug Fixes
CVE-2021-23337
(#1931) (55194c1)v17.4.2
Compare Source
Bug Fixes
v17.4.1
Compare Source
Bug Fixes
marked-terminal
(#1829) (07f12b9)v17.4.0
Compare Source
Features
v17.3.9
Compare Source
Bug Fixes
v17.3.8
Compare Source
Bug Fixes
v17.3.7
Compare Source
Bug Fixes
v17.3.6
Compare Source
Bug Fixes
v17.3.5
Compare Source
Bug Fixes
v17.3.4
Compare Source
Bug Fixes
v17.3.3
Compare Source
Bug Fixes
v17.3.2
Compare Source
Bug Fixes
v17.3.1
Compare Source
Bug Fixes
v17.3.0
Compare Source
Features
v17.2.4
Compare Source
Bug Fixes
v17.2.3
Compare Source
Bug Fixes
v17.2.2
Compare Source
Bug Fixes
v17.2.1
Compare Source
Reverts
v17.2.0
Compare Source
Features
Configuration
📅 Schedule: Branch creation - "on the 1st through 7th day of the month" in timezone America/Los_Angeles, Automerge - 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.