Repository navigation
[v2.19.1]
Fixed
- Run the complete release gate and downstream publishers when optional recovery jobs are
skipped, while still blocking publication after any required build fails, is cancelled, or skips. - Exercise transitive GitHub Actions skip propagation in release-cohort regression tests,
including main, CLI/SDK tags, registry no-ops, and metadata-only recovery.
Changed
- Prepare CLI/application 2.19.1 with the changes staged for
v2.19.0. Preserve the
original v2.19.0 tag, which did not publish release assets; library and SDK versions remain
independent and unchanged.
Python SDK publishing provenance
The PyPI “Change of provenance” notice for kingfisher-secret-scanner 1.6.4 records an intentional publishing-workflow migration within the official mongodb/kingfisher repository: from the standalone Python SDK workflow to the release coordinator. This corrects the reusable-workflow OIDC/attestation identity mismatch; attestations remain enabled.
All seven published 1.6.4 files match the SHA256 hashes of the original staged distributions from the successful release cohort. Each file's original Sigstore attestation passed independent cryptographic verification, including the expected repository, workflow, source commit, ref, publisher run/attempt, and protected environment. This verifies authenticated publication and artifact integrity, not an audit of code safety.
The notice records a historical identity change, not a failed signature check. We are keeping the published files and their attestations intact and retaining the coordinator identity for future releases. See PyPI's provenance guidance.