Publish v0.5.14 when plugin.json is untagged

[sverdlov93]

Overview

main already has plugin 0.5.14 and skills v0.25.0, but there is no v0.5.14 GitHub Release, so Cursor Marketplace cannot ingest this drop. This PR does not bump the version.

The Release job no longer reads [patch] / [minor] / [major] from the squash subject. That depended on GitHub squash settings and PR-title rewrites (Claude shipped, Cursor skipped). The gate is now the tag:

• plugin.json version has no vX.Y.Z tag → publish
• tag already exists → skip
• workflow_dispatch on a tagged version → fail (no re-tag)

Merging this PR publishes v0.5.14 because that version is already on main and still untagged. The squash title does not matter.

Flow

flowchart TD
  push["push to main or workflow_dispatch"]
  read["Read plugin.json version"]
  tagged{"tag vX.Y.Z exists?"}
  dispatch{"workflow_dispatch?"}
  publish["Create GitHub Release + tag"]
  skip["Skip"]
  fail["Fail: bump manifests first"]
  push --> read --> tagged
  tagged -->|no| publish
  tagged -->|yes| dispatch
  dispatch -->|no| skip
  dispatch -->|yes| fail

Loading

Notes

• Do not bump plugin.json / marketplace.json. Both are already 0.5.14.
• After merge, confirm the Release workflow created v0.5.14 with release.zip. Cursor.com can still lag GitHub after that.
• Claude and VS Code still use the marker. Same tag-based gate should be copied there in follow-ups (those versions are already tagged, so a merge of this workflow alone will skip, not publish).

[sverdlov93]

Closing this in favor of a manual GitHub Release: https://github.com/jfrog/cursor-plugin/releases/tag/v0.5.14

v0.5.14 is published from main (#65) with release.zip. The tag-based Release workflow is a real change — leaving that for the plugin team.