docs: record scanned sops v0.4.0 digest #39
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/record-sops-v0-4-digest"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Records the corrected sops-no-duplicates v0.4.0 multi-arch index digest. The published digest passed the catalog CRITICAL Trivy gate with zero findings and its legacy cosign signature verified against the catalog public key.
Triage (2026-10-16): I checked this against
mainatd7b7c8a, which includes the notify-on-push-failure fix (#52). Left open, not rebased. This is an operator-authored branch, so I won't force-push it.mainstill listssops-no-duplicatesatv0.3.0and has nov0.4.0digest row.git.nastoupil.org/brandon/sops-no-duplicates:v0.4.0resolves tosha256:23b8c2e0…69b4e5fctoday (checked anonymously), which matches this PR.mainhas since changed the neighbouring rows:vps-sshis nowv0.2.0(v0.3.0reserved),terraform-stackisv0.2.2, andtailscale-acl/governor-gaterows were added. To resolve, takemain's table and change only thesops-no-duplicatescell tov0.4.0, then keep the new digest-table row.plugin-tests,shellcheck) re-runs on the new head. The green status shown here is from 2026-08-28.Risk: R2 (supply-chain digest record and catalog pin). Reuse: the existing README digest-table convention.
Review Findings
No issues found.
The diff updates the
sops-no-duplicatesplugin version fromv0.3.0tov0.4.0in two locations:The changes are straightforward version bumps with proper digest documentation. The date (2026-08-28) is consistent with existing entries.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.