Repository navigation
Prepare versioned 2.10.0 guidance after registry delivery - #212
Conversation
|
|
Documentation delivery is complete. Qualified head Actual Pages build/deploy 39982873189 succeeded for that merge. At 16:09 UTC, ordinary public URLs returned HTTP 200 and showed the qualified SDK 2.10.0 requirements on all five affected pages: client, metrics, testing, worker and SDK reference. No cache-busting URL was needed. The changelog date matches actual PyPI upload on October 23. Registry-installed acceptance covers the exact published 2.10.0 source, 334 controls, 37 source files and all 50 hashed RECORD entries, plus the retained genuine console/TLS scope. The four lost export originals remain excluded. This completes the planned docs gate for #189, #198, #166, #205, #173, #179 and #167; separate #175/#215 source is not included. |



Python SDK 2.10.0 is published, while five guides still call its APIs unreleased. Replace those notices with the precise minimum SDK version for schema-2 verification, private CA support, poll backoff, metrics and testing helpers. Date the changelog October 23, matching the actual PyPI upload.
Current head
990a9c2b62dac07ac74b6d2f68ba79d28a53369epasses all 18 normal checks, including CI 39978396546, integration, target qualification and the developer portal. Scoped Sonar review has zero OPEN/CONFIRMED findings and zero unreviewed hotspots; CodeQL has no open PR alerts. This does not describe the entire main backlog.Actual OIDC and registry-installed acceptance verifies exact
4f853f39, 37 source files, all 50 hashed RECORD entries, 334 passing controls and retained genuine console/TLS behavior. The four lost raw negatives are excluded. Earlier12band local4fartifacts remain separate from actual registry hashes.After merge, verify the real Pages deployment and the five affected routes, then close the seven delivered package issues. #175/#215 are separate source work outside this release. No protocol-floor change or automatic Server/Cloud adoption is included.