Repository navigation
docs(matrix): bring release markers up to cachekit-py 0.23.0 and cachekit-rs 0.11.0 (LAB-10702) - #208
Conversation
…it-rs PR Sixteen markers called a PR unreleased that a published release carries: four cachekit-py PRs (0.21.0, 0.23.0) and twelve cachekit-rs markers (0.11.0), checked with git tag --contains on each merge commit and against the PyPI wheels and crates.io .crate files. Footnote 16's py/ts release notes gain the rs floor. The TypeScript test-vectors cell and footnote 16 called the cachekit-rs and cachekit-ts python-frame.json copies the current revision; both hash to the protocol#180 revision, one behind main.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
Summary by CodeRabbit
WalkthroughThe changelog and feature matrix update Python and Rust release markers, compliance entries, and protocol-vector coverage. They also record Python and TypeScript markers that remain unchanged. ChangesSDK release markers
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Possibly related PRs
Merge Risk: ⚪ Minimal · up to
|
Code Review Completed! 🔥The code review was successfully completed based on your current configurations. Kody Guide: Usage and ConfigurationInteracting with Kody
Providing Context (Files & MCPs)Add these hints in your PR description (or a comment) to unlock deeper checks:
Current Kody ConfigurationReview OptionsThe following review options are enabled or disabled:
|
Code Review Completed! 🔥The code review was successfully completed based on your current configurations. Kody Guide: Usage and ConfigurationInteracting with Kody
Providing Context (Files & MCPs)Add these hints in your PR description (or a comment) to unlock deeper checks:
Current Kody ConfigurationReview OptionsThe following review options are enabled or disabled:
|
|
@coderabbitai review |
✅ Action performed
|
What
Release markers only. Sixteen markers in
sdk-feature-matrix.mdcalled a PR unreleased that a published release carries; each now names the first release that carries it. Three phrases called an SDK'spython-frame.jsoncopy "the current revision" when it vendors an older one; each now names that revision. No cell's status or claim changes otherwise.expired_entryread)X-TTL, fractional TTLs)main, unreleased" becomes "Compliant"refresh_ttl)main" reworded tooFootnote 16 also has four "(py since 0.23.0, ts since npm 0.2.1)" notes on fixtures that cachekit-rs vendors in cachekit-io/cachekit-rs#146 and #152. Leaving rs out read as unreleased, so each gains "rs since 0.11.0".
python-frame.json: the TypeScript "Test vectors in CI" cell (cachekit-io/cachekit-ts#230) and footnote 16 (cachekit-io/cachekit-rs#160, cachekit-io/cachekit-ts#230) now name the cachekit-io/protocol#180 revision.Left as they are, still correct: the markers naming cachekit-io/cachekit-py#618 and #627, because PyPI's latest is 0.24.1 and the 0.25.0 release PR (cachekit-io/cachekit-py#619) is still open. Also the TypeScript markers naming cachekit-io/cachekit-ts#240 and #245, which wait on an npm release whose bindings embed
cachekit-core0.7.0, and the historical "🚧 Unreleased" sentence under the Reliability table. The Python Wire format (ByteStorage) cell is not touched.Verification
git tag --contains <merge commit>for each PR: py#397 first inv0.21.0; py#514, #520 and #550 first inv0.23.0; rs#140, feat(conformance): requirement ids, a requirement-to-vector index and per-SDK coverage (LAB-8002) #142, docs(matrix): record the reject vectors and every vendored fixture the SDKs' CI runs (LAB-8075) #146, docs(matrix): state what each SDK's CI runs for the File backend vectors (LAB-8073) #147, feat(conformance): index saas-api.md (LAB-8078) #150, feat(conformance): index intent-presets.md (LAB-8079) #152, feat(conformance): record cachekit-ts path-encoding 1.2.0 and freshness-headers 1.0.0 (LAB-8244) #158 and docs(conformance): record cachekit-py's path-encoding 1.2.0 and freshness-headers 1.0.0 copies (LAB-8254) #160 first incachekit-rs-v0.11.0. None are in the release before.>=expiry reads and the py#520_wire_seconds/ no-X-TTLpath in 0.23.0, but not in 0.22.0. They have py#397's empty key in_RESERVED_KEY_SEGMENTSin 0.21.0, but not in 0.20.0. The crates.io 0.11.0.crate(.cargo_vcs_info.jsonat the tag commit) has rs#147'stry_lead, rs#142'sttl_wire_secsinrefresh_ttland rs#140's trailing-byte rejection, plus every vendored vector file and test from docs(matrix): record the reject vectors and every vendored fixture the SDKs' CI runs (LAB-8075) #146 / feat(conformance): index saas-api.md (LAB-8078) #150 / feat(conformance): index intent-presets.md (LAB-8079) #152 / feat(conformance): record cachekit-ts path-encoding 1.2.0 and freshness-headers 1.0.0 (LAB-8244) #158 / docs(conformance): record cachekit-py's path-encoding 1.2.0 and freshness-headers 1.0.0 copies (LAB-8254) #160. 0.10.0 has none of them.python-frame.jsonsha256: protocolmainise97e041d…, from cachekit-io/protocol#193. The cachekit-rs copy atcachekit-rs-v0.11.0,v0.11.1andmain, and the cachekit-ts copy atcachekit-v0.2.1andmain, are allb677d5f1…. That is the cachekit-io/protocol#180 revision.python3 tools/test_check_version_floors.py && python3 tools/check-version-floors.py,python3 tools/test_changelog_collect.pyandpython3 tools/conformance.py checkpass. Every table row keeps its five cells.