Skip to content

Back-merge hotfix #179 into staging - #193

Merged
Niels Laute (niels9001) merged 3 commits into
stagingfrom
backmerge/hotfix-sync-adapter-versions
Sep 25, 2026
Merged

Niels Laute (niels9001) merged 3 commits into
stagingfrom
backmerge/hotfix-sync-adapter-versions

Conversation

@Jaylyn-Barbee

Copy link
Copy Markdown
Contributor

Description

Brings hotfix #179 (Hotfix: sync Claude/Codex adapter manifest versions (0.6.1)) back into staging, restoring the ancestry the staging-up-to-date-with-main gate requires.

main was 2 commits ahead of staging and had never been back-merged, so every feature PR targeting staging currently fails that check — see #192, which is blocked on exactly this.

This merge is content-neutral

git diff origin/staging HEAD is empty. Staging already carried the equivalent change via #180, so this merge only repairs commit ancestry — it changes no files. All five version fields remain consistent at 0.6.1:

Manifest Version
plugins/winui/agent-plugin/plugin.json 0.6.1
plugins/winui/.claude-plugin/plugin.json 0.6.1
plugins/winui/.codex-plugin/plugin.json 0.6.1
.github/plugin/marketplace.json 0.6.1 / 0.6.1
.claude-plugin/marketplace.json 0.6.1 / 0.6.1

Type of Change

  • 🔧 Config / build / CI

Affected area

  • Repo-level docs / governance

⚠️ Merge as a merge commit — do not squash

The staging-up-to-date-with-main gate evaluates git rev-list --count origin/main ^HEAD. Squashing or rebasing flattens the two parents, drops the link to main, and leaves the gate failing exactly as it does now — the back-merge would accomplish nothing.

This branch uses the required backmerge/ prefix so the version-sync check skips it, per CONTRIBUTING.md § Back-merge path.

Additional Notes

Once this lands, #192 needs a rebase onto the updated staging.

The Agent Plugins 1.0 package migration bumped plugins/winui/agent-plugin/plugin.json,
.github/plugin/marketplace.json, and .claude-plugin/marketplace.json to 0.6.0,
but left plugins/winui/.claude-plugin/plugin.json and
plugins/winui/.codex-plugin/plugin.json at 0.3.0 -- neither the release
helper nor CI tracked them. This blocks the Claude Code plugin submission
in MARKETPLACE-DISTRIBUTION.md, which requires the Claude adapter manifest
to carry the release version.

- Bump all 7 version fields to 0.6.1 (patch, per the hotfix path in
  CONTRIBUTING.md -- no user-facing behavior changed).
- Add the two adapter manifests to open-release-pr.ps1's Set-JsonField
  calls so future releases keep them in sync automatically.
- Add the two adapter manifests to the version-sync and version-bump CI
  jobs in release-policy.yml (now checks 7 fields, not 5).
- version-bump's main-side drift check stays advisory (::warning::, no
  exit) rather than hard-failing: Rule 1 already forces all 7 PR-head
  fields into sync, and a hard fail on main-side drift would deadlock this
  exact corrective PR against the inconsistency it's fixing.
- Update RELEASING.md/CONTRIBUTING.md field counts and CHANGELOG.md.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Hotfix: sync Claude/Codex adapter manifest versions to 0.6.1
@niels9001
Niels Laute (niels9001) merged commit a026db9 into staging Sep 25, 2026
11 checks passed
@niels9001
Niels Laute (niels9001) deleted the backmerge/hotfix-sync-adapter-versions branch September 25, 2026 13:33
Jaylyn Barbee (Jaylyn-Barbee) added a commit that referenced this pull request Sep 25, 2026
Back-merge main into staging (merge commit, not squash) — replaces #193
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants