fix: 🚨 release: inject main.Version + use 'version' subcommand in smoke-test #149
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!149
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/149/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?
Fixes v2.23.0 release run #172. Two bugs in the v2.23.0 pipeline:
.goreleaser.ymlldflags injected-X main.BuildTag={{.Version}}butmain.godeclaresvar Version.main.BuildTagdoes not exist — injection is a no-op; shipped binaries reportforgejo-mcp dev.$BIN --help, butcmd.gousesflag.NewFlagSet(..., flag.ExitOnError)with no-helpflag. Exits non-zero, captured banner is the Usage block, regex never matches.Fix:
.goreleaser.yml:-X main.BuildTag→-X main.Version(drop unused BuildCommit/BuildDate)..forgejo/workflows/release.yml:$BIN --help→$BIN version(handled bycmd.isVersionRequest).Verified locally:
Closes
forgejo-mcp-hvr. Refs run #172.op1st Pipelines as Code/on-pull-request-8kdlj is running.
Starting Pipelinerun on-pull-request-8kdlj 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-8kdlj -fop1st Pipelines as Code/code-scans-nphmp is running.
Starting Pipelinerun code-scans-nphmp 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-nphmp -fop1st Pipelines as Code/code-scans-nphmp has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/on-pull-request-8kdlj has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test