Bump plugin.json to 1.0.0 for the nauro 1.0.0 release#16
Merged
Conversation
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.
Why
nauro 1.0.0 is published to PyPI. The
version-syncgate requiresplugin.jsonto match the latest published nauro, so the plugin bumps in lockstep with the CLI release. CI onmainis red until this lands.What changed
plugin.jsonversion0.13.3->1.0.0. No agent or skill body changes: the bundled agents already byte-match the nauro 1.0.0 render, so this is version-only.Test plan
Verified locally against all three
version-syncjobs:plugin.jsonversion (1.0.0) equals the latest published nauro on PyPI (1.0.0).nauro render-plugin . --checkwithnauro==1.0.0pinned: rendered agents match the bundled source.claude plugin validate . --strict: validation passed.