Repository navigation
ci(release): pack without installing dependencies - #99
Merged
Merged
Conversation
Closed
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 run for v1.1.0 failed in
pack(run 39511071405): uppt/pack refuses to install dependencies when the repo has no lockfile and nopackageManagerfield, and this repo deliberately has neither (.npmrcsetspackage-lock=false).Changed: the
packjob in.github/workflows/release.ymlnow passesinstall: falseto uppt/pack and sets up Node 24 itself withactions/setup-nodev7.1.0, pinned by SHA like the other actions in this file. No published package has aprepackorpreparescript, sonpm packneeds no dependencies. Running uppt'spack.tslocally against the v1.1.0 tree with nonode_modulespacked all 8 workspaces.Also replaced a comment that pointed to a "Lifecycle scripts" section that doesn't exist.