docs: record scanned sops v0.4.0 digest #39

Open
brandon wants to merge 2 commits from docs/record-sops-v0-4-digest into main
Owner

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.

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.
docs: record scanned sops v0.4.0 digest
All checks were successful
ci/woodpecker/pr/ci Pipeline was successful
1c69723f3c
Author
Owner

Triage (2026-10-16): I checked this against main at d7b7c8a, 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.

  • Still fully relevant: main still lists sops-no-duplicates at v0.3.0 and has no v0.4.0 digest row. git.nastoupil.org/brandon/sops-no-duplicates:v0.4.0 resolves to sha256:23b8c2e0…69b4e5fc today (checked anonymously), which matches this PR.
  • Rebase conflict: README.md, in the catalog table only. main has since changed the neighbouring rows: vps-ssh is now v0.2.0 (v0.3.0 reserved), terraform-stack is v0.2.2, and tailscale-acl/governor-gate rows were added. To resolve, take main's table and change only the sops-no-duplicates cell to v0.4.0, then keep the new digest-table row.
  • After the rebase, the PR pipeline (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.

Triage (2026-10-16): I checked this against `main` at d7b7c8a, 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. - **Still fully relevant:** `main` still lists `sops-no-duplicates` at `v0.3.0` and has no `v0.4.0` digest row. `git.nastoupil.org/brandon/sops-no-duplicates:v0.4.0` resolves to `sha256:23b8c2e0…69b4e5fc` today (checked anonymously), which matches this PR. - **Rebase conflict:** README.md, in the catalog table only. `main` has since changed the neighbouring rows: `vps-ssh` is now `v0.2.0` (`v0.3.0` reserved), `terraform-stack` is `v0.2.2`, and `tailscale-acl`/`governor-gate` rows were added. To resolve, take `main`'s table and change only the `sops-no-duplicates` cell to `v0.4.0`, then keep the new digest-table row. - After the rebase, the PR pipeline (`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.
Merge origin/main into docs/record-sops-v0-4-digest
All checks were successful
ci/woodpecker/pr/pr-review Pipeline was successful
ci/woodpecker/pr/ci Pipeline was successful
0214fb0edc
Resolve the README catalog conflict: keep main's rows (vps-ssh v0.3.0
reservation, terraform-stack v0.2.2, tailscale-acl and governor-gate)
and apply this PR's sops-no-duplicates v0.3.0 -> v0.4.0 bump. The v0.4.0
digest row merged cleanly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
First-time contributor

Review Findings

No issues found.

The diff updates the sops-no-duplicates plugin version from v0.3.0 to v0.4.0 in two locations:

  1. The plugin table (line 9)
  2. The digest records table (line 18) - adds a new entry with the corresponding SHA256 digest

The changes are straightforward version bumps with proper digest documentation. The date (2026-08-28) is consistent with existing entries.

## Review Findings **No issues found.** The diff updates the `sops-no-duplicates` plugin version from `v0.3.0` to `v0.4.0` in two locations: 1. The plugin table (line 9) 2. The digest records table (line 18) - adds a new entry with the corresponding SHA256 digest The changes are straightforward version bumps with proper digest documentation. The date (2026-08-28) is consistent with existing entries. <!-- claude-review: commit=0214fb0edc681253e40309373bdc5a525ba2c2c4 -->
All checks were successful
ci/woodpecker/pr/pr-review Pipeline was successful
ci/woodpecker/pr/ci Pipeline was successful
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin docs/record-sops-v0-4-digest:docs/record-sops-v0-4-digest
git switch docs/record-sops-v0-4-digest

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.

git switch main
git merge --no-ff docs/record-sops-v0-4-digest
git switch docs/record-sops-v0-4-digest
git rebase main
git switch main
git merge --ff-only docs/record-sops-v0-4-digest
git switch docs/record-sops-v0-4-digest
git rebase main
git switch main
git merge --no-ff docs/record-sops-v0-4-digest
git switch main
git merge --squash docs/record-sops-v0-4-digest
git switch main
git merge --ff-only docs/record-sops-v0-4-digest
git switch main
git merge docs/record-sops-v0-4-digest
git push origin main
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
brandon/ci-plugins!39
No description provided.