Repository navigation
Release workflow: bootstrap before setup-node - #811
Merged
Merged
Conversation
…xists post-bootstrap v3.0.0 and v3.2.0 both failed at setup-node: cache-dependency-path js/package-lock.json is created by bootstrap.rb, which ran after setup-node. Reorder so the lock file exists when the cache is configured.
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.
The monorepo release failed at setup-node for v3.0.0 and v3.2.0: the npm cache path (js/package-lock.json) is created by bootstrap.rb, which ran after setup-node. Reorder. Then tag v3.2.0 on main triggers the gem release.