Repository navigation
Record v0.16.0 publication and begin 0.16.1 development - #124
Merged
Merged
Conversation
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.
Summary
Record the verified v0.16.0 publication and advance development to 0.16.1.dev0.
Publication evidence
No runtime or frozen result changes. All 39 historical result/evidence JSON/JSONL files are byte-identical. The existing v0.16.0 tag and earlier tags are unchanged.
Validation
Release-state and generated PyPI checks, Ruff, format, mypy (180 modules), actionlint, Markdown/text checks and strict MkDocs build pass.
.audit/v016-sync-screenshots/. Hosted screenshots are retained as CI artifacts.Hosted CI/build/docs/bridge must be green before merge.