-
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): semantic-release [security] #337
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.
Open
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
December 7, 2020 16:54
208adf8
to
583ebfe
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
January 23, 2021 09:55
583ebfe
to
a24e207
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
February 15, 2021 12:19
a24e207
to
b785832
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
March 1, 2021 12:32
ff5515e
to
841a5ee
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 8, 2021 13:54
841a5ee
to
80aa53b
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
March 22, 2021 14:19
d32387c
to
b6944b1
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 5, 2021 09:59
b6944b1
to
99f4d99
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
April 12, 2021 17:22
930a039
to
b4d1d06
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 26, 2021 09:45
b4d1d06
to
848bd61
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
May 10, 2021 10:08
6687326
to
67f5aa9
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 24, 2021 10:43
67f5aa9
to
5725f65
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
June 7, 2021 09:09
af52100
to
656c3fa
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
June 21, 2021 07:56
0363261
to
4c44bbf
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
July 5, 2021 08:45
2d97021
to
35f5ee4
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
July 19, 2021 08:32
469c8ce
to
1389a3b
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
August 2, 2021 08:59
b549f88
to
1548744
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
3 times, most recently
from
August 16, 2021 08:59
67b3370
to
ef8bdaf
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 23, 2021 09:45
ef8bdaf
to
d8c6b11
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 30, 2021 09:58
d8c6b11
to
369aeb4
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
December 26, 2022 11:45
f1289b0
to
9291578
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
January 2, 2023 14:54
9291578
to
d517781
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
January 16, 2023 12:35
6d13fa8
to
a6c4ea1
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
January 23, 2023 13:48
a6c4ea1
to
68dbd02
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
January 30, 2023 14:55
68dbd02
to
cdf6b23
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
February 13, 2023 12:24
cdf6b23
to
e493791
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
3 times, most recently
from
February 27, 2023 12:16
3fd5a4c
to
9738cf5
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 4, 2023 11:03
9738cf5
to
28f88cc
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 20, 2023 14:16
28f88cc
to
f5d1fc8
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
April 10, 2023 11:52
566cd1b
to
998e68c
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 17, 2023 15:21
998e68c
to
c09d834
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
May 1, 2023 14:43
b537cc8
to
1ddbc17
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
May 16, 2023 18:32
1628b2a
to
19fb63f
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 29, 2023 10:16
19fb63f
to
8b1a597
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
June 27, 2023 06:39
a914149
to
d4593dd
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
August 21, 2023 20:30
4a30c3d
to
6b553fb
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 26, 2023 01:42
6b553fb
to
25880fe
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
September 13, 2023 04:48
25880fe
to
85edfb0
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
November 21, 2023 21:56
85edfb0
to
0c8b789
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
January 23, 2024 09:43
0c8b789
to
94c048d
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.12.5
->17.2.3
GitHub Vulnerability Alerts
CVE-2020-26226
Impact
Secrets that would normally be masked by
semantic-release
can be accidentally disclosed if they contain characters that become encoded when included in a URL.Patches
Fixed in v17.2.3
Workarounds
Secrets that do not contain characters that become encoded when included in a URL are already masked properly.
Release Notes
semantic-release/semantic-release (semantic-release)
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)Performance Improvements
git tag --merge <branch>
to filter tags present in a branch history (cffe9a8)Bug Fixes
channel
to publish success log (5744c5e)ERELEASEBRANCHES
error message (#1188) (37bcc9e)ci
option via API and config file (2faff26)getTagHead
only when necessary (de77a79)success
plugin only once for releases added to a channel (9a023b4)addChannel
for 2 merged branches configured with the same channel (4aad9cd)false
(751a5f1)getError
(f96c660)await
(9a1af4d)get-tags
algorithm (00420a8)branch
parameter frompush
function (968b996)v15.14.0
Compare Source
Features
envi-ci
values to plugins context (a8c747d)v15.13.32
Compare Source
Bug Fixes
v15.13.31
Compare Source
Bug Fixes
v15.13.30
Compare Source
Bug Fixes
v15.13.29
Compare Source
Bug Fixes
v15.13.28
Compare Source
Bug Fixes
v15.13.27
Compare Source
Bug Fixes
v15.13.26
Compare Source
Bug Fixes
v15.13.25
Compare Source
Bug Fixes
v15.13.24
Compare Source
Reverts
v15.13.23
Compare Source
Bug Fixes
v15.13.22
Compare Source
Bug Fixes
v15.13.21
Compare Source
Bug Fixes
v15.13.20
Compare Source
Bug Fixes
v15.13.19
Compare Source
Bug Fixes
v15.13.18
Compare Source
Bug Fixes
^1.0.0
(6b3adf6)v15.13.17
Compare Source
Bug Fixes
v15.13.16
Compare Source
Bug Fixes
v15.13.15
Compare Source
Bug Fixes
v15.13.14
Compare Source
Bug Fixes
v15.13.13
Compare Source
Bug Fixes
v15.13.12
Compare Source
Bug Fixes
v15.13.11
Compare Source
Bug Fixes
v15.13.10
Compare Source
Bug Fixes
v15.13.9
Compare Source
Bug Fixes
v15.13.8
Compare Source
Bug Fixes
v15.13.7
Compare Source
Bug Fixes
v15.13.6
Compare Source
Bug Fixes
v15.13.5
Compare Source
Bug Fixes
v15.13.4
Compare Source
Bug Fixes
v15.13.3
Compare Source
Bug Fixes
v15.13.2
Compare Source
Bug Fixes
v15.13.1
Compare Source
Bug Fixes
v15.13.0
Compare Source
Features
publish
plugins to returnfalse
in order to signify no release was done (70c68ef)Configuration
📅 Schedule: Branch creation - "" 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.