Repository navigation
fix(publish): sync-version moves the skills' pins of the synced package - #166
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 458dcc2 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 |
unional
force-pushed
the
up-164-sync-pins
branch
2 times, most recently
from
October 11, 2026 08:42
bf97c56 to
e11fc7b
Compare
…sion sync-version left `npx --yes <pkg>@0.8.0` and `npx -y <pkg>@0.8.0` in skills/** behind the version it synced. It now re-pins the synced package's references through bundle's own rewriter, with a version source that resolves only that package, so other packages' pins and pin-exempt skills stay as authored. Refs #164 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
unional
force-pushed
the
up-164-sync-pins
branch
from
October 11, 2026 08:44
e11fc7b to
458dcc2
Compare
This was referenced Oct 11, 2026
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.
Refs #164 (item 3)
publish sync-versionnow rewrites thenpx/upx <pkg>@<version>pins in the plugin's skills directory (including the--yesand-yspellings) for the package it synced from, using thatpackage.json'sname.plugin bundle's rewriter (bundlePins) with a version source that resolves only the synced package. Pins of other packages and pin-exempt skills are left as authored.--no-builddoes not skip it. Output gains apinnedfield.publish/sync-versionspec node, because the spec places the sync engine out of charter. publish sync-version leaves vendor manifests stale, and no skill routes to build-plugin #143 recorded sync-version's behavior as prose inplugin/version/README.md, so this PR does the same rather than adding a.featureto a node that doesn't exist.plugin versionalready rewrites these pins (feat(plugin): addplugin version— bump the canonical manifest and every version-carrying file in sync #32). It does not;plugin bundleowns them. This PR doesn't changeplugin version.syncSkillPinsand the package name, plus a CLI e2e.pnpm verifypasses (743 tests).🤖 Generated with Claude Code