fix: 🔒️ SHA256-verify goreleaser+syft, drop piped install.sh #159
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human-required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!159
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/159/head"
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?
Summary
Hardens supply-chain pinning for two tools in the release-tools image that had no integrity verification:
goreleaser: was
go install github.com/goreleaser/goreleaser/v2@v2.16.0— re-resolves the full transitive dependency graph from proxy.golang.org on every image build. A transitive dep takeover would ship unnoticed. Now: downloads prebuiltgoreleaser_Linux_x86_64.tar.gzand SHA256-verifies against both the recordedVERSIONS.mdhash and the publisher'schecksums.txt.syft: was
curl install.sh | sh— piped-script antipattern with no integrity control. Now: downloads prebuiltsyft_N.N.N_linux_amd64.tar.gzand SHA256-verifies the same way.Both expected SHA256 hashes are recorded in
VERSIONS.mdas the single source of truth. On version bumps, updateVERSIONS.md+ the correspondingARG *_SHA256default inContainerfiletogether.cosign verification was already correct and is unchanged.
Verification pattern (dual check)
Both tools use the same pattern:
VERSIONS.md/ Containerfile ARG)checksums.txtIf either check fails, the build fails before any binary reaches
/usr/local/bin.Closes forgejo-mcp-3h2
op1st Pipelines as Code/on-pull-request-57br8 is running.
Starting Pipelinerun on-pull-request-57br8 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines on-pull-request-57br8 -fop1st Pipelines as Code/code-scans-glvr6 is running.
Starting Pipelinerun code-scans-glvr6 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines code-scans-glvr6 -fop1st Pipelines as Code/code-scans-glvr6 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/on-pull-request-57br8
Task Statuses:
fetch-source
build-and-test
Failure snippet:
task build-and-test has the status "TaskRunCancelled":