Skip to content

chore: backfill CHANGELOG sections for v0.1.1, v0.2.0, v0.2.1, v0.3.0#114

Open
avrabe wants to merge 1 commit into
mainfrom
chore/changelog-backfill
Open

chore: backfill CHANGELOG sections for v0.1.1, v0.2.0, v0.2.1, v0.3.0#114
avrabe wants to merge 1 commit into
mainfrom
chore/changelog-backfill

Conversation

@avrabe
Copy link
Copy Markdown
Contributor

@avrabe avrabe commented May 15, 2026

Hygiene fix only. The CHANGELOG had a single sprawling [Unreleased] block that mixed content shipped across four releases (v0.1.1 / v0.2.0 / v0.2.1 / v0.3.0). Split into per-version sections matching the actual git tag history.

[Unreleased] is now empty and ready for v0.3.1 entries (mentions in-flight PRs #113 + Phase 1 safety as context).

No semantic changes; existing [0.1.0] block preserved as-is. +107 -28 lines.

Hygiene fix only. The CHANGELOG had a single sprawling `[Unreleased]`
block that mixed content shipped in v0.1.1 (M7 hardening, AAPCS regalloc
fixes, --relocatable, clippy hygiene), v0.2.0 (RISC-V GA), v0.2.1
(memset silicon fix), and v0.3.0 (AAPCS audit + optimisations + fuzz +
safety policy + spectre policy). Split into per-version sections
matching the actual `git tag` history. `[Unreleased]` is now empty and
ready for v0.3.1 entries.

No semantic changes; existing `[0.1.0]` block is preserved as-is.
@codecov
Copy link
Copy Markdown

codecov Bot commented May 15, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

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