ROADMAP: v0.12 shipped, and benchmarks struck rather than deferred - #45
Merged
Merged
Conversation
Most of the v0.12 line was already true when the milestone opened: fuzzing, CodeQL, signed artifacts, concurrency stress, failure injection and upgrade testing all shipped earlier. What was genuinely missing was property tests and an SBOM, and both are here. Benchmarks are struck from the line, not carried forward. postgres.md withholds a throughput figure on purpose and soak.mdx says three times that its number is not one to plan against; a benchmark suite manufactures exactly the figure those pages decline to give. A test is owed by a claim, and there is no performance claim here to defend. The import-cycle item is closed, and it was not the public-surface question the roadmap assumed: re-exporting kept every frozen name, so nothing public moved. T180's allow-list gains one line from the new CHANGELOG entry. "Signed" there is the distribution, signed by release.yml's attestation step, not a receipt, which is the distinction T180 exists to hold. Signed-off-by: arpan <contact@arpanghoshal.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review. 📝 WalkthroughWalkthroughThe documentation now reports v0.12.0 and 6,221 tests. It records the shipped hardening milestone and SBOM, updates verification examples, and allow-lists the related changelog sentence. Changesv0.12 Release Documentation
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Merge Risk: ⚪ Minimal · up to The documentation changes introduce no confirmed correctness, security, or availability risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
The version moved and the quoted output did not. `test_every_quoted_verify_transcript_is_one_verify_actually_prints` runs verify and compares, which is why CI caught it. It should have been caught locally and was not: the docs venv still had 0.11.0 installed from another worktree, because the editable install that was supposed to point it at the release branch had failed on shell quoting and I did not read its output. The gate passed against the wrong library. Re-run against 0.12.0, every generator and audit is clean. Signed-off-by: arpan <contact@arpanghoshal.com>
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.
Pairs with the kernel release PR.
Most of the v0.12 line was already true when the milestone opened: fuzzing, CodeQL, signed artifacts, concurrency stress, failure injection and upgrade testing all shipped in earlier milestones. What was genuinely missing was property tests and an SBOM, and both are here.
Benchmarks are struck from the line rather than carried forward.
postgres.mdwithholds a throughput figure on purpose andsoak.mdxsays three times that its number is not one to plan against. A benchmark suite manufactures exactly the figure those pages decline to give, and a test is owed by a claim. There is no performance claim in this project to defend.The import-cycle item is closed, and it was not the public-surface question the roadmap assumed: re-exporting kept every frozen name.
T180's allow-list gains one line from the new CHANGELOG entry: "signed" there is the distribution, signed by
release.yml's attestation step, not a receipt, which is the distinction T180 exists to hold.🤖 Generated with Claude Code
Summary by CodeRabbit