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] #311
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 }}
Could not load tags
Nothing to show
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
January 23, 2021 03:59
2ade024
to
ccb3e75
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
February 15, 2021 12:31
573199a
to
6410aaa
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
February 22, 2021 11:13
6410aaa
to
f61a0ca
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 1, 2021 12:20
f61a0ca
to
a1db650
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 8, 2021 12:56
a1db650
to
b6b19ed
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
March 22, 2021 12:57
c1a6567
to
b97d491
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 5, 2021 10:25
b97d491
to
effb4ef
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
April 12, 2021 18:33
dfed138
to
91ade2a
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
May 3, 2021 10:29
a12c3b0
to
0effc98
Compare
renovate
bot
changed the title
chore(deps): semantic-release [security]
chore(deps): semantic-release [security] - autoclosed
May 10, 2021
renovate
bot
changed the title
chore(deps): semantic-release [security] - autoclosed
chore(deps): semantic-release [security]
May 10, 2021
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 10, 2021 03:52
0effc98
to
5d7f346
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 24, 2021 09:38
5d7f346
to
5d628fc
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
June 7, 2021 09:05
6a92d9a
to
dfa0232
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
June 21, 2021 08:42
e98a2f4
to
27f5c58
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
June 28, 2021 08:55
27f5c58
to
25b5ac3
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
July 12, 2021 08:52
2e1457d
to
363e252
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
July 19, 2021 08:36
363e252
to
9d16a7f
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
July 26, 2021 09:32
9d16a7f
to
08bd536
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 2, 2021 08:38
08bd536
to
d25f80c
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
August 16, 2021 09:06
c1bcf16
to
bb7dc85
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 23, 2021 09:37
bb7dc85
to
0030277
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
3 times, most recently
from
September 6, 2021 09:59
04471b9
to
c386ccf
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
September 20, 2021 09:47
f55f196
to
4868a3d
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
October 4, 2021 09:10
0988227
to
ff8d112
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
October 11, 2021 09:44
ff8d112
to
b8f3840
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
October 25, 2021 10:44
b8f3840
to
bf90589
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
November 8, 2021 13:50
bf90589
to
f8e47a0
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
November 29, 2021 08:23
f8e47a0
to
9457733
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
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.13.30
->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
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
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 has been generated by Mend Renovate. View repository job log here.