Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 15, 2024

This PR contains the following updates:

Package Change Age Confidence
semantic-release ^22.0.12 -> ^25.0.0 age confidence

Release Notes

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

v25.0.2

Compare Source

Bug Fixes

v25.0.1

Compare Source

Bug Fixes

v25.0.0

Compare Source

Bug Fixes
  • deps: update dependency hosted-git-info to v9 (9fa04f8)
  • deps: update dependency yargs to v18 (#​3745) (cde9a72)
  • deps: update to the stable version of the github plugin (f12cf81)
  • deps: update to the stable version of the release-notes-generator plugin (d9def72)
  • deps: updated to the stable version of the commit-analyzer plugin (291533b)
  • deps: upgrade to the new major version of the npm plugin, which upgrades npm to v11 for publishing (1be8290)
Features
  • node-versions: drop support for node versions v20, v21, and v23 (56d16f4)
  • node-versions: raise the minimum node version for the v24 range (116a188)
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • node-versions: a minimum of node v22.14 is now required

v24.2.9

Compare Source

Bug Fixes

v24.2.8

Compare Source

Bug Fixes

v24.2.7

Compare Source

Performance Improvements

v24.2.6

Compare Source

Bug Fixes

v24.2.5

Compare Source

Bug Fixes
  • deps: raise the minimum of the defined range for marked-terminal (#​3742) (fb1ccd4)

v24.2.4

Compare Source

Bug Fixes

v24.2.3

Compare Source

Bug Fixes

v24.2.2

Compare Source

Bug Fixes

v24.2.1

Compare Source

Bug Fixes

v24.2.0

Compare Source

Features
  • clarify branch existence requirement in error messages (#​3462) (05a2ea9)

v24.1.3

Compare Source

Bug Fixes
  • branch-naming: prevent non-range versions from being identified as maintenance branches (07f2672)

v24.1.2

Compare Source

Bug Fixes

v24.1.1

Compare Source

Bug Fixes

v24.1.0

Compare Source

Features

v24.0.0

Compare Source

Bug Fixes
  • deps: upgraded to the beta of the commit-analyzer plugin (dfc3d91)
  • deps: upgraded to the beta of the release-notes-generator plugin (4a4cd92)
BREAKING CHANGES
  • deps: the commit-analyzer plugin now expects to be used with the latest major versions of
    conventional-changelog packages. if you are installing any of these packages in addition to
    semantic-release, be sure to update them as well
  • deps: the release-notes-generator plugin now expects to be used with the latest major
    versions of conventional-changelog packages. if you are installing any of these packages in addition
    to semantic-release, be sure to update them as well

v23.1.1

Compare Source

Bug Fixes

v23.1.0

Compare Source

Features

v23.0.8

Compare Source

Bug Fixes
  • deps: rename read-pkg-up -> read-package-up (4980cba)
  • deps: rename read-pkg-up -> read-package-up (#​3249) (95a8b9e)

v23.0.7

Compare Source

Bug Fixes
  • deps: update dependency find-versions to v6 (6a2b6bb)

v23.0.6

Compare Source

Bug Fixes

v23.0.5

Compare Source

Bug Fixes

v23.0.4

Compare Source

Bug Fixes

v23.0.3

Compare Source

Bug Fixes

v23.0.2

Compare Source

Bug Fixes

v23.0.1

Compare Source

Bug Fixes
  • deps: update dependency marked-terminal to v7 (9faded8)

v23.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES

related to https://github.com/semantic-release/semantic-release/discussions/3088


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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 renovate bot changed the title chore(deps): update dependency semantic-release to v23 chore(deps): update dependency semantic-release to v24 Jun 1, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from faa8aca to cbba47d Compare June 1, 2024 08:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from cbba47d to 114f7d0 Compare August 13, 2025 08:11
@socket-security
Copy link

socket-security bot commented Aug 13, 2025

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedsemantic-release@​25.0.29810010097100

View full report

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 114f7d0 to 688a140 Compare August 23, 2025 00:05
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 688a140 to b8d8d8d Compare September 1, 2025 10:56
@socket-security
Copy link

socket-security bot commented Sep 1, 2025

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 npm is 94.0% likely obfuscated

Confidence: 0.94

Location: Package overview

From: pnpm-lock.yamlnpm/[email protected]npm/[email protected]

ℹ 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 [email protected].

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/[email protected]. 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

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from b8d8d8d to 43c5616 Compare September 11, 2025 04:14
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 614e6dd to e3ac7f9 Compare September 26, 2025 20:05
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 chore(deps): update dependency semantic-release to v25 Oct 16, 2025
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 9c88ac5 to 84f5c09 Compare October 20, 2025 07:48
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 84f5c09 to 7969534 Compare October 25, 2025 11:46
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7969534 to fe8eaae Compare November 8, 2025 19:45
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from fe8eaae to ce5cc88 Compare November 16, 2025 23:45
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ce5cc88 to 6e1c403 Compare December 4, 2025 22:26
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.

1 participant