chore(deps): update dependency semantic-release to v19 [security] by renovate[bot] · Pull Request #313 · nartc/react-native-barcode-mask

renovate · 2022-06-18T21:21:16Z

This PR contains the following updates:

Package	Change	Age	Confidence
semantic-release	`17.3.7` → `19.0.3`

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:

Open a discussion in semantic-release discussions

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.

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

marked: reverted upgrade to v3 (#2087) (5edff69)

`v17.4.5`

Compare Source

Bug Fixes

deps: update dependency marked to v3 (6e4beb8)

`v17.4.4`

Compare Source

Bug Fixes

corrected spelling of invalid plugin config error (#1979) (80e1665)

`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

deps: update dependency hosted-git-info to v4 (#1838) (44b3344)

`v17.4.1`

Compare Source

Bug Fixes

deps: peer dependecy error with marked-terminal (#1829) (07f12b9)

`v17.4.0`

Compare Source

Features

config: Use cosmiconfig defaults to support .cjs config files (#1815) (3ecc196), closes #1814

`v17.3.9`

Compare Source

Bug Fixes

update link to GitLab CI introduction (#1794) (a9be97b)

`v17.3.8`

Compare Source

Bug Fixes

deps: update dependency marked to v2 (a2eaed0)

Configuration

📅 Schedule: (UTC)

Branch creation
- ""
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.

renovate · 2022-06-18T21:21:17Z

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json


real	0m7.545s
user	0m6.553s
sys	0m0.751s
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @nartc/react-native-barcode-mask@0.0.0-development
npm ERR! Found: react@16.13.1
npm ERR! node_modules/react
npm ERR!   dev react@"16.13.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"17.0.1" from react-native@0.64.1
npm ERR! node_modules/react-native
npm ERR!   dev react-native@"0.64.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-06-18T21_21_02_823Z-debug-0.log

renovate · 2025-08-10T14:45:51Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @nartc/react-native-barcode-mask@0.0.0-development
npm ERR! Found: react@16.13.1
npm ERR! node_modules/react
npm ERR!   dev react@"16.13.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"17.0.1" from react-native@0.64.1
npm ERR! node_modules/react-native
npm ERR!   dev react-native@"0.64.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-04-08T16_51_46_203Z-debug-0.log

renovate Bot changed the title ~~chore(deps): update dependency semantic-release to v19 [security]~~ chore(deps): update dependency semantic-release to v19 [security] - autoclosed Mar 27, 2026

renovate Bot closed this Mar 27, 2026

renovate Bot deleted the renovate/npm-semantic-release-vulnerability branch March 27, 2026 01:41

chore(deps): update dependency semantic-release to v19 [security]

667c766

renovate Bot changed the title ~~chore(deps): update dependency semantic-release to v19 [security] - autoclosed~~ chore(deps): update dependency semantic-release to v19 [security] Mar 30, 2026

renovate Bot reopened this Mar 30, 2026

renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from e32090e to 667c766 Compare March 30, 2026 21:30

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update dependency semantic-release to v19 [security]#313

chore(deps): update dependency semantic-release to v19 [security]#313
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-semantic-release-vulnerability

renovate Bot commented Jun 18, 2022 •

edited

Loading

Uh oh!

renovate Bot commented Jun 18, 2022

Uh oh!

renovate Bot commented Aug 10, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

renovate Bot commented Jun 18, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

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

Details

Impact

Patches

Workarounds

References

For more information

Severity

References

Release Notes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

BREAKING CHANGES

Bug Fixes

BREAKING CHANGES

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Configuration

Uh oh!

renovate Bot commented Jun 18, 2022

⚠ Artifact update problem

File name: package-lock.json

Uh oh!

renovate Bot commented Aug 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Artifact update problem

File name: package-lock.json

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Jun 18, 2022 •

edited

Loading

renovate Bot commented Aug 10, 2025 •

edited

Loading