Release Apache Magpie 0.1.0

[potiuk]

Release: Apache Magpie 0.1.0

Release Manager: Jarek Potiuk (potiuk)
Release train: 0.x (single active train off main)
Base branch: main
Previous release: none — this is the first Apache Magpie release

In scope

Initial Apache Magpie release — full history since repo inception
(676 merged PRs into main; first commit 2026-04-28), reflecting main
at 73d94cd0 (includes the 13 PRs merged 2026-07-08: #763–#786). As the
first release there is no previous tag to diff against, so scope is the
entire 0.x groundwork rather than an enumerated PR delta.

Steps

• Step 1: Planning issue open ← this issue
• Step 2: Prep PR open — done via chore(release): first-release groundwork + prep for 0.1.0 #712 (chore(release): first-release groundwork + prep for 0.1.0, merged; pyproject.toml at 0.1.0)
• Step 3: KEYS reconciliation (release-keys-sync)
• Step 4–5: RC cut + stage (release-rc-cut 0.1.0 rc1)
• Step 6: Pre-flight verify (release-verify-rc 0.1.0-rc1)
• Step 7: [VOTE] thread (release-vote-draft 0.1.0-rc1)
• Step 8: Voting window
• Step 9: Tally (release-vote-tally 0.1.0-rc1)
• Step 10: Promote (release-promote 0.1.0-rc1)
• Step 11: Announce + site bump (release-announce-draft 0.1.0)
• Step 12: Archive sweep (release-archive-sweep)
• Step 13: Audit log (release-audit-report 0.1.0)
• Step 14: Post-release bump (release-prepare post 0.1.0)

Artefacts

• Staging URL: (TBD — release-rc-cut)
• Tag URL: (TBD — release-rc-cut)
• RC artefact list: (TBD)

Timestamps

• Planning issue opened: 2026-07-07
• KEYS synced: 2026-07-07 — RM signing key 8BA8D21BB4A2350A43680A7466187A61A0A7E894 (Jarek Potiuk (apache) <potiuk@apache.org>, RSA 4096; signing subkey B31140BB… on YubiKey) committed to dist/release/magpie/KEYS; dist areas dist/dev/magpie + dist/release/magpie provisioned. (Replaced an interim Ed25519 key 673ED6A6… that the RM does not hold locally.)
• Prep PR opened: chore(release): first-release groundwork + prep for 0.1.0 #712 (merged before this planning issue was filed)
• RC staged: (TBD)
• Vote opened: (TBD)
• Vote closed: (TBD)
• Promote commit: (TBD)
• [ANNOUNCE] sent: (TBD)

---

Restart (2026-07-08): the RC is being re-cut on latest main (73d94cd0).
The earlier 0.1.0-rc1 was cut at 2f0a21c1, before 13 PRs (#763–#786) merged
2026-07-08; the 0.1.0-rc1 tag is being moved to current main so the
release reflects that work. RC-onward steps (4–6) are being redone and the
previously staged rc1 artefacts replaced. Prep (#712) and KEYS sync remain valid.

Note: Steps 1 and 2 ran out of order for this first release — the prep
PR (#712) merged before this tracking issue was filed. This issue now
serves as the lifecycle hub for the remaining steps (3–14).

Generated by release-prepare (magpie-release-prepare).

[potiuk]

RC cut: 0.1.0-rc1

• Tag: https://github.com/apache/magpie/releases/tag/0.1.0-rc1 (8e791e08, signed)
• Staging: https://dist.apache.org/repos/dist/dev/magpie/0.1.0-rc1/
• Artefacts: apache-magpie-0.1.0-source.zip (+ .asc, .sha512) — canonical source; Magpie is a source-only release (no convenience binaries)
• Signing key: 8BA8D21BB4A2350A43680A7466187A61A0A7E894 — Jarek Potiuk (apache) potiuk@apache.org, in KEYS
• Digest: SHA-512

Next: release-verify-rc 0.1.0-rc1 (RAT scan + signature/checksum verification + binary-exclude check) before the [VOTE] thread.

_{Recorded by release-rc-cut (magpie-release-rc-cut).}

[potiuk]

RC re-cut: 0.1.0-rc1 (moved to latest main)

• Tag: 0.1.0-rc1 → 9a54cbb8 (re-cut on latest main; was 2f0a21c1) — https://github.com/apache/magpie/releases/tag/0.1.0-rc1
• Staging: https://dist.apache.org/repos/dist/dev/magpie/0.1.0-rc1/ (re-staged)
• Artefacts: apache-magpie-0.1.0-source.zip (+ .asc, .sha512) — canonical source, source-only release
• Signing key: 8BA8D21BB4A2350A43680A7466187A61A0A7E894 — Jarek Potiuk (apache), in KEYS
• Digest: SHA-512

This RC now reflects main through 9a54cbb8 (all 0.x groundwork incl. #763–#789). Next: release-verify-rc 0.1.0-rc1.

_{Recorded by release-rc-cut (magpie-release-rc-cut).}

[potiuk]

RC verification: 0.1.0-rc1 — ✅ PASS

release-verify-rc pre-flight against the staged RC (dist/dev/magpie/0.1.0-rc1/, tag 9a54cbb8):

Check	Result
Inventory	✅ apache-magpie-0.1.0-source.zip + .asc + .sha512
GPG signature	✅ Good signature — Jarek Potiuk (apache), key 8BA8D21B… (in KEYS)
SHA-512	✅ OK
Apache RAT 0.18 (license headers)	✅ 0 unapproved (real run against the unpacked artefact; 2,220 approved)
NOTICE / LICENSE	✅ both present at artefact root
Binary exclusion	✅ 0 prohibited binaries
Version consistency	✅ pyproject.toml = 0.1.0

Overall: PASS. Mechanical pre-flight aid only — a PASS does not discharge a voter's ASF obligation to download, build, and test the candidate before a binding +1. Next: [VOTE].

[potiuk]

RC re-cut from latest main. The earlier 0.1.0-rc1 tag was invalid (stale commit / wrong tagger), so the RC was rebuilt from scratch:

• Tag: 0.1.0-rc1 now points to f638e3b92bd8d987b01210bfc54bc7b523586482 (latest main, chore(agent-isolation): bump pinned socat 1.8.1.3, claude-code 2.1.202 #790).
• Staging: https://dist.apache.org/repos/dist/dev/magpie/0.1.0-rc1/ (re-staged: apache-magpie-0.1.0-source.zip + .asc + .sha512).
• Content re-verified: pyproject.toml = 0.1.0; NOTICE + LICENSE present at root; no prohibited binaries; 6003 files.
• Still to confirm on the RM's machine before the [VOTE]: git verify-tag 0.1.0-rc1 (Good signature from Jarek Potiuk 8BA8D21B…) + gpg --verify + sha512 -c.

Supersedes the earlier RC-cut note above.