chore(deps): update semantic-release monorepo (major)#40
Open
renovate[bot] wants to merge 1 commit intomasterfrom
Open
chore(deps): update semantic-release monorepo (major)#40renovate[bot] wants to merge 1 commit intomasterfrom
renovate[bot] wants to merge 1 commit intomasterfrom
Conversation
a66a654 to
f145ae1
Compare
7dbd7f7 to
8c4fc9a
Compare
faa8846 to
14c1d31
Compare
14c1d31 to
45e990c
Compare
cb70a58 to
5694b07
Compare
5694b07 to
65421a0
Compare
65421a0 to
22143a0
Compare
22143a0 to
451eb09
Compare
451eb09 to
1e247a5
Compare
1e247a5 to
4c1b5da
Compare
4c1b5da to
dbb0029
Compare
dbb0029 to
dc577ab
Compare
dc577ab to
950b40a
Compare
Author
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: package-lock.json |
e771ad5 to
f52025a
Compare
f52025a to
f64ce64
Compare
f64ce64 to
23723d3
Compare
23723d3 to
3339b8c
Compare
3339b8c to
f558405
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 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:
3.0.6→6.0.37.0.18→10.0.115.14.0→25.0.3Release Notes
semantic-release/changelog (@semantic-release/changelog)
v6.0.3Compare Source
Bug Fixes
v6.0.2Compare Source
Bug Fixes
v6.0.1Compare Source
Bug Fixes
v6.0.0Compare Source
Features
BREAKING CHANGES
v5.0.1Compare Source
Bug Fixes
v5.0.0Compare Source
chore
BREAKING CHANGES
v4.0.0Compare Source
Features
BREAKING CHANGES
semantic-release/git (@semantic-release/git)
v10.0.1Compare Source
Bug Fixes
v10.0.0Compare Source
Features
BREAKING CHANGES
v9.0.1Compare Source
Bug Fixes
v9.0.0Compare Source
chore
BREAKING CHANGES
v8.0.0Compare Source
Bug Fixes
Features
branchparameter from semantic-release@16.0.0 (02b1f6d)BREAKING CHANGES
semantic-release/semantic-release (semantic-release)
v25.0.3Compare Source
Bug Fixes
v25.0.2Compare Source
Bug Fixes
v25.0.1Compare Source
Bug Fixes
v25.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
v24.2.9Compare Source
Bug Fixes
v24.2.8Compare Source
Bug Fixes
v24.2.7Compare Source
Performance Improvements
v24.2.6Compare Source
Bug Fixes
v24.2.5Compare Source
Bug Fixes
marked-terminal(#3742) (fb1ccd4)v24.2.4Compare Source
Bug Fixes
v24.2.3Compare Source
Bug Fixes
v24.2.2Compare Source
Bug Fixes
v24.2.1Compare Source
Bug Fixes
v24.2.0Compare Source
Features
v24.1.3Compare Source
Bug Fixes
v24.1.2Compare Source
Bug Fixes
@semantic-release/githubtov11.0.0(#3460) (43df51b)v24.1.1Compare Source
Bug Fixes
v24.1.0Compare Source
Features
warntype to globalcontext.logger(#3423) (bcc663c)v24.0.0Compare 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.1Compare Source
Bug Fixes
v23.1.0Compare Source
Features
v23.0.8Compare Source
Bug Fixes
v23.0.7Compare Source
Bug Fixes
v23.0.6Compare Source
Bug Fixes
v23.0.5Compare Source
Bug Fixes
v23.0.4Compare Source
Bug Fixes
v23.0.3Compare Source
Bug Fixes
v23.0.2Compare Source
Bug Fixes
v23.0.1Compare Source
Bug Fixes
v23.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
https://github.com/semantic-release/env-ci/releases/tag/v11.0.0 for more information
related to https://redirect.github.com/semantic-release/semantic-release/discussions/3088
release.config.jsas the name of your config file, it needs to be moved to a.config/directory or renamed to.releaserc.jsto keep it in the root of the repository. see https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0 for more detailv22.0.12Compare Source
Bug Fixes
v22.0.11Compare Source
Bug Fixes
v22.0.10Compare Source
Bug Fixes
v22.0.9Compare Source
Bug Fixes
v22.0.8Compare Source
Bug Fixes
v22.0.7Compare Source
Bug Fixes
Features
v22.0.6Compare Source
Bug Fixes
v22.0.5Compare Source
Bug Fixes
v22.0.4Compare Source
Bug Fixes
v22.0.3Compare Source
Bug Fixes
exportsdefinition for the time being (561e2d6), closes #2968. see #2978 for more information.v22.0.2Compare Source
Bug Fixes
v22.0.1Compare Source
Bug Fixes
release-notes-generatorandcommit-analyzerplugins to stable versions (041e4f7), closes #2934v22.0.0Compare Source
Bug Fixes
Features
BREAKING CHANGES
v20.6.1 to avoid a known node bug
v21.1.2Compare Source
Bug Fixes
v21.1.1Compare Source
Bug Fixes
v21.1.0Compare Source
Features
v21.0.9Compare Source
Bug Fixes
v21.0.8Compare Source
Bug Fixes
v21.0.7Compare Source
Bug Fixes
v21.0.6Compare Source
Bug Fixes
v21.0.5Compare Source
Bug Fixes
v21.0.4Compare Source
Bug Fixes
v21.0.3Compare Source
Bug Fixes
@semantic-release/commit-analyzertov10.0.0-beta.1(4a6b31f)@semantic-release/githubto9.0.0-beta.2(#2818) (6f19d77)v21.0.2Compare Source
Bug Fixes
v21.0.1Compare Source
Bug Fixes
v21.0.0Compare Source
BREAKING CHANGES
NPM_USERNAMEandNPM_PASSWORDis no longer supported. UseNPM_TOKENinstead.Bug Fixes
@semantic-release/npmto^10.0.0(d647433)v20.1.3Compare Source
Bug Fixes
v20.1.2Compare Source
Bug Fixes
v20.1.1Compare Source
Bug Fixes
v20.1.0Compare Source
Features
v20.0.4Compare Source
Bug Fixes
v20.0.3Compare Source
Reverts
v20.0.2Compare Source
Bug Fixes
v20.0.1Compare Source
Bug Fixes
v20.0.0Compare Source
BREAKING CHANGES
Features
Bug Fixes
v19.0.5Compare Source
Reverts
v19.0.4Compare Source
Bug Fixes
v19.0.3Compare Source
Bug Fixes
v19.0.2Compare Source
Bug Fixes
v19.0.1Compare Source
Bug Fixes
v19.0.0Compare Source
Bug Fixes
markedto resolve ReDos vulnerability (#2330) (d9e5bc0)BREAKING CHANGES
@semantic-release/npmhas also dropped support for node v15markedandmarked-terminalthat 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.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
v17.4.7Compare Source
Bug Fixes
v17.4.6Compare Source
Bug Fixes
v17.4.5Compare Source
Bug Fixes
v17.4.4Compare Source
Bug Fixes
v17.4.3Compare Source
Bug Fixes
CVE-2021-23337(#1931) (55194c1)[
v17.4.2](https://redirect.gitConfiguration
📅 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.
👻 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.