chore(deps): pin semantic-release as a devDependency - #19
Merged
Conversation
The release workflow runs `npx semantic-release`, which resolves and executes the package from the registry at run time in a job holding a write-scoped GITHUB_TOKEN. Pinning it to the lockfile means the release job runs a reviewed, checksummed version. The lockfile churn is large because adding a dependency to a lockfile this stale re-resolves every transitive. No runtime dependency versions were changed by hand. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
omar-sr88
approved these changes
Aug 10, 2026
omar-sr88
left a comment
omar-sr88
left a comment
Collaborator
There was a problem hiding this comment.
I checked the dependencies with claude for something dangerous/out of the ordinary and nothing was found. So im giving this a good to go
|
🎉 This PR is included in version 1.5.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
2 participants
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.
The release workflow runs
npx semantic-release, resolving and executing the package from the registry at run time in a job that holds a write-scopedGITHUB_TOKEN. Pinning it to the lockfile means the release job runs a reviewed, checksummed version.The lockfile diff is large (+13.6k/−5.1k) and that is the whole reason this is its own PR. Adding a single dependency to a lockfile this stale re-resolves every transitive. No dependency versions were changed by hand — only
semantic-release: ^25.0.9was added todevDependencies.Verified locally:
npm ci --ignore-scriptsclean, 26/26 tests pass, all three lambda zips build,semantic-release25.0.9 resolves fromnode_modules.The safe-chain workflow change is stacked on top of this in a separate PR.
🤖 Generated with Claude Code