fix(ci): collapse goreleaser Task install+run into single step #153
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!153
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/153/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
First Tekton release run on
v2.24.0failed:releaseStep exited 127 (goreleaser: command not found). Tekton Step containers in a Pod share the workspace volume but NOT/usr/local/bin/, so tools installed in earlierinstall-*Steps were gone when thereleaseStep started.This commit moves syft + goreleaser installation inline into the
releaseStep so the binaries are available where they're used.Smoke-test stays a separate Step — it only reads from
dist/which lives on the shared workspace.Tracks bead
forgejo-mcp-29g.Why this is a workaround, not the fix
Inline install on every release is fragile (upstream URL changes, GitHub rate limits,
go installbuild time on every run). Proper fix is a prebuilt OCI image with all release tooling baked in. Tracked as P0 inforgejo-mcp-1b4. This PR unblocks v2.24.x shipping; the image work proceeds in parallel.State of v2.24.0
Tag
v2.24.0exists on remote but no Release object on Codeberg (goreleaser never reached the publish call). Path B: leave the tag, ship v2.24.1 as the first real Tekton release. Phantom tag is harmless for binary/mcpb users (Codeberg Releases page simply skips it).Test plan
v2.24.1(fix(ci) → patch bump).on-tag-push-releasePipelineRun inop1st-pipelines.releaseStep completes;dist/contains 4× archive + 4× SBOM +checksums.txt.forgejo-mcp versionbanner matches2.24.1).cosign-sign+mcpb-packTasks complete.checksums.txt.sig.cosign verify-blob --key <op1st-pub> --signature checksums.txt.sig checksums.txtsucceeds.op1st Pipelines as Code/code-scans-ldqvp is running.
Starting Pipelinerun code-scans-ldqvp 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-ldqvp -fop1st Pipelines as Code/on-pull-request-km6qv is running.
Starting Pipelinerun on-pull-request-km6qv 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-km6qv -fop1st Pipelines as Code/code-scans-ldqvp
Task Statuses:
fetch-source
gitleaks-version
Failure snippet:
task fetch-source has the status "TaskRunCancelled":op1st Pipelines as Code/on-pull-request-km6qv
Task Statuses:
fetch-source
Failure snippet:
task fetch-source has the status "TaskRunCancelled":