Repository navigation
release: cut v1.1.0 - #40
Merged
Merged
Conversation
Rolls the Unreleased section into `## [1.1.0] — 2026-09-11` and bumps `project(protowire VERSION ...)` to 1.1.0. The three `### Fixed` headers that accumulated under Unreleased are merged into one; entry text is unchanged (verified: identical non-header line set). Minor, not major: every new parameter (`pb::UnmarshalOptions`, `sbe::CodecOptions`, `pxf::ParseOptions`, the five pxf limit fields) is defaulted and `IsIdentifierSafe` is retained beside `IsIdentifierSafeEntryName`, so v1.0 callers compile unchanged. Claude-Session: https://claude.ai/code/session_01EUW2Rq9zr1kXxiiDi12QK7
Step 4 said `.github/workflows/release.yml` builds artifacts and posts the GitHub Release. The repository has only ci.yml and codeql.yml, and v0.70.0, v0.75.0 and v1.0.0 were each published by hand with a written body. Say that, so the next release does not wait on a workflow. Claude-Session: https://claude.ai/code/session_01EUW2Rq9zr1kXxiiDi12QK7
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
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.
Cuts v1.1.0 per the CONTRIBUTING release recipe: rolls
## [Unreleased]into## [1.1.0] — 2026-09-11and bumpsproject(protowire VERSION ...)to 1.1.0. Tagv1.1.0and the GitHub Release follow the merge.Why minor. Every new parameter is defaulted (
pb::UnmarshalOptions,sbe::CodecOptions,pxf::ParseOptions, the five pxf limit fields) andIsIdentifierSafestays exported besideIsIdentifierSafeEntryName, so v1.0 callers compile unchanged. The lockstep clause no longer binds: the sibling ports are at go v1.8.1, java v1.2.0, typescript v1.2.0, kotlin v1.0.0.What ships (13 commits since v1.0.0): keyed repeated fields and quoted entry names (#18); the HARDENING mandatory limits enforced per call in pxf, pb and sbe with the adversarial corpus green on all 38 rows (#26, #25); packed repeated numerics in pb (#32); import-closure bind-time validation (#34); zero-valued map entries (#24); map-key quoting and bool-key spellings (#27, #36); fractional and µs durations (#20); extension renumbering into the registered 1314-1363 block (#21).
Evidence. Changelog roll-up verified as a pure reorder: the sorted non-header line set of the section is identical before and after.
cmake -S . -B buildon the branch writesPACKAGE_VERSION "1.1.0"intoprotowireConfigVersion.cmake. Head of main (c221b3b) has CI and CodeQL green; this PR's ownbuildcheck is the gate.Also fixed
release.ymlworkflow that does not exist; it now describes the by-handgh release createstep the last three releases used.https://claude.ai/code/session_01EUW2Rq9zr1kXxiiDi12QK7