AX-2134: unify release trigger on version-file diff - #69
Merged
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Keeps the version-file release trigger from this branch and drops the old commit-subject marker behavior entirely, while preserving main's unrelated work and its latest vendored skills. Conflicts were limited to the two version manifests. Both are set to 0.6.4, the next unused patch after the v0.6.3 release tag, so merging this PR cuts a clean release. The skill-governance release gate main added carried an `if:` condition on the now-removed marker-detection step; it is unconditional here so it actually runs, matching every other gate in the job. Co-authored-by: Cursor <cursoragent@cursor.com>
YoniMelki
force-pushed
the
feature/AX-2134-unified-release-mechanism
branch
from
September 3, 2026 08:52
d779f31 to
82bf1d8
Compare
davida-jfrog
previously approved these changes
Sep 3, 2026
Bring in the hook payload change and its revert, SH support for the opencode plugin agent name, the skills v0.36.0 pin, the README version removal, and the new agent-guard and bridge-client fallback test suites. Both version manifests conflicted on the version line only. Resolved to 0.6.8, the next unused patch above the latest release tag v0.6.7, so merging this branch still cuts a real release. plugin.json and marketplace.json stay identical, as validate-version requires. Release behaviour is unchanged: the canonical latest-tag lookup, the already-released and revert gates, the unconditional skill-governance validation, and the gh release view/delete rollback all stay as they were on the branch. Main's rewritten vendor-refresh docs listed only plugin.json for the version bump. Under the unified mechanism a PR that bumps one manifest without the other fails validate-version, so README.md and VENDOR.md now say to sync both, matching CONTRIBUTING.md and adding no version numbers. Co-authored-by: Cursor <cursoragent@cursor.com>
YoniMelki
force-pushed
the
feature/AX-2134-unified-release-mechanism
branch
from
September 7, 2026 07:48
ad2678c to
1256359
Compare
davida-jfrog
approved these changes
Sep 7, 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
2 participants
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.
Summary
release.ymlfrom commit-subject markers to comparingplugins/jfrog/.cursor-plugin/plugin.json(cross-checked with marketplace.json) against the latest strictvX.Y.Ztag.mainand bump 0.6.3 → 0.6.4 in both manifests so merge is a real release.Part of AX-2134.
Landing
Merging cuts v0.6.4. After that, every merge to
mainmust bump both manifests or Release fails by design.Test plan
release.zip.