-
Notifications
You must be signed in to change notification settings - Fork 0
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] #143
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
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
from
January 9, 2023 13:16
5877e6b
to
5cc5099
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
January 23, 2023 10:38
f0ee90e
to
da68fbc
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
January 30, 2023 15:23
da68fbc
to
66e88bd
Compare
renovate
bot
changed the title
chore(deps): semantic-release [security]
chore(deps): semantic-release [security] - autoclosed
Feb 8, 2023
renovate
bot
changed the title
chore(deps): semantic-release [security] - autoclosed
chore(deps): semantic-release [security]
Feb 8, 2023
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
February 27, 2023 13:53
66e88bd
to
b43a4d4
Compare
renovate
bot
changed the title
chore(deps): semantic-release [security]
chore(deps): semantic-release [security] - autoclosed
Mar 1, 2023
renovate
bot
changed the title
chore(deps): semantic-release [security] - autoclosed
chore(deps): semantic-release [security]
Mar 1, 2023
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 6, 2023 12:53
b43a4d4
to
a46b8c5
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 20, 2023 12:29
a46b8c5
to
1bff0ea
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 10, 2023 12:48
1bff0ea
to
8fd0144
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 24, 2023 12:02
8fd0144
to
715ca65
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 15, 2023 12:20
715ca65
to
417b086
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 22, 2023 14:23
417b086
to
e5554cb
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
June 19, 2023 10:51
e5554cb
to
d933e0f
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
June 26, 2023 12:49
d933e0f
to
116aa0f
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
2 times, most recently
from
July 10, 2023 09:47
0d12037
to
c05e761
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
July 24, 2023 10:52
c05e761
to
d8d21bd
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
August 7, 2023 10:58
d8d21bd
to
222dc7f
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.