From dc7ef6d8e849cfc049a64344e073e4831f37c25e Mon Sep 17 00:00:00 2001 From: RobertoIskandarani Date: Fri, 7 Aug 2026 13:07:53 -0300 Subject: [PATCH] docs: record 0.1.0 in the changelog on main release.yml deletes the release branch, so the version heading only ever lives on the tag. The section here is a byte-for-byte copy of the tagged one. The runbook now spells out this step and the next-dev bump merge, which were both undocumented. --- CHANGELOG.md | 2 ++ RELEASE_SETUP.md | 4 +++- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 57df20c..8ab6fc3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## [Unreleased] +## [0.1.0] - 2026-08-07 + ### Added - Explicit RFC 9449 §4.3 #1 enforcement: the new diff --git a/RELEASE_SETUP.md b/RELEASE_SETUP.md index 9fff315..c07a2f1 100644 --- a/RELEASE_SETUP.md +++ b/RELEASE_SETUP.md @@ -58,7 +58,9 @@ End-to-end happy path: - atomic-pushes branch + tag using the Release Bot token, - creates the GitHub Release with notes extracted from CHANGELOG, - deletes the source branch. -4. **`publish-nuget.yml` triggers automatically** on the tag push. It builds, packs, and pushes `Authplane.Sdk` then `Authplane.Mcp` to NuGet. The `nuget` environment gates the publish. +4. **`publish-nuget.yml` triggers automatically** on the tag push. It builds, packs, and pushes `Authplane.Sdk` then `Authplane.Mcp` to NuGet. The `nuget` environment gates the publish: a `maintainers` reviewer has to approve the deployment before anything reaches nuget.org. +5. **Record the release in the default branch's changelog.** `release.yml` deletes the source branch, so the `## [X.Y.Z]` heading only ever exists on the tag — the default branch still says `## [Unreleased]`. Open a follow-up PR that renames it and opens a fresh empty `## [Unreleased]` above. The `## [X.Y.Z]` section on the default branch must be a byte-for-byte copy of the tagged one; if the notes need correcting after the fact, edit the GitHub Release body, never the published section. +6. **Merge the next-dev bump PR** that step 1 opened. It carries the `-pre.N` bump for the default branch, and it does not auto-merge (`allow_auto_merge` is off on this repository), so it needs a manual merge like any other PR. ## 6. Hotfix flow