Version Packages - #85
Merged
Merged
Conversation
unional
force-pushed
the
changeset-release/main
branch
from
September 17, 2026 19:35
f806c5c to
ba9a392
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
universal-plugin@0.9.0
Minor Changes
plugin buildcopies each governance into the skills that use it, so a skill reads its rule sets from disk instead of runningnpx <pkg> governance show <name>at run time — no registry lookup per read, and no network while the skill works. The.mdfiles already in<skill>/references/governances/declare which governances that skill uses; the build rewrites each from the package that owns it, copies the governances those reference, transitively, and rewrites everygovernance show <other>pointer inside a copy into an instruction to load the sibling copy. The build fails when a declared file names no governance, when a referenced one has no copy to point at, or whenSKILL.mddoes not list a copy under References. Commit the copies — a git-sourced install has no build step — and run the newplugin build --checkin CI, which writes nothing and exits non-zero naming each copy that differs from its source.doctorskill todoctor-universal-plugin. Other plugins ship their owndoctorskill, and the bare name collided when more than one was installed —buddy-agent-harnessalready resolved this by namespacing its own asdoctor-buddy-agent-harness. Invoke it as/universal-plugin:doctor-universal-plugin; the CLI's own next-step hints now name that too.