🚨 [security] Update semantic-release 17.4.7 → 25.0.2 (major) #600
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ semantic-release (17.4.7 → 25.0.2) · Repo
Security Advisories 🚨
🚨 Exposure of Sensitive Information to an Unauthorized Actor in semantic-release
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by 27 commits:
fix(deps): update dependency read-package-up to v12 (#3935)Merge pull request #3931 from Simek/patch-1Merge pull request #3932 from Deltamir/docs-add-semantic-release-uv-community-pluginMerge pull request #3920 from semantic-release/installationupdate Node version in `npx` command exampledocs(plugins): add semantic-release-uv community plugin in plugins listdocs: Update minimal required Node versionchore(deps): update dependency @types/node to v24.10.0 (#3929)chore(deps): lock file maintenance (#3928)chore(deps): update dependency got to v14.6.2 (#3927)chore(deps): update node.js to v24 (#3923)ci(action): update github/codeql-action action to v4.31.2 (#3925)ci(action): update github/codeql-action action to v4.31.1 (#3924)chore(deps): update dependency @types/node to v24 (#3922)docs: update GitHub Actions documentation for Trusted Publisher (#3913)chore(deps): lock file maintenance (#3921)chore(deps): update dependency semantic-release to v25 (#3903)docs(installation): update recommendations to align with advice provided as support for some timechore(deps): update dependency got to v14.6.1 (#3919)ci(action): update actions/upload-artifact action to v5 (#3918)docs(plugins): add @jno21/semantic-release-github-commit (#3914)ci(action): update github/codeql-action action to v4.31.0 (#3917)Merge pull request #3916 from pynickle/docs/semantic-release-minecraftdocs(plugin): add semantic-release-minecraft to plugin listchore(deps): update dependency @types/node to v22.18.12 (#3915)chore(deps): update dependency publint to v0.3.15 (#3912)chore(deps): lock file maintenance (#3911)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands