Repository navigation
Give the version bump a pnpm it can find - #23
Merged
Merged
Conversation
pnpm/action-setup@v4 with no `version:` resolves one out of package.json. There is no package.json at the repository root and no packageManager field in pipeline's, so the step fails — and the only run it ever reaches is the one where a missed version bump is already the problem being fixed. Pinned to 9, as validate.yml has been all along. Co-Authored-By: Claude Opus 5 <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.
The
Bump plugin versionworkflow fails at itsSetup pnpmstep. Reproduced on main:pnpm/action-setup@v4with noversion:input resolves one frompackage.json. There isno
package.jsonat the repo root and nopackageManagerfield inpipeline/'s, so thestep cannot resolve anything.
validate.ymlalready pinsversion: 9; this does the same.Only reached when the version did not already move in the push, so the one run where it
matters is the one where a missed bump is already the problem being fixed — skill content
lands on main and nothing reaches an installed plugin. Today's run passed only because
#22 carried its own bump and the workflow short-circuited before this step.
Split out of the one-plugin branch so it can land now rather than behind a large review.
🤖 Generated with Claude Code