From 281a874e0f31e3533efde11497fc3a44966133b4 Mon Sep 17 00:00:00 2001 From: "Ronald A. Richardson" Date: Thu, 10 Sep 2026 11:49:53 +0800 Subject: [PATCH] chore: prepare 1.3.0 release recovery --- CHANGELOG.md | 3 ++- docs/release-checklist.md | 4 ++-- docs/releases/1.3.0.md | 4 +++- 3 files changed, 7 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 61a1aeb..7f6210d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,7 +8,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0. ## [Unreleased] -## [1.3.0] - 2026-09-09 +## [1.3.0] - 2026-09-10 ### Added @@ -25,6 +25,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0. - Contract tests now use canonical placeholder names for legacy envelopes when scenario URLs spell the same identifier differently. - Restored the complete PHP example catalog required by the website's Postman submodule update. +- Pinned the validated Xdebug coverage driver and retried delayed GitHub merge metadata so release validation and automatic release detection remain reliable. ## [1.2.0] - 2026-09-06 diff --git a/docs/release-checklist.md b/docs/release-checklist.md index 269db82..c4c7267 100644 --- a/docs/release-checklist.md +++ b/docs/release-checklist.md @@ -12,7 +12,7 @@ The release workflow starts automatically when a semantic `release/` branch is m ## Repository preparation -1. Create `release/v1.3.0`, update its dated changelog section and `docs/releases/1.3.0.md`, and open a pull request to `main`. +1. Create `release/1.3.0` from `main` after the workflow repairs, update its dated changelog section and `docs/releases/1.3.0.md`, and open a recovery pull request to `main`. The original `release/v1.3.0` attempt did not publish a release. 2. Require every pull-request check, including the disposable 264-request SDK contract, before merge. 3. Configure required checks and the protected `release` environment without granting workflow bypasses. 4. Add `POSTMAN_API_KEY` at repository or organization scope and retain the live-contract artifacts. @@ -20,7 +20,7 @@ The release workflow starts automatically when a semantic `release/` branch is m ## Publication -1. Merge the reviewed `release/v1.3.0` pull request into `main`; this automatically starts the release workflow and derives version `1.3.0`. +1. Merge the reviewed `release/1.3.0` recovery pull request into `main`; this automatically starts the repaired release workflow and derives version `1.3.0`. 2. Confirm the live SDK contract and validation jobs pass, then approve the protected `release` environment if an approval rule is configured. 3. Confirm the immutable `1.3.0` tag and GitHub Release target the reviewed commit and contain the expected artifacts and provenance. 4. Verify GitHub and Packagist identify `AGPL-3.0-or-later` for 1.3.0 while 1.0.x tags retain their original MIT terms. diff --git a/docs/releases/1.3.0.md b/docs/releases/1.3.0.md index 29cccd5..ad6855d 100644 --- a/docs/releases/1.3.0.md +++ b/docs/releases/1.3.0.md @@ -11,4 +11,6 @@ New actions follow the existing positional-ID, direct-data, final-request-option The release retains PHP 7.4 and PHP 8.x support and the `AGPL-3.0-or-later` license. Published releases and their tags are unchanged. -Merging the reviewed `release/v1.3.0` branch into `main` starts the existing release workflow, which reruns validation and the disposable SDK contract before publication. +Release automation now pins the validated Xdebug 3.5.3 coverage driver and retries GitHub's merged-PR lookup. The 100% line and branch coverage requirements are unchanged. + +The original 1.3.0 attempt did not publish a tag or package. Merging the reviewed recovery branch `release/1.3.0` into `main` starts a fresh release run with these fixes, reruns validation and the disposable SDK contract, and retains the protected release environment before publication. The version remains 1.3.0; no published tag is replaced.