Repository navigation
fix: declare packagePath so the release version script can sync plugin.json - #15
Merged
Merged
Conversation
…n.json Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: unional <homawong@gmail.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.
Summary
The release job failed at
npm run version(run 35752740639):universal-plugin publish sync-versionreads the package location from.agents/universal-plugin.json, and that file did not exist. This PR adds it with"packagePath": ".", because the package is at the repo root.Verification
Locally,
universal-plugin publish sync-versionanduniversal-plugin plugin buildboth succeed with this file in place.🤖 Generated with Claude Code