fix(ci): re-setup bun after upstream merge to handle version bumps#37
Merged
fix(ci): re-setup bun after upstream merge to handle version bumps#37
Conversation
When upstream bumps the bun version in package.json, the pre-push hook rejects the push because the CI runner still has the old version from initial setup. Re-run setup-bun after merge/resolution to pick up any version changes before tests and push. Closes #30 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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.
When upstream bumps the bun version in package.json, the pre-push hook rejects the push because the CI runner still has the old version from initial setup. Re-run setup-bun after merge/resolution to pick up any version changes before tests and push.
Closes #30
What does this PR do?
Please provide a description of the issue (if there is one), the changes you made to fix it, and why they work. It is expected that you understand why your changes work and if you do not understand why at least say as much so a maintainer knows how much to value the pr.
If you paste a large clearly AI generated description here your PR may be IGNORED or CLOSED!
How did you verify your code works?