feat: lock semantic-release publish dependencies#1327
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
samcx
approved these changes
May 27, 2026
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.
We have a problem where semantic-release is only called in ci.yml but it doesnt have a lockfile which means transitive dependencies could change.
I think the reason it was set up this way is to avoid slowing down CI for PRs that don't publish since they wont need to install semantic-release (40MB). Only main needs to publish.
The fix is to add a new publish directory with its own lock file, then we can install and invoke the bin from the publish directory to ensure dependencies are locked.