Repository navigation
Conversation
Add `publish check-version`, a read-only check that exits 1 when the packagePath package.json, plugin.json, the derived vendor manifests, the repository catalogs, or the skill npx/upx pins disagree, naming each file. doctor asks it and reports one version-drift finding per file, and the doctor skill offers to add the check to the repo's verify script or CI. Refs #164 (item 5) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: e7eebdc The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This branch has not been deployed
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
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.
Refs #164 (item 5)
What
universal-plugin publish check-version: a new read-only command. It exits 1 when any file that carries the plugin version disagrees with the release's number, and it names each disagreeing file. The release's number comes from thepackagePathpackage.jsonwhen one is declared, otherwise fromplugin.json. The command compares:plugin.json(a manifest with noversiondrifts when the package has one)npx/upx <pkg>@<ver>, with-yor--yes). Pins are read withplugin bundle's reader. Pin-exempt skills and pins that aren't versions (<version>,latest) are skipped.sync-version,plugin build, orplugin bundle.doctor: askscheck-versionfor the comparison and reports oneversion-driftfinding per file. When the CLI is too old to have the command,doctorfalls back to comparing the two authored files.doctorstays advisory and always exits 0.doctor-universal-pluginskill: when it finds drift, it checks whether the repo already runscheck-version. If not, it offers to add it to theverifyscript or the CI workflow, and asks before editing either.check-versionsection and scenarios toplugin/version(README and.feature) and an amendment note to ADR-0010 §6. The website docs and a changeset are included.Notes
src/version/drift.ts. It reusesextractPinsandisPinExemptand adds no new pin reader, so a sibling change that makessync-versionrewrite pins shouldn't conflict beyondpublish/cli.ts.Tests
src/version/drift.test.ts: unit tests for the comparisonsrc/publish/check-version.test.mts: CLI tests on a monorepo git fixture, including the issue's 0.9.0/0.8.0 casesrc/doctor-script.test.mts: one finding per drifted file, and drift with no npm packagepnpm verifypasses (759 tests)🤖 Generated with Claude Code