-
Notifications
You must be signed in to change notification settings - Fork 1
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 #260
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
from
January 22, 2021 18:57
2cccc8c
to
83e141d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 30, 2021 18:55
83e141d
to
9fe695f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
February 13, 2021 10:46
11ed0b0
to
eb81423
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
March 3, 2021 21:05
d4bc5a6
to
2a66a39
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 11, 2021 22:28
2a66a39
to
e860eec
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 15, 2021 19:12
e860eec
to
f83ebde
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 18, 2021 19:15
f83ebde
to
1408933
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v17
chore(deps): update dependency semantic-release to v18
Oct 18, 2021
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 7, 2022 08:13
1408933
to
6f63fe2
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
from
June 18, 2022 13:39
6f63fe2
to
8dca45a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 25, 2022 12:52
8dca45a
to
407d11b
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 12:04
407d11b
to
3d3fb3b
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v20
chore(deps): update dependency semantic-release to v21
Mar 25, 2023
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 25, 2023 00:26
3d3fb3b
to
9f3b68f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 3, 2023 10:33
9f3b68f
to
9e5c3c0
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
June 2, 2023 22:40
4cacb55
to
a523003
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
June 10, 2023 00:22
de47f14
to
b7b1c2f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
July 5, 2023 01:16
c8efe61
to
c2415b4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
August 24, 2023 17:09
27398d3
to
ae596db
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
September 24, 2023 19:19
a7ec4f4
to
8eac0b6
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
November 3, 2023 22:12
460f7ee
to
d3740cf
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 17, 2023 02:11
d3740cf
to
5d4c8bf
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
December 6, 2023 06:42
3a5b89c
to
8b2994b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
December 12, 2023 06:25
89c426f
to
fdb598f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 12, 2024 22:09
fdb598f
to
138e941
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 15:36
09d4cf1
to
2188653
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
March 18, 2024 17:40
0b81b3e
to
4081f95
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 24, 2024 18:06
4081f95
to
424c2dc
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
April 9, 2024 21:31
0ebc5cd
to
5fe2bad
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
May 10, 2024 23:03
a0b5b5a
to
03eff17
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 31, 2024 23:33
03eff17
to
4fdb206
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 12:49
4fdb206
to
ad15907
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 11, 2024 04:15
ad15907
to
febaa69
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 27, 2024 19:16
febaa69
to
8186203
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 18, 2024 22:51
8186203
to
a7d790c
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:
15.14.0
->24.1.3
Release Notes
semantic-release/semantic-release (semantic-release)
v24.1.3
Compare Source
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
v17.1.2
Compare Source
Bug Fixes
v17.1.1
Compare Source
Bug Fixes
v17.1.0
Compare Source
Features
v17.0.8
Compare Source
Bug Fixes
v17.0.7
Compare Source
Bug Fixes
v17.0.6
Compare Source
Bug Fixes
v17.0.5
Compare Source
Bug Fixes
v17.0.4
Compare Source
Bug Fixes
repositoryUrl
in logs (55be0ba)v17.0.3
Compare Source
Bug Fixes
getGitAuthUrl
(e7bede1)v17.0.2
Compare Source
Bug Fixes
v17.0.1
Compare Source
Bug Fixes
v17.0.0
Compare Source
BREAKING CHANGES
v16.0.4
Compare Source
Bug Fixes
v16.0.3
Compare Source
Bug Fixes
--no-verify
when testing the Git permissions (b54b20d)v16.0.2
Compare Source
Bug Fixes
v16.0.1
Compare Source
Bug Fixes
v16.0.0
Compare Source
BREAKING CHANGES
v16.0.0@​beta
users only:In v16, a JSON object stored in a Git note is used to keep track of the channels on which a version has been released, the
@{channel}
suffix is no longer necessary.The tags formatted as v{version}@{channel} will now be ignored. If you have releases using this format you will have to upgrade them:
v{version}@​{channel}
{"channels":["channel1","channel2"]}
and usingnull
for the default channel (for example.{"channels":[null,"channel1","channel2"]}
)Require Node.js >= 10.13
Git CLI version 2.7.1 or higher is now required: The
--merge
option of thegit tag
command has been added in Git version 2.7.1 and is now used by semantic-releaseRegexp are not supported anymore for property matching in the
releaseRules
option.Regex are replaced by globs. For example
/core-.*/
should be changed to'core-*'
.The
branch
option has been removed in favor ofbranches
The new
branches
option expect either an Array or a single branch definition. To migrate your configuration:master
: nothing to changebranch
configuration and want to publish only from one branch: replacebranch
withbranches
("branch": "my-release-branch"
=>"branches": "my-release-branch"
)Features
addChannel
plugins to returnfalse
in order to signify no release was done (e1c7269)publish
plugins to returnfalse
in order to signify no release was done (47484f5)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.