Skip to content

chore(deps): update dependency semantic-release to v17.2.3 [security] - autoclosed #22

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

Closed

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Nov 27, 2020

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 17.0.4 -> 17.2.3 age adoption passing confidence

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
  • mask secrets when characters get uri encoded (ca90b34)

v17.2.2

Compare Source

Bug Fixes
  • don't parse port as part of the path in repository URLs (#​1671) (77a75f0)
  • use valid git credentials when multiple are provided (#​1669) (2bf3771)

v17.2.1

Compare Source

Reverts

v17.2.0

Compare Source

Features
  • throw an Error if package.json has duplicate "repository" key (#​1656) (b8fb35c)

v17.1.2

Compare Source

Bug Fixes

v17.1.1

Compare Source

Bug Fixes

v17.1.0

Compare Source

Features
  • bitbucket-basic-auth: support for bitbucket server basic auth (#​1578) (a465801)

v17.0.8

Compare Source

Bug Fixes
  • prevent false positive secret replacement for Golang projects (#​1562) (eed1d3c)

v17.0.7

Compare Source

Bug Fixes

v17.0.6

Compare Source

Bug Fixes

v17.0.5

Compare Source

Bug Fixes
  • adapt for semver to version 7.3.2 (0363790)

Configuration

📅 Schedule: "" (UTC).

🚦 Automerge: Enabled.

♻️ 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.


  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@codecov-io
Copy link

codecov-io commented Nov 27, 2020

Codecov Report

Merging #22 (7f793b8) into develop (665e490) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##           develop       #22   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           14        14           
  Lines          330       330           
  Branches        22        22           
=========================================
  Hits           330       330           
Flag Coverage Δ
unittests ?

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 665e490...7f793b8. Read the comment docs.

@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from ea0d66e to 28bbd9d Compare December 10, 2020 16:56
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from b928e87 to a4864c1 Compare January 10, 2021 20:54
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from a4864c1 to ed00b7a Compare January 24, 2021 15:56
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from d7d8902 to 8fa0cd3 Compare February 10, 2021 11:51
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 8fa0cd3 to 7f793b8 Compare February 11, 2021 09:48
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 7f793b8 to 7e517f1 Compare April 26, 2021 15:26
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 7e517f1 to 3c85101 Compare May 9, 2021 22:28
@codecov-commenter
Copy link

Codecov Report

Merging #22 (3c85101) into develop (665e490) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##           develop       #22   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           14        14           
  Lines          330       330           
  Branches        22        22           
=========================================
  Hits           330       330           
Flag Coverage Δ
unittests ?

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 665e490...3c85101. Read the comment docs.

@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17.2.3 [security] chore(deps): update dependency semantic-release to v17.2.3 [security] - autoclosed Aug 16, 2021
@renovate renovate bot closed this Aug 16, 2021
@renovate renovate bot deleted the renovate/npm-semantic-release-vulnerability branch August 16, 2021 07:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants