Skip to content

docs: record 0.1.0 in the changelog on main - #15

Open
RobertoIskandarani wants to merge 1 commit into
mainfrom
docs/record-0.1.0-changelog
Open

docs: record 0.1.0 in the changelog on main#15
RobertoIskandarani wants to merge 1 commit into
mainfrom
docs/record-0.1.0-changelog

Conversation

@RobertoIskandarani

Copy link
Copy Markdown
Collaborator

Summary

Post-release bookkeeping for 0.1.0, and the two runbook steps that turned out to be missing while shipping it.

Changes

  • CHANGELOG.md: the ## [0.1.0] heading only ever existed on the tag, because release.yml deletes the release branch after tagging. This records it on the default branch and opens a fresh empty ## [Unreleased] above it. The ## [0.1.0] section is a byte-for-byte copy of the tagged one — verified by diffing both against each other.
  • RELEASE_SETUP.md §5: added steps 5 and 6. Step 5 is the changelog record above, with the rule that corrections after the fact go in the GitHub Release body rather than in the recorded section. Step 6 is the manual merge of the next-dev bump PR, which does not auto-merge because allow_auto_merge is off on this repository. Step 4 also now mentions that the nuget environment requires a maintainers approval before anything reaches nuget.org.

Test Plan

Documentation only; no code, workflows or packaging touched.

  • The recorded ## [0.1.0] section was diffed against git show v0.1.0:CHANGELOG.md — identical, 212 lines.
  • ## [Unreleased] is present again on the default branch, which cut-release.yml requires for the next cut.

Checklist

  • dotnet build / dotnet format / dotnet test — n/a, no source or project files touched
  • Tests added for new functionality — n/a
  • Documentation updated
  • CHANGELOG.md entry added — this PR is the changelog entry
  • New workflow actions are SHA-pinned — no workflow changes
  • No token values, secrets, or key material in logs or test fixtures

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.
@RobertoIskandarani
RobertoIskandarani requested a review from a team as a code owner August 7, 2026 16:12
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.

1 participant