chore: finalize v0.13.1 CHANGELOG for release#240
Merged
Conversation
- Set the [0.13.1] release date to 2026-06-19 (was a stale 2026-06-01 placeholder; the release had not shipped on that date). - Record the tier-1 documentation work that landed after the entry was first written: README/CONTRIBUTING accuracy pass, REPO-INSTRUCTIONS.md removal, and the XML-doc <example> corrections from the code-review pass. Docs-only; version stays 0.13.1 (no public API or runtime change). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Final release-prep for v0.13.1 before vNext (#192) merges to main. Docs-only — no public API or runtime change, so the version stays 0.13.1 (PATCH).
Why
The
[0.13.1]CHANGELOG entry was written early in the canonical round and had drifted from what's actually on vNext:REPO-INSTRUCTIONS.mdremoval, and the code-review XML-doc fixes via tier1: README accuracy pass (#171, #168) #233 / tier1: Markdown audit — drop stale REPO-INSTRUCTIONS, fix analyzer list (#172) #234 / tier1: fix XML-doc inaccuracies from code-review pass (#161) #235 / tier1: recover orphaned doc fixes into vNext (CONTRIBUTING header + #235) #236) wasn't recorded.Changes
[0.13.1]date to 2026-06-19 (today / release-cut date).REPO-INSTRUCTIONS.md(post-setup bootstrap checklist).<example>references (MaxItemCount→MaximumItemCount,ManualProgressTimer→IProgressTimer).Release readiness (verified)
<Version>=0.13.1, last shipped tag =v0.13.0→ clean PATCH bump.<AssemblyVersion>1.0.0.0</AssemblyVersion>+ prerelease-safe<FileVersion>intact (C4 binding stability).[Unreleased]section left empty per Keep-a-Changelog.After this merges into vNext, #192 (vNext → main) is the release; tag
v0.13.1to firerelease.yaml.