Skip to content

docs(changelog): catch up [Unreleased] section with 2026-05-26 session work#72

Merged
CryptoJones merged 1 commit into
masterfrom
docs/changelog-catchup-2026-05-26
May 26, 2026
Merged

docs(changelog): catch up [Unreleased] section with 2026-05-26 session work#72
CryptoJones merged 1 commit into
masterfrom
docs/changelog-catchup-2026-05-26

Conversation

@CryptoJones
Copy link
Copy Markdown
Owner

CHANGELOG.md's [Unreleased] section wasn't updated as PRs landed throughout the day. Adding a single dated section (2026-05-26) that records the 28 PRs merged this session, grouped by Rec:

  • Rec 28: ignoreAudit Stage 2 strict, 17 author-declared-not-a-regression-test deletions, tracking-issue re-file, inventory honesty refresh.
  • Rec 31: cppRaiiAudit per-file gate (Stage 1), marshal.cc RAII Stage 2A, Stage 2C design doc.
  • Rec 13/14: OSS-Fuzz primary_contact fill-in, in-tree/upstream sync, upstream PR (google/oss-fuzz#15545) submitted.
  • CI / housekeeping: sync-labels live mode, 26-branch sweep.
  • Doc sync: SprintPlanning.md marshal-shipped + std::span deviation acknowledged.

Also noted the three in-flight PRs (#50/#51/#52) that landed-as-CI but didn't merge yet, so they appear as "queued" rather than as shipped work.

Also fixes a stale "Work toward v26.1.10" header — v26.1.10 already shipped (per the Released section); [Unreleased] is now toward v26.1.11.

Surfaced when you (correctly) asked whether I was remembering to put PRs in changelog. I wasn't.

Proudly Made in Nebraska. Go Big Red! 🌽 https://xkcd.com/2347/

…n work

CHANGELOG.md's [Unreleased] section wasn't updated as PRs landed
throughout the day. Adding a single dated section (2026-05-26)
that records the 28 PRs merged this session, grouped by Rec:

  - Rec 28: ignoreAudit Stage 2 strict, 17 author-declared-not-a-
    regression-test deletions, tracking-issue re-file, inventory
    honesty refresh.
  - Rec 31: cppRaiiAudit per-file gate (Stage 1), marshal RAII
    Stage 2A, Stage 2C design doc.
  - Rec 13/14: OSS-Fuzz primary_contact fill-in + in-tree/upstream
    sync + upstream PR (google/oss-fuzz#15545) submitted.
  - CI / housekeeping: sync-labels live mode, 26-branch sweep.
  - Doc sync: SprintPlanning marshalshipped + std::span deviation.

Also noted the three in-flight PRs (#50/#51/#52) that landed-as-CI
but didn't merge yet, so they appear as "queued" rather than as
shipped work.

Also fixes a stale "Work toward v26.1.10" header — v26.1.10
already shipped (per the Released section); [Unreleased] is now
toward v26.1.11.

Proudly Made in Nebraska. Go Big Red! 🌽 https://xkcd.com/2347/

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@CryptoJones CryptoJones merged commit 1e1ac5c into master May 26, 2026
10 of 11 checks passed
@CryptoJones CryptoJones deleted the docs/changelog-catchup-2026-05-26 branch May 26, 2026 07:44
CryptoJones added a commit that referenced this pull request May 26, 2026
…leased] (#76)

The catch-up changelog PR (#72) listed #50, #51, #52 as in-flight.
Now resolved:

  - #51 (lvalue) — merged (was the lone in-flight item that landed
    cleanly).
  - #50 (CodeQL fix) — superseded by #74 after the stacking mistake.
    #74 landed and Analyze (c-cpp) now passes on master.
  - #52 (global_scan) — superseded by #73 after the same stacking
    mistake. #73 landed.
  - #75 (Apologies) — landed alongside, recording the chain.

Removes the "in flight" footnote and replaces with a paragraph
explaining the chain of events so readers understand why #50 / #52
are absent from the merged ledger and #73 / #74 are present
covering the same scope.

Aaron's per-PR changelog feedback (feedback_changelog_per_pr.md)
applied: this PR ships its own changelog touch alongside the actual
state change, not as a catch-up.

Proudly Made in Nebraska. Go Big Red! 🌽 https://xkcd.com/2347/

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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