chore(deps): semantic-release [security] - #143
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
February 15, 2021 12:30
3f328df to
416c957
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
February 22, 2021 12:37
416c957 to
bf8b359
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
March 8, 2021 12:59
b8e3cb4 to
4167c51
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
March 22, 2021 13:39
af5763a to
5c34a64
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 5, 2021 09:23
5c34a64 to
4897be5
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 12, 2021 10:53
4897be5 to
a229baa
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
May 3, 2021 10:27
81ee36d to
aacfe2d
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 10, 2021 11:01
aacfe2d to
71bc469
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 24, 2021 10:49
71bc469 to
7ed4750
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
June 7, 2021 08:24
18f2252 to
3a558d4
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
June 21, 2021 09:05
0fb6793 to
a812815
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
July 5, 2021 08:56
9534b9d to
fef27ff
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
July 12, 2021 08:31
fef27ff to
3b6d53c
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
July 26, 2021 08:56
2673e22 to
f24bcd7
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 2, 2021 09:12
f24bcd7 to
1948af7
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
August 16, 2021 09:25
eb8168e to
9598e46
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 23, 2021 11:16
9598e46 to
5cd9ae4
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
September 6, 2021 10:13
0e49975 to
c021ade
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
September 13, 2021 10:43
c021ade to
c900e05
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
September 27, 2021 10:17
af92973 to
bfff6a8
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
3 times, most recently
from
January 15, 2022 01:38
8dba2ad to
be7e80b
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
January 24, 2022 10:49
be7e80b to
475bd4b
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
February 7, 2022 11:02
475bd4b to
937c3b5
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
February 21, 2022 13:37
937c3b5 to
5dec3c3
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 21, 2022 14:24
5dec3c3 to
5579045
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 11, 2022 15:00
5579045 to
367c763
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 2, 2022 14:03
367c763 to
75e54fe
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 23, 2022 12:52
75e54fe to
805cd9b
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
July 18, 2022 13:23
805cd9b to
c0cd5c8
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
August 15, 2022 13:54
6391b81 to
5e0943d
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 22, 2022 13:34
5e0943d to
725dc11
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
September 8, 2022 14:52
725dc11 to
a1f07bf
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
September 19, 2022 13:09
a1f07bf to
14bdad8
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
October 3, 2022 15:30
a0e19c2 to
79ff63d
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
October 17, 2022 08:16
92fbdb3 to
663ea28
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
October 24, 2022 10:55
663ea28 to
a6d3920
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
November 7, 2022 14:04
a6d3920 to
a5662fb
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
November 28, 2022 11:40
954cbf9 to
317f725
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
December 12, 2022 11:45
10bd9db to
f35ce52
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
December 19, 2022 12:08
f35ce52 to
f35896d
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:
15.12.5→17.2.3GitHub Vulnerability Alerts
CVE-2020-26226
Impact
Secrets that would normally be masked by
semantic-releasecan 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.3Compare Source
Bug Fixes
v17.2.2Compare Source
Bug Fixes
v17.2.1Compare Source
Reverts
v17.2.0Compare Source
Features
v17.1.2Compare Source
Bug Fixes
v17.1.1Compare Source
Bug Fixes
v17.1.0Compare Source
Features
v17.0.8Compare Source
Bug Fixes
v17.0.7Compare Source
Bug Fixes
v17.0.6Compare Source
Bug Fixes
v17.0.5Compare Source
Bug Fixes
v17.0.4Compare Source
Bug Fixes
repositoryUrlin logs (55be0ba)v17.0.3Compare Source
Bug Fixes
getGitAuthUrl(e7bede1)v17.0.2Compare Source
Bug Fixes
v17.0.1Compare Source
Bug Fixes
v17.0.0Compare Source
BREAKING CHANGES
v16.0.4Compare Source
Bug Fixes
v16.0.3Compare Source
Bug Fixes
--no-verifywhen testing the Git permissions (b54b20d)v16.0.2Compare Source
Bug Fixes
v16.0.1Compare Source
Bug Fixes
v16.0.0Compare Source
BREAKING CHANGES
v16.0.0@​betausers 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 usingnullfor 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
--mergeoption of thegit tagcommand 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
releaseRulesoption.Regex are replaced by globs. For example
/core-.*/should be changed to'core-*'.The
branchoption has been removed in favor ofbranchesThe new
branchesoption expect either an Array or a single branch definition. To migrate your configuration:master: nothing to changebranchconfiguration and want to publish only from one branch: replacebranchwithbranches("branch": "my-release-branch"=>"branches": "my-release-branch")Features
addChannelplugins to returnfalsein order to signify no release was done (e1c7269)publishplugins to returnfalsein 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
channelto publish success log (5744c5e)ERELEASEBRANCHESerror message (#1188) (37bcc9e)cioption via API and config file (2faff26)getTagHeadonly when necessary (de77a79)successplugin only once for releases added to a channel (9a023b4)addChannelfor 2 merged branches configured with the same channel (4aad9cd)false(751a5f1)getError(f96c660)await(9a1af4d)get-tagsalgorithm (00420a8)branchparameter frompushfunction (968b996)v15.14.0Compare Source
Features
envi-civalues to plugins context (a8c747d)v15.13.32Compare Source
Bug Fixes
v15.13.31Compare Source
Bug Fixes
v15.13.30Compare Source
Bug Fixes
v15.13.29Compare Source
Bug Fixes
v15.13.28Compare Source
Bug Fixes
v15.13.27Compare Source
Bug Fixes
v15.13.26Compare Source
Bug Fixes
v15.13.25Compare Source
Bug Fixes
v15.13.24Compare Source
Reverts
v15.13.23Compare Source
Bug Fixes
v15.13.22Compare Source
Bug Fixes
v15.13.21Compare Source
Bug Fixes
v15.13.20Compare Source
Bug Fixes
v15.13.19Compare Source
Bug Fixes
v15.13.18Compare Source
Bug Fixes
^1.0.0(6b3adf6)v15.13.17Compare Source
Bug Fixes
v15.13.16Compare Source
Bug Fixes
v15.13.15Compare Source
Bug Fixes
v15.13.14Compare Source
Bug Fixes
v15.13.13Compare Source
Bug Fixes
v15.13.12Compare Source
Bug Fixes
v15.13.11Compare Source
Bug Fixes
v15.13.10Compare Source
Bug Fixes
v15.13.9Compare Source
Bug Fixes
v15.13.8Compare Source
Bug Fixes
v15.13.7Compare Source
Bug Fixes
v15.13.6Compare Source
Bug Fixes
v15.13.5Compare Source
Bug Fixes
v15.13.4Compare Source
Bug Fixes
v15.13.3Compare Source
Bug Fixes
v15.13.2Compare Source
Bug Fixes
v15.13.1Compare Source
Bug Fixes
v15.13.0Compare Source
Features
publishplugins to returnfalsein 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.