Skip to content

docs(changelog): cut the 1.0.0-rc.10 section - #127

Merged
xerj-org merged 1 commit into
mainfrom
docs/rc10-changelog
Aug 2, 2026
Merged

docs(changelog): cut the 1.0.0-rc.10 section#127
xerj-org merged 1 commit into
mainfrom
docs/rc10-changelog

Conversation

@xerj-org

@xerj-org xerj-org commented Aug 2, 2026

Copy link
Copy Markdown
Owner

Closes the Unreleased section as 1.0.0-rc.10 and records the 31 commits merged since rc.9.

Grouped as Added / Fixed / Performance, alongside the runtime-field Changed, Security and Breaking entries that were already staged from the console and cluster hardening.

Two things stated rather than smoothed over

The max_buckets entry is marked partial. #125 fixed the histogram paths, but exec_terms still has no bucket cap at all, and that is the half that actually matters for memory safety — measured at cap 37 over 200 distinct terms, the fast path materialised all 200. Writing it as closed would be a claim the code does not support.

The date-parse entry records the interim regression. #91#96 went through a scan-based guard that made 64 KB values 16x slower than having no guard, before the bounded six-byte window replaced it. The shipped 217.0 → 110.2 ns/op number is only meaningful against that history.

Also restores the blank line before the ### Security heading, which an earlier conflict resolution removed while merging two entries into one section.

Not included

Release mechanics — the version bump in engine/Cargo.toml, the tag, and the 8-target build matrix — are deliberately not in this PR. This is the changelog only, so it can land independently of the cut.

Closes the Unreleased section as rc.10 and records the 31 commits merged since
rc.9, grouped as Added / Fixed / Performance alongside the runtime-field
Changed, Security and Breaking entries that were already staged.

Two things stated rather than smoothed over: the max_buckets entry is marked
partial, because exec_terms still has no bucket cap and that is the half that
actually matters for memory safety; and the date-parse entry records that an
interim scan-based guard regressed long values 16x before the bounded window
replaced it, since the shipped number is only meaningful against that.

Also restores the blank line before the Security heading, which an earlier
conflict resolution removed while merging two entries into one section.
@xerj-org
xerj-org merged commit cadd94d into main Aug 2, 2026
9 checks passed
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