Skip to content

Release 1.4.0 (2026-04-24)

Features

  • rewrite publish skill for poll-and-merge; bump composite pins to v1.2; plugin 1.4.0 (#70) Step 3 of 3 for the poll-and-merge rework (plugin#57).

Three coordinated changes:

skills/publish/SKILL.md

  • New "Policy: agent-driven merges for release-workflow PRs" section up front. Explicitly names the two PRs the agent is allowed to merge (release PR and bump PR) and frames every other PR as human-merged.
  • States that the release workflow is not complete until the bump PR is merged — that step prepares the repo for the next cycle and is part of this skill's responsibility.
  • Phase 2 was "Review and merge" (passive wait). Now "Merge release PR": st-docker-run -- st-merge-when-green <url> with explicit failure-propagation language.
  • Phase 4 was "Confirm version bump" (passive wait). Now "Merge bump PR": poll for the chore/bump-version-<next> URL, then st-merge-when-green. Callout that the bump PR is typically green before the publish workflow run finishes, so Phase 4 can overlap with Phase 3 verification.
  • TOC updated to match new headings.

.github/workflows/publish.yml

  • tag-and-release pin bumped @v1.1 -> @v1.2.
  • version-bump-pr pin bumped @v1.1 -> @v1.2. This is the coordinated opt-in into the new "composite doesn't auto-merge; skill does" behavior — must land together with the skill rewrite, which is why it's in this same PR.

.claude-plugin/plugin.json

  • 1.3.2 -> 1.4.0. Minor: behavior change in the skill; this release is the fleet's opt-in trigger.

Verification

This PR itself is a release-workflow dogfood: 1. Manual review of the skill prose (no executable code beyond workflow pin changes, which are mechanical). 2. After merge, the v1.4.0 release cycle runs through the updated publish.yml. That cycle will exercise both the new @v1.2 composite (creates but does not merge the bump PR) and the new skill phases (agent merges both release PR and bump PR via st-merge-when-green).