Skip to content

docs(changelog): sync [Unreleased] with main (#253–#262)#264

Merged
memtomem merged 1 commit intomainfrom
docs/changelog-sync-unreleased
Apr 18, 2026
Merged

docs(changelog): sync [Unreleased] with main (#253–#262)#264
memtomem merged 1 commit intomainfrom
docs/changelog-sync-unreleased

Conversation

@memtomem
Copy link
Copy Markdown
Owner

Summary

Backfills 8 [Unreleased] entries in CHANGELOG.md for PRs merged to main without a CHANGELOG update. These commits shipped to main between v0.1.9 (2026-04-13) and the 0.1.10 release preparation (#263), and their entries will land in the next release (0.1.11 / 0.2.0), not 0.1.10.

This is a follow-up hygiene PR to #263 (0.1.10 security release prep) and must merge before the release session's "UNRELEASED → date" commit, so that [Unreleased] reflects the full main state at tag time.

Scope

Net diff: +54 lines, 0 removals.

Classification rationale

Keep-a-changelog convention:

#256 and #258 are narratively linked (both improve save correctness via comparand-based drop); cross-reference is baked into the #258 bullet ("Extends #256's class-level default drop by broadening the comparand").

Sources

All 8 bullets drafted from gh pr view <N> --json title,body — no commit-subject paraphrase. Fact-checks performed:

Out of scope

Gate runs

ruff check / ruff format --check trivially pass (CHANGELOG-only text diff, no Python changes).

Backfills 8 PRs (#253, #254, #255, #256, #257, #258, #259, #262)
merged to main between v0.1.9 and 0.1.10 release prep (#263) without
CHANGELOG entries. Entries land in the next release, not 0.1.10.

- Added: #253 (NamespacePolicyRule), #254 (wizard Preserved summary),
  #255 (mm init --fresh), #259 (mm config unset)
- Changed: #256 (save drops default-valued fields)
- Fixed: #257 (list[BaseSettings] mutation coercion), #258 (fragment/
  env drag-in on save), #262 (atomic config.json writes)
@memtomem memtomem merged commit 9887516 into main Apr 18, 2026
7 checks passed
@memtomem memtomem deleted the docs/changelog-sync-unreleased branch April 18, 2026 23:16
@github-actions github-actions Bot locked and limited conversation to collaborators Apr 18, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants