Skip to content

⬆️ Updates semantic-release to v19 [SECURITY] - #539

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-semantic-release-vulnerability
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-semantic-release-vulnerability

Conversation

@renovate

@renovate renovate Bot commented May 28, 2023 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
semantic-release 17.3.9 → 19.0.3 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Exposure of Sensitive Information to an Unauthorized Actor in semantic-release

CVE-2022-31051 / GHSA-x2pg-mjhr-2m5x

More information

Details

Impact

What kind of vulnerability is it? Who is impacted?

Secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that are excluded from uri encoding by encodeURI. Occurrence is further limited to execution contexts where push access to the related repository is not available without modifying the repository url to inject credentials.

Patches

Has the problem been patched? What versions should users upgrade to?

Fixed in 19.0.3

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Secrets that do not contain characters that are excluded from encoding with encodeURI when included in a URL are already masked properly.

References

Are there any links users can visit to find out more?

For more information

If you have any questions or comments about this advisory:

Severity

  • CVSS Score: 4.4 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

semantic-release/semantic-release (semantic-release)

v19.0.3

Compare Source

Bug Fixes
  • log-repo: use the original form of the repo url to remove the need to mask credentials (#​2459) (58a226f), closes #​2449

v19.0.2

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the stable version (0eca144)

v19.0.1

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the latest beta version (8097afb)

v19.0.0

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the beta, which upgrades npm to v8 (f634b8c)
  • upgrade marked to resolve ReDos vulnerability (#​2330) (d9e5bc0)
BREAKING CHANGES
  • npm-plugin: @semantic-release/npm has also dropped support for node v15
  • node v15 has been removed from our defined supported versions of node. this was done to upgrade to compatible versions of marked and marked-terminal that resolved the ReDoS vulnerability. removal of support of this node version should be low since it was not an LTS version and has been EOL for several months already.

v18.0.1

Compare Source

Bug Fixes

v18.0.0

Compare Source

This is a maintenance release. An increasing amount of dependencies required a node version higher than the Node 10 version supported by semantic-release@17. We decided to go straight to a recent Node LTS version because the release build is usually independent of others, requiring a higher node version is less disruptive to users, but helps us reduce the maintenance overhead.

If you use GitHub Actions and need to bump the node version set up by actions/node-setup, you can use octoherd-script-bump-node-version-in-workflows

BREAKING CHANGES

node-version: the minimum required version of node is now v14.17

v17.4.7

Compare Source

Bug Fixes
  • engines: fixed defined node version to account for the higher requirement from the npm plugin (#​2088) (ea52e17)

v17.4.6

Compare Source

Bug Fixes

v17.4.5

Compare Source

Bug Fixes
  • deps: update dependency marked to v3 (6e4beb8)

v17.4.4

Compare Source

Bug Fixes

v17.4.3

Compare Source

Bug Fixes
  • bump minimal version of lodash to address CVE-2021-23337 (#​1931) (55194c1)

v17.4.2

Compare Source

Bug Fixes

v17.4.1

Compare Source

Bug Fixes

v17.4.0

Compare Source

Features

Configuration

📅 Schedule: (in timezone Europe/Moscow)

  • Branch creation
    • At any time (no schedule defined)
  • 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.


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

This PR was generated by Mend Renovate. View the repository job log.

@changelogg

changelogg Bot commented May 28, 2023

Copy link
Copy Markdown

Hey! Changelogs info seems to be missing or might be in incorrect format.
Please use the below template in PR description to ensure Changelogg can detect your changes:
- (tag) changelog_text
or
- tag: changelog_text
OR
You can add tag in PR header or while doing a commit too
(tag) PR header
or
tag: PR header
Valid tags: added / feat, changed, deprecated, fixed / fix, removed, security, build, ci, chore, docs, perf, refactor, revert, style, test
Thanks!
For more info, check out changelogg docs

@auto-assign
auto-assign Bot requested a review from AlexRogalskiy May 28, 2023 09:55
@viezly

viezly Bot commented May 28, 2023

Copy link
Copy Markdown

Pull request by bot. No need to analyze

@socket-security

socket-security Bot commented May 28, 2023 •

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @pnpm/network.ca-file is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package-lock.json → npm/semantic-release@19.0.3 → npm/@pnpm/network.ca-file@1.0.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@pnpm/network.ca-file@1.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@github-actions

Copy link
Copy Markdown

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

@github-actions

Copy link
Copy Markdown

🏷️ [bumpr] Next version:v2.0.2 Changes:v2.0.1...AlexRogalskiy:renovate/npm-semantic-release-vulnerability

@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from c911eae to 0b4d1ca Compare January 23, 2025 19:36
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 0b4d1ca to 1220032 Compare February 9, 2025 15:39
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 1220032 to 17e8742 Compare March 11, 2025 16:36
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 17e8742 to 33b114b Compare May 19, 2025 18:49
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 57ab327 to 5914626 Compare August 13, 2025 14:15
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 5914626 to 7fa23ca Compare August 24, 2025 03:26
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 7fa23ca to 10440ac Compare September 25, 2025 20:35
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 10440ac to 38ca76d Compare November 11, 2025 01:16
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 38ca76d to 4ca93e8 Compare November 20, 2025 19:40
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 4ca93e8 to 69a92de Compare December 31, 2025 15:45
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 69421b3 to b864c24 Compare January 23, 2026 16:33
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from b864c24 to 20eb732 Compare March 5, 2026 19:18
@renovate renovate Bot changed the title ⬆️ Updates semantic-release to v19 [SECURITY] ⬆️ Updates semantic-release to v19 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-semantic-release-vulnerability branch March 27, 2026 01:05
@renovate renovate Bot changed the title ⬆️ Updates semantic-release to v19 [SECURITY] - autoclosed ⬆️ Updates semantic-release to v19 [SECURITY] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from ab0f665 to 20eb732 Compare March 30, 2026 22:06
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 20eb732 to ab0f665 Compare March 30, 2026 22:06
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from ab0f665 to d631fc9 Compare April 8, 2026 17:05
@renovate renovate Bot changed the title ⬆️ Updates semantic-release to v19 [SECURITY] ⬆️ Updates semantic-release to v19 [SECURITY] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title ⬆️ Updates semantic-release to v19 [SECURITY] - autoclosed ⬆️ Updates semantic-release to v19 [SECURITY] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from d631fc9 to a4ae664 Compare April 27, 2026 21:20
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from a4ae664 to c96ff44 Compare May 12, 2026 13:15
@socket-security

socket-security Bot commented May 12, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedsemantic-release@​17.3.9 ⏵ 19.0.397 +1100 +210095 +5100

View full report

@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from c96ff44 to 73eddec Compare June 11, 2026 16:14
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 73eddec to 2a6fa3c Compare July 12, 2026 11:33
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 2a6fa3c to fd18e72 Compare July 24, 2026 18:40
@socket-security

socket-security Bot commented Jul 24, 2026 •

Copy link
Copy Markdown

All alerts resolved. Learn more about Socket for GitHub.

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report

@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from fd18e72 to c36165c Compare September 24, 2026 18:50
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from c36165c to 4514c60 Compare October 30, 2026 07:53
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 4514c60 to 3c29c80 Compare November 5, 2026 23:48
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.

0 participants