Use the 'UpdateVersionBranch' and 'CheckMarketplaceMetadata' job templates

[pytooling-claude]

Important

The pipeline on this branch is red, and will stay red until
pyTooling/Actions#260 is merged into dev. Both new jobs
reference ...@dev, and those two templates exist only on #260's branch so far, so GitHub rejects the workflow file
before any job starts — the run has zero jobs, not a failing one. Merging #260 to dev turns this green with no
change here.

Bug Fixes

• ⚠️ The version-branch pull-request targeted v6; this repository publishes v7. The hand-written
  Create Pull-Request job hard-coded it:

  title="Update v6 from ${{ needs.Prepare.outputs.version }}"
  gh pr create --base v6 --head main --title "${title}" --body "Auto generated"

  So every release proposed updating a branch that consumers stopped pinning 1 major version(s) ago, and
  v7 was left to be moved by hand. Replacing it with the job template removes the constant: the branch is
  derived, and the body says which release it carries and links the compare.

Changes

• UpdateVersionBranch replaces the hand-written job — 38 lines of inline shell become 13 lines of
  instantiation. Beyond the fixed branch, it also creates the branch when a new major appears, rewrites references to
  this repository so the version branch names itself rather than main, and retitles the pull-request still open
  from a previous release instead of failing to create a duplicate.

  It is passed major: '7', because this repository tags releases v1.x.y while publishing a v7
  branch — the branch number isn't the released version's major. That parameter was added to the template because of
  this repository; the original assumed the two matched.

• CheckMarketplaceMetadata runs on every push, and TriggerTaggedRelease now waits for it, so a release
  can't be tagged with metadata the Marketplace would reject.

  Checked against this repository as it stands: the description is 72 of the 125 allowed characters, the
  branding icon and colour are accepted, and action.yml is at the root. Nothing to fix — but pyTooling/SynchronizeForks
  v1.0.0 was refused for a 127-character description, and that is discovered in the publish form, months after the
  wording changed.

• Both templates are pinned @dev until pyTooling/Actions releases them, with a comment saying so. The rest
  of the pipeline stays on @r7. This is the documented way to prove a template in a real repository before it is
  released.

Others

• Not changed here, worth a decision: this repository's release pages are written by hand — no
  PublishReleaseNotes job, and the last release body carries no pyTooling/Actions footer. Adding it would make
  the release description come from the release pull-request automatically, the way pyTooling/pyTooling and
  pyTooling/SynchronizeForks do it. That changes how releases are written, so it isn't folded in silently.

---

Related Issues and Pull-Requests

• Depends on pyTooling/Actions#260, which adds both templates.
  Once it is released, the two @dev references become @r8.

🤖 Generated with Claude Code