ci: Promote develop to main #63

Merged
linus merged 6 commits from develop into main 2026-10-18 15:26:16 +00:00
Collaborator

Cosmetic dual-branch realign after workflow-move merge commits. TREE_SAME (no file diff). Eva GO in open.md for Linus queue pass 2026-10-18.

Cosmetic dual-branch realign after workflow-move merge commits. TREE_SAME (no file diff). Eva GO in open.md for Linus queue pass 2026-10-18.
Move CI workflows to .forgejo/workflows
Some checks failed
CI / vulncheck (pull_request) Failing after 29s
CI / check-and-test (pull_request) Successful in 1m34s
2c38d8ba53
The server moved from Gitea to Forgejo, which reads .forgejo/workflows and ignores .gitea/workflows, so CI would silently stop running here. Move the files over. While at it, swap the gitea.* expression contexts for github.* (Forgejo rejects gitea.*) and point upload/download-artifact@v4 at code.forgejo.org/forgejo, since upstream v4 refuses to run on non-GitHub servers.
build: Pin Go 1.27.2 and stop early on a toolchain mismatch
Some checks failed
CI / vulncheck (pull_request) Successful in 26s
CI / check-and-test (pull_request) Failing after 31s
102f0cd106
CI / vulncheck is failing because the stdlib in go1.27.0 and go1.27.1 has
known vulnerabilities (GO-2026-6603 to 6617) that are fixed in go1.27.2.
setup-go reads go.mod, which only said go 1.27.0, so every runner kept
building with the vulnerable toolchain.

Add a toolchain go1.27.2 line to go.mod and a scripts/check-toolchain.sh
preflight, run before the build in each CI job. If the Go, GoReleaser or
go.mod pins are wrong it stops and prints what it found, what is required
and the fix command. Also pin GoReleaser to v2.18.3 in the release job and
use the versioned action tags instead of @main/@master.
ci: Bump golangci-lint to v2.14.0 for Go 1.27.2
All checks were successful
CI / vulncheck (pull_request) Successful in 23s
CI / check-and-test (pull_request) Successful in 1m2s
bc29941cea
With the toolchain at go1.27.2 the pinned golangci-lint v2.13.2 stops
type-checking the module (undefined: yaml and similar typecheck errors),
which fails CI / check-and-test even though go build and go vet pass.
v2.14.0 lints the same tree with 0 issues and is the version in the
forge toolchain standard.
Merge pull request 'ci: Merge main into develop' (#62) from main into develop
All checks were successful
CI / vulncheck (pull_request) Successful in 24s
CI / check-and-test (pull_request) Successful in 52s
8b0f218513
linus requested review from eva 2026-10-18 15:22:42 +00:00
linus merged commit 61aa2ce7c4 into main 2026-10-18 15:26:16 +00:00
Sign in to join this conversation.
No description provided.