chore(deps): update dependency universal-plugin to ^0.12.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
universal-plugin (source)	^0.11.0 → ^0.12.0

---

Release Notes

cyberuni/universal-plugin (universal-plugin)

v0.12.1

Compare Source

Patch Changes

• da18173: Depend on @cyberuni/agent-harness ^0.5.0. That release ships the agent-harness CLI, so npx @cyberuni/agent-harness reference show <name> reads this package's documents without a version pin.
• 1904555: Point reference loading at the cyber-agent-harness plugin. The reference skill moved there from buddy-agent-harness in buddy-agent-harness@​0.20.0, so the shipped skills and references now name cyber-agent-harness, and the plugin declares it as a dependency.

v0.12.0

Compare Source

Minor Changes

• c82b27b: plugin build now 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 in allowCrossMarketplaceDependenciesOn, warns and names the fix. Pass --strict-dependencies to fail the build on it instead. A dependency that declares a source, such as { "name": "cyber-asana", "source": { "source": "npm", "package": "cyber-asana" } }, is listed in the catalog for you.
• 602e1c8: plugin build no longer warns about a dependency qualified with the catalog's own name, such as cyber-asana@uip-pods-local, when the catalog does not list it. Only a plain dependency (a bare name, or an object with no marketplace) has to be listed in the catalog. Naming a marketplace is an explicit choice by the author.
• f87bfc8: marketplace validate now 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 no marketplace) the catalog does not list is an issue, and so is a dependency on another marketplace that the catalog does not allow in allowCrossMarketplaceDependenciesOn. It reads what is on disk: an entry's own dependencies, and the manifest of a plugin at a ./ source. marketplace init --force now keeps a catalog's allowCrossMarketplaceDependenciesOn when it regenerates the file.
• b0558cd: The publish-plugin skill 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's allowCrossMarketplaceDependenciesOn.

v0.11.3

Compare Source

Patch Changes

• 4a0e9ac: doctor no longer reports com.github.copilot/ as stale after a rebuild. It compares the newest file in the directory against plugin.json, because a directory's own mtime does not move when its files are rewritten in place.
• 4a0e9ac: publish sync-version now re-derives the vendor manifests after it moves the version, the same way plugin version does, so they no longer keep the old number. Pass --no-build to skip that step when your release script runs plugin build itself. The version and doctor-universal-plugin skills now name build-plugin as the follow-up step.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: ca444e5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR