docs(changelog): add v1.6.0 release notes#51
Merged
Conversation
Move the §7.3 min_timestamp freshness-hint gate entry from [Unreleased] to [v1.6.0]. Release-prep for the v1.6.0 tag (conformance-harness + specification only; no proto/wire change from v1.5.0). Closes the min_timestamp thread: providers bump their harness pin to v1.6.0 to activate the gate in CI.
|
The latest Buf updates on your PR. Results from workflow CI / lint (pull_request).
|
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
1 participant
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.
Release-prep for v1.6.0 — moves the §7.3 min_timestamp freshness-hint gate (#50) from
[Unreleased]to[v1.6.0]. Same shape as the v1.5.0 prep (#43): docs-only, version is tag-derived via hatch-vcs.v1.6.0 is conformance-harness + specification only — no proto/wire change from v1.5.0. It carries the §7.3 clarification + the
test_min_timestamp_hint_is_not_fatalgate. Cutting it lets all three providers bump their harness pin and activate the min_timestamp gate in CI (the providers are already behavior-converged: sim/bread/ezo all pass it locally).Once merged, I'll tag
v1.6.0to trigger the release workflow, then open the provider pin-bump PRs. Refs #49.