:arrow_up: Updates semantic-release monorepo (major) by renovate[bot] · Pull Request #273 · AlexRogalskiy/github-action-screenshots

renovate · 2021-05-15T19:25:14Z

This PR contains the following updates:

Package	Change	Age	Confidence
@semantic-release/changelog	`^5.0.1` → `^7.0.0`
@semantic-release/commit-analyzer	`^8.0.1` → `^13.0.1`
@semantic-release/git	`^9.0.0` → `^11.0.1`
@semantic-release/github	`^7.2.0` → `^7.2.3`
@semantic-release/npm	`^7.0.10` → `^7.1.3`
@semantic-release/release-notes-generator	`^9.0.1` → `^9.0.3`

Warning

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

Release Notes

semantic-release/changelog (@semantic-release/changelog)

`v7.0.0`

Compare Source

Features

ES Module (#414) (e154214)

BREAKING CHANGES

@semantic-release/changelog is now a native ES
Module. It has named exports for each plugin hook (verifyConditions,
prepare)
the minimum required version of semantic-release to use
@semantic-release/changelog is now
v20.1.0

Other Notable Changes

Replaced xo with prettier with default configuration; following
newly established convention
Replaced nyc with c8 for code coverage
Replaced lodash with lodash-es for proper esm support

Related Issue

`v6.0.3`

Compare Source

Bug Fixes

deps: update dependency fs-extra to v11.1.1 (#309) (47045b3)

`v6.0.2`

Compare Source

Bug Fixes

deps: update dependency fs-extra to v11 (#276) (404c768)

`v6.0.1`

Compare Source

Bug Fixes

deps: update dependency @semantic-release/error to v3 (#167) (ef37296)

`v6.0.0`

Compare Source

Features

node-version: raised the minimum required version to v14.17 (#170) (5cf74e4)

BREAKING CHANGES

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

semantic-release/commit-analyzer (@semantic-release/commit-analyzer)

`v13.0.1`

Compare Source

Bug Fixes

deps: update dependency import-from-esm to v2 (#741) (f106b76)

`v13.0.0`

Compare Source

Bug Fixes

log the raw message again (e2f5d6c)

Features

support latest conventional-changelog packages (0254d7a)

BREAKING CHANGES

by supporting the latest major versions of conventional-changelog packages, we are
dropping support for previous major versions of those packages due to the breaking changes between
majors. this only impacts your project if you are installing alongside semantic-release, so updating
those packages to latest version should be the only change you need for this update. no action
should be necessary if you are using default semantic-release config

`v12.0.0`

Compare Source

Features

exports: defined exports to point at ./index.js (f3358dd)
node-versions: dropped support for node v18 and v19 (0a23b82)

BREAKING CHANGES

exports: exports has been defined, which prevents access to private apis (which arent
intended for consumption anyway)
node-versions: node v18 and v19 are no longer supported

`v11.1.0`

Compare Source

Features

add support for ESM presets (#537) (9dc87e0)

`v11.0.0`

Compare Source

Bug Fixes

config-loader: accounted for normalization of preset interfaces (3ff9458)
deps: update dependency conventional-commits-filter to v4 (99dcf7e)

Features

conventional-changelog-presets: supported new preset format (f3b88d3)
node-versions: raised the minimum node version to v18.17 and dropped v19 support (a681fbd)

BREAKING CHANGES

node-versions: the minimum required node version is now v18.17, v19 support has been dropped, and the minimum required in the v20 range is v20.6.1
conventional-changelog-presets: the new preset format is a breaking change when compared to the previous preset format. updating to support the new format means that the old preset format is no longer supported. update your preset to the latest version to maintain compatibility

`v10.0.4`

Compare Source

Bug Fixes

deps: update dependency conventional-commits-parser to v5 (a7201b6)

`v10.0.3`

Compare Source

Reverts

Revert "fix(deps): update dependency conventional-commits-parser to v5 (#501)" (ab3ee9f), closes #501
Revert "chore(deps): update dependency conventional-changelog-atom to v4 (#502)" (f21eb8e), closes #502
Revert "chore(deps): update dependency conventional-changelog-ember to v4 (#504)" (c48b533), closes #504

`v10.0.2`

Compare Source

Bug Fixes

deps: update dependency conventional-commits-parser to v5 (#501) (91cf4d5)

`v10.0.1`

Compare Source

Bug Fixes

deps: update dependency conventional-changelog-angular to v6 (#460) (0607201)
deps: update dependency conventional-commits-filter to v3 (#461) (97d683f)
deps: update dependency conventional-commits-parser to v4 (#462) (5d94efa)

`v10.0.0`

Compare Source

Code Refactoring

esm: converted the package to esm (b4f9865), closes #296

Features

deps: raised the peer-dependency requirement on semantic-release to v20.1.0 (e1ab8ea)
node-versions: raised the minimum required node version to v18 (affeb23)

BREAKING CHANGES

deps: the minimum required version of semantic-release is now v20.1.0 in order to support
loading ESM plugins
node-versions: the minimum required version of node is now v18
esm: @semantic-release/commit-analyzer is now a native ES Module. It has named exports
for each plugin hook (analyzeCommits)

`v9.0.2`

Compare Source

Bug Fixes

bump conventional commits parser to version 3.2.3 (#289) (fc0a88a)

`v9.0.1`

Compare Source

Bug Fixes

deps: update dependency import-from to v4 (#235) (2da0011)

`v9.0.0`

Compare Source

Features

raise minimum version of Node to v14.17 (#248) (6eeaeb2)

BREAKING CHANGES

the minimum required version of node is now v14.17

`v8.0.1`

Compare Source

Bug Fixes

package: update micromatch to version 4.0.2 (ab3e4fd)

`v8.0.0`

Compare Source

chore

require Node.js >=10.18 (3f1dfc3)

BREAKING CHANGES

Require Node.js >= 10.18

`v7.0.0`

Compare Source

Bug Fixes

use correct peerDependencies for semantic-release (4ff652f)
package: update import-from to version 3.0.0 (060dc29)

Features

add support for conventionalcommits preset (2b5ac0a)
allow to disable default release rules with release: false (ea2b204)
require Node.js >=10.13 (9f72907)
use globs instead of regexp for releases rules (fc9b28a)

BREAKING CHANGES

Require Node.js >= 10.13
Regexp are not supported anymore for property matching in the releaseRules option.

Regex are replaced by globs. For example /core-.*/ should be changed to 'core-*'.

semantic-release/git (@semantic-release/git)

`v11.0.1`

Compare Source

Bug Fixes

deps: update dependency execa to v10 (#564) (b39d5c6)

`v11.0.0`

Compare Source

Features

ES Module (#544) (4d704a2), closes #491 #490

BREAKING CHANGES

@semantic-release/git is now a native ES Module. It
has named exports for each plugin hook (verifyConditions, prepare)
the minimum required version of semantic-release to use
@semantic-release/git is now v20.1.0

`v10.0.1`

Compare Source

Bug Fixes

deps: update dependency @semantic-release/error to v3 (#295) (3e934d4)

`v10.0.0`

Compare Source

Features

node-version: raised the minimum required version to v14.17 (7ab65f8)

BREAKING CHANGES

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

`v9.0.1`

Compare Source

Bug Fixes

deps: update dependency execa to v5 (#228) (f536d60)

semantic-release/github (@semantic-release/github)

`v7.2.3`

Compare Source

Bug Fixes

improve text in comment (#367) (0aa2ba1)

`v7.2.2`

Compare Source

Bug Fixes

deps: update dependency fs-extra to v10 (1a28625)

`v7.2.1`

Compare Source

Bug Fixes

allow proxy to be false and fallback an empty string (#356) (bea917f)

`v7.2.0`

Compare Source

Features

set target_commitish when creating a GitHub release (#305) (a54e596), closes #304

`v7.1.2`

Compare Source

Bug Fixes

deps: update dependency @octokit/rest to v18 (#297) (73490fc)

`v7.1.1`

Compare Source

Bug Fixes

success: fix access to the release notes (#284) (24344df)

`v7.1.0`

Compare Source

Features

add additional release links to the release (#282) (db2e9c8), closes #281

`v7.0.7`

Compare Source

Bug Fixes

skip permission verification exception when Github Apps (#272) (32654fb)

`v7.0.6`

Compare Source

Bug Fixes

publish a release when env.GITHUB_URL is set to https://github.com (#269) (543f40b)

`v7.0.5`

Compare Source

Bug Fixes

package: update fs-extra to version 9.0.0 (884dfee)

`v7.0.4`

Compare Source

Bug Fixes

package: update @octokit/rest to version 17.0.0 (e328b76)

`v7.0.3`

Compare Source

Bug Fixes

package: update https-proxy-agent to version 5.0.0 (3a5d3e4)

`v7.0.2`

Compare Source

Bug Fixes

address @octokit/rest deprecations (#249) (c1ae4ac)

`v7.0.1`

Compare Source

Bug Fixes

package: update globby to version 11.0.0 (e055e41)

`v7.0.0`

Compare Source

chore

require Node.js >=10.18 (fb249b7)

BREAKING CHANGES

Require Node.js >= 10.18

`v6.0.2`

Compare Source

Bug Fixes

package: update http-proxy-agent to version 4.0.0 (2a0a8f8)

`v6.0.1`

Compare Source

Bug Fixes

package: update issue-parser to version 6.0.0 (b02a35b)

`v6.0.0`

Compare Source

Bug Fixes

adapt for latest @octokit/rest to remove deprecation warnings (#177) (b2bc352)
use correct peerDependencies for semantic-release (742b521)
use the branch.main flag to determine is the release need the prerelease flag (7aaeb0f)
package: update @octokit/rest to version 16.13.1 (4c756b2)
package: update aggregate-error to version 2.0.0 (7d6b7f0)
package: update aggregate-error to version 3.0.0 (2f08578)
package: update p-filter to version 2.0.0 (bab986f)
package: update p-retry to version 3.0.0 (36aab02)
package: update p-retry to version 4.0.0 (01822de)
also add comment/label to open issues (b69986f)
release debug messsage in publish (0a3ed26)
retrieve the branch name from context.branch (5f19284)
update globby to latest version (2b5e557)
update globby to latest version (c290940)
when adding labels, expect labels array to be sent in request body for GHE support (a81a825)

Features

add addChannel plugin step (589a5c4)
append assets before release (8eb8d66)
require Node.js >=10.13 (bd4322d)
support nextRelease.channel property in publish step (869c827)

BREAKING CHANGES

Require Node.js >= 10.13

semantic-release/npm (@semantic-release/npm)

`v7.1.3`

Compare Source

Bug Fixes

use NPM_CONFIG_USERCONFIG in get-registry to match auth (#362) (13200ca)

`v7.1.2`

Compare Source

Bug Fixes

deps: update dependency fs-extra to v10 (80fde1e)

`v7.1.1`

Compare Source

Bug Fixes

deps: update dependency normalize-url to v6 (97ca719)

`v7.1.0`

Compare Source

Features

use npm v7 (#304) (a15c017)

`v7.0.10`

Compare Source

Bug Fixes

improve error message text for npm tokens (#323) (88e5862)

`v7.0.9`

Compare Source

Bug Fixes

deps: update dependency execa to v5 (#299) (d4e5bb2)

`v7.0.8`

Compare Source

Bug Fixes

deps: update dependency tempy to v1 (#289) (5a1dbb8)

`v7.0.7`

Compare Source

Bug Fixes

deps: update dependency tempy to ^0.7.0 (#287) (dd25707)

`v7.0.6`

Compare Source

Bug Fixes

update required node and npm version (#273) (493fbad)

`v7.0.5`

Compare Source

Bug Fixes

package: update fs-extra to version 9.0.0 (67a3109)

`v7.0.4`

Compare Source

Bug Fixes

package: update tempy to version 0.5.0 (6ffff19)

`v7.0.3`

Compare Source

Bug Fixes

package: update tempy to version 0.4.0 (4874bf6)

`v7.0.2`

Compare Source

Bug Fixes

package: update normalize-url to version 5.0.0 (a554580)

`v7.0.1`

Compare Source

Bug Fixes

package: update semver to version 7.1.2 (a58b30b)

`v7.0.0`

Compare Source

chore

require Node.js >=10.18 (8140f0f)

BREAKING CHANGES

Require Node.js >= 10.18

`v6.0.0`

Compare Source

Bug Fixes

package: update execa to version 4.0.0 (d97dee5)
package: update semver to version 6.3.0 (c515862)
add dist-tag to publish and add-channel logs (db6ccd2)
use correct peerDependencies for semantic-release (8b47e7b)
package: pin npm to 6.5.0 (ddab7b7)
package: update aggregate-error to version 2.0.0 (df53298)
package: update aggregate-error to version 3.0.0 (3e0d5d0)
package: update execa to version 3.0.0 (b1780c1)
package: update npm to version 6.8.0 (2b0492e)
package: update read-pkg to version 5.0.0 (877ce40)
package: update vulnerable dependencies (#185) (a96c6da)
skip tarball move if config is cwd (a224497)
package: update execa to version 2.0.2 (d2932ba)
package: update registry-auth-token to version 4.0.0 (2868b2c)
add dist-tag to publish log (2de37a1)
Honor NPM_CONFIG_USERCONFIG setting (932ea5e)
package: update fs-extra to version 8.0.0 (bf603e5)
return false if the npm publish is skipped (4a41228)
return false in addChannel if package is not published on npm (5434bab)

Features

add addChannel plugin step (fb96126)
require Node.js >=10.13 (6426458)
require Node.js >=8.15 (4caf538)
support nextRelease.channel property in publish step (b8deba7)

BREAKING CHANGES

Require Node.js >= 10.13
Require Node.js => 8.15

semantic-release/release-notes-generator (@semantic-release/release-notes-generator)

`v9.0.3`

Compare Source

Bug Fixes

deps: update dependency get-stream to v6 (d8abb62)

`v9.0.2`

Compare Source

Bug Fixes

deps: update dependency into-stream to v6 (9f33802)

`v9.0.1`

Compare Source

Bug Fixes

remove duplicate debug log (14129a9)

`v9.0.0`

Compare Source

chore

require Node.js >=10.18 (97ab553)

BREAKING CHANGES

Require Node.js >= 10.18

`v8.0.0`

Compare Source

Features

require Node.js >=10.13 (c34dbc2)

BREAKING CHANGES

Require Node.js >= 10.13

Configuration

📅 Schedule: (in timezone Europe/Moscow)

Branch creation
- "after 10pm every weekday,before 5am every weekday,every weekend"
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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

github-actions · 2021-05-15T19:25:31Z

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 · 2021-05-15T19:26:01Z

🏷️ [bumpr] Next version:v1.12.1 Changes:v1.12.0...AlexRogalskiy:renovate/major-semantic-release-monorepo

renovate · 2021-10-18T17:44:05Z

⚠ 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 WARN old lockfile 
npm WARN old lockfile The npm-shrinkwrap.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: github-action-screenshot@0.0.0-dev
npm ERR! Found: @semantic-release/changelog@5.0.1
npm ERR! node_modules/@semantic-release/changelog
npm ERR!   dev @semantic-release/changelog@"^6.0.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev @semantic-release/changelog@"^6.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: semantic-release@23.0.4
npm ERR! node_modules/semantic-release
npm ERR!   peer semantic-release@">=18.0.0" from @semantic-release/changelog@6.0.3
npm ERR!   node_modules/@semantic-release/changelog
npm ERR!     dev @semantic-release/changelog@"^6.0.3" 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/2024-03-18T06_46_10_024Z-debug-0.log

viezly · 2022-03-07T09:28:26Z

Pull request by bot. No need to analyze

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Dependency Scan (universal)	3	18	8	0	❌
Secrets Audit	0	469	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Dependency Scan (universal)	3	20	9	0	❌
Secrets Audit	0	434	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Dependency Scan (universal)	3	21	9	0	❌
Secrets Audit	0	436	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Dependency Scan (universal)	3	21	9	0	❌
Secrets Audit	0	439	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Dependency Scan (universal)	3	21	9	0	❌
Secrets Audit	0	446	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Dependency Scan (universal)	3	20	9	0	❌
Secrets Audit	0	447	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Dependency Scan (universal)	3	21	9	0	❌
Secrets Audit	0	444	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Dependency Scan (universal)	3	20	9	0	❌
Secrets Audit	0	445	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

renovate · 2024-06-01T03:20:04Z

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn old lockfile
npm warn old lockfile The npm-shrinkwrap.json file was created with an old version of npm,
npm warn old lockfile so supplemental metadata must be fetched from the registry.
npm warn old lockfile
npm warn old lockfile This is a one-time fix-up, please be patient...
npm warn old lockfile
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: github-action-screenshot@0.0.0-dev
npm error Found: @semantic-release/changelog@5.0.1
npm error node_modules/@semantic-release/changelog
npm error   dev @semantic-release/changelog@"^7.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error dev @semantic-release/changelog@"^7.0.0" from the root project
npm error
npm error Conflicting peer dependency: semantic-release@25.0.9
npm error node_modules/semantic-release
npm error   peer semantic-release@">=20.1.0" from @semantic-release/changelog@7.0.0
npm error   node_modules/@semantic-release/changelog
npm error     dev @semantic-release/changelog@"^7.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-10-20T21_05_37_768Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-20T21_05_37_768Z-debug-0.log

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Dependency Scan (universal)	3	21	9	0	❌
Secrets Audit	0	433	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Dependency Scan (universal)	3	21	9	0	❌
Secrets Audit	0	431	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

socket-security · 2025-08-10T15:20:10Z

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		Obfuscated code: npm `@pnpm/network.ca-file` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/@semantic-release/changelog@7.0.0` → `npm/@semantic-release/git@11.0.1` → `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.
Warn		Obfuscated code: npm `execa` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/@semantic-release/changelog@7.0.0` → `npm/@semantic-release/git@11.0.1` → `npm/execa@9.6.1` ℹ 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/execa@9.6.1`. 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.
Warn		Obfuscated code: npm `highlight.js` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/@semantic-release/changelog@7.0.0` → `npm/@semantic-release/git@11.0.1` → `npm/highlight.js@10.7.3` ℹ 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/highlight.js@10.7.3`. 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.
Warn		Obfuscated code: npm `npm` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/@semantic-release/changelog@7.0.0` → `npm/@semantic-release/git@11.0.1` → `npm/npm@11.18.0` ℹ 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/npm@11.18.0`. 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.
Warn		Obfuscated code: npm `npm` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/@semantic-release/changelog@7.0.0` → `npm/@semantic-release/git@11.0.1` → `npm/npm@11.18.0` ℹ 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/npm@11.18.0`. 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

Scan Summary

Tool	Critical	High	Medium	Low	Status
Secrets Audit	0	499	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Secrets Audit	0	433	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

github-actions · 2026-04-27T17:53:05Z

Welcome, new contributor!

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Secrets Audit	0	495	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Secrets Audit	0	432	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

socket-security · 2026-07-21T10:04:20Z

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@semantic-release/changelog@5.0.1 ⏵ 7.0.0	⁺¹		⁺²	⁺⁶
	@semantic-release/git@9.0.0 ⏵ 11.0.1	⁺¹			⁺¹¹

View full report

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Secrets Audit	0	447	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Secrets Audit	0	446	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

renovate Bot added bump:patch labels May 15, 2021

auto-assign Bot requested a review from AlexRogalskiy May 15, 2021 19:25

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from c18ccd7 to e9b162c Compare June 15, 2021 08:11

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from e9b162c to 8df4de8 Compare October 18, 2021 17:43

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 8df4de8 to c9627aa Compare March 7, 2022 09:28

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from c9627aa to cb5169a Compare March 16, 2023 13:36

github-actions Bot reviewed Mar 16, 2023

View reviewed changes

github-actions Bot added the security findings label Mar 16, 2023

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from cb5169a to 3a197d4 Compare March 24, 2023 19:46

github-actions Bot reviewed Mar 24, 2023

View reviewed changes

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 3a197d4 to d4293f7 Compare June 3, 2023 11:48

github-actions Bot reviewed Jun 3, 2023

View reviewed changes

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from d4293f7 to 082109f Compare June 10, 2023 02:40

github-actions Bot reviewed Jun 10, 2023

View reviewed changes

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 082109f to 2c71530 Compare August 27, 2023 09:01

github-actions Bot reviewed Aug 27, 2023

View reviewed changes

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 5a306fe to 603c69b Compare August 29, 2023 11:55

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 603c69b to 68bd598 Compare September 19, 2023 23:27

github-actions Bot reviewed Sep 19, 2023

View reviewed changes

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 68bd598 to dc42872 Compare November 6, 2023 02:27

github-actions Bot reviewed Nov 6, 2023

View reviewed changes

github-actions Bot removed bump:patch labels Jan 5, 2024

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from dc42872 to 8f71c9d Compare March 18, 2024 06:46

github-actions Bot added the security findings label Mar 18, 2024

github-actions Bot reviewed Mar 18, 2024

View reviewed changes

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 8f71c9d to c6aa10a Compare June 1, 2024 03:19

github-actions Bot reviewed Jun 1, 2024

View reviewed changes

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from c6aa10a to 76dcadf Compare January 3, 2025 04:53

github-actions Bot reviewed Jan 3, 2025

View reviewed changes

github-actions Bot removed the security findings label Mar 4, 2025

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 76dcadf to bccedc3 Compare August 10, 2025 15:19

github-actions Bot added the security findings label Aug 10, 2025

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from bccedc3 to c0c0780 Compare March 27, 2026 05:46

github-actions Bot reviewed Mar 27, 2026

View reviewed changes

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from c0c0780 to 371d248 Compare March 30, 2026 18:31

github-actions Bot reviewed Mar 30, 2026

View reviewed changes

github-actions Bot removed the security findings label Apr 18, 2026

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 371d248 to 73514b1 Compare April 27, 2026 17:31

github-actions Bot reviewed Apr 27, 2026

View reviewed changes

github-actions Bot added the security findings label Apr 27, 2026

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 73514b1 to 73ee5f4 Compare April 27, 2026 23:49

github-actions Bot reviewed Apr 27, 2026

View reviewed changes

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from 73ee5f4 to b6cd051 Compare July 21, 2026 10:03

github-actions Bot reviewed Jul 21, 2026

View reviewed changes

⬆️ Updates semantic-release monorepo

afb6460

renovate Bot force-pushed the renovate/major-semantic-release-monorepo branch from b6cd051 to afb6460 Compare July 24, 2026 05:59

github-actions Bot reviewed Jul 24, 2026

View reviewed changes

Conversation

renovate Bot commented May 15, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Features

BREAKING CHANGES

Other Notable Changes

Related Issue

Bug Fixes

Bug Fixes

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

Bug Fixes

Features

BREAKING CHANGES

Features

BREAKING CHANGES

Features

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

Reverts

Bug Fixes

Bug Fixes

Code Refactoring

Features

BREAKING CHANGES

Bug Fixes

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

chore

BREAKING CHANGES

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

chore

BREAKING CHANGES

Bug Fixes

Bug Fixes

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

renovate Bot commented May 15, 2021 •

edited

Loading