-
Notifications
You must be signed in to change notification settings - Fork 4
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 [security] #13
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-semantic-release-vulnerability
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/npm-semantic-release-vulnerability
branch
from
March 5, 2024 05:32
de214ef
to
118c61a
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Mar 5, 2024
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
Mar 14, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
March 16, 2024 11:55
7131751
to
306341d
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Mar 16, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 22, 2024 23:49
306341d
to
080e33d
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
Mar 22, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 23, 2024 14:58
080e33d
to
3baccf4
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Mar 23, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 24, 2024 23:45
3baccf4
to
ee9eef2
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
Mar 24, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 25, 2024 23:49
ee9eef2
to
febadd3
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Mar 25, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 15, 2024 05:49
febadd3
to
994a69b
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
Apr 15, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 17, 2024 05:37
994a69b
to
a731a3b
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Apr 17, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 21, 2024 20:55
a731a3b
to
a0a320e
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
Apr 21, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 22, 2024 05:32
a0a320e
to
f01425d
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Apr 22, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 26, 2024 02:59
f01425d
to
4dd79fc
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
Apr 26, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 27, 2024 11:56
4dd79fc
to
be406c3
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Apr 27, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 2, 2024 17:42
be406c3
to
e7e0874
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
May 2, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 3, 2024 02:15
e7e0874
to
bd36ee8
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
May 3, 2024
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Jun 28, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
June 29, 2024 08:27
25f26d4
to
78817a9
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Jun 29, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
July 14, 2024 23:25
78817a9
to
2be1a1b
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Jul 14, 2024
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Jul 15, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
July 15, 2024 05:15
2be1a1b
to
4d9d317
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
July 24, 2024 02:39
4d9d317
to
5afe85b
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Jul 24, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
July 25, 2024 05:55
5afe85b
to
663c475
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Jul 25, 2024
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Jul 29, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
July 30, 2024 08:29
567b1b4
to
d995ce8
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Jul 30, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
October 10, 2024 14:57
d995ce8
to
94e084b
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Oct 10, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
October 11, 2024 05:09
94e084b
to
82335ce
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Oct 11, 2024
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Oct 29, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
October 31, 2024 05:38
2853cd3
to
1d97627
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Oct 31, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
December 3, 2024 05:59
1d97627
to
733987a
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Dec 3, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
December 5, 2024 23:48
733987a
to
09e8eda
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Dec 5, 2024
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
December 21, 2024 14:41
09e8eda
to
20870c3
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Dec 21, 2024
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:
^17.0.4
->^24.0.0
GitHub Vulnerability Alerts
CVE-2022-31051
Impact
What kind of vulnerability is it? Who is impacted?
Secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that are excluded from uri encoding by encodeURI. Occurrence is further limited to execution contexts where push access to the related repository is not available without modifying the repository url to inject credentials.
Patches
Has the problem been patched? What versions should users upgrade to?
Fixed in 19.0.3
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Secrets that do not contain characters that are excluded from encoding with
encodeURI
when included in a URL are already masked properly.References
Are there any links users can visit to find out more?
For more information
If you have any questions or comments about this advisory:
Release Notes
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 - "" (UTC), 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.