Repository navigation
Version Packages - #149
Merged
Merged
Version Packages#149
Conversation
unional
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
October 5, 2026 00:31
5332219 to
a537f2f
Compare
unional
force-pushed
the
changeset-release/main
branch
from
October 5, 2026 01:05
a537f2f to
24972c2
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
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.12.0
Minor Changes
plugin buildnow checks each declared dependency against the marketplace catalogs it refreshes. A bare dependency the catalog does not list, or one qualified with a marketplace the catalog does not allow inallowCrossMarketplaceDependenciesOn, warns and names the fix. Pass--strict-dependenciesto fail the build on it instead. A dependency that declares asource, such as{ "name": "cyber-asana", "source": { "source": "npm", "package": "cyber-asana" } }, is listed in the catalog for you.plugin buildno longer warns about a dependency qualified with the catalog's own name, such ascyber-asana@uip-pods-local, when the catalog does not list it. Only a plain dependency (a bare name, or an object with nomarketplace) has to be listed in the catalog. Naming a marketplace is an explicit choice by the author.marketplace validatenow checks, in the Claude catalog, that each listed plugin's dependencies can resolve from it. A plain dependency (a bare name, or an object with nomarketplace) the catalog does not list is an issue, and so is a dependency on another marketplace that the catalog does not allow inallowCrossMarketplaceDependenciesOn. It reads what is on disk: an entry's owndependencies, and the manifest of a plugin at a./source.marketplace init --forcenow keeps a catalog'sallowCrossMarketplaceDependenciesOnwhen it regenerates the file.publish-pluginskill now reads the plugin's dependencies. A plain dependency the target marketplace does not list is listed in the same PR, or the skill stops and asks for it to be published first. A dependency on another marketplace gets an offer to add it to the catalog'sallowCrossMarketplaceDependenciesOn.