s1d3sw1ped/steamcache2
1
0
Fork 0
Code Issues Pull requests Projects Releases 34 Packages Wiki Activity Actions

ci: Merge main into develop #60

Merged
linus merged 4 commits from main into develop 2026-10-18 03:10:10 +00:00
Conversation 0 Commits 4 Files changed 6 +85 -9
linus commented 2026-10-18 03:08:34 +00:00
Collaborator
Copy link

Merge main into develop so develop descends from main again after the Forgejo workflow move landed on both branches separately. No content change beyond the merge.

Merge main into develop so develop descends from main again after the Forgejo workflow move landed on both branches separately. No content change beyond the merge.
Move CI workflows to .forgejo/workflows
Some checks failed
CI / vulncheck (pull_request) Failing after 29s
Details
CI / check-and-test (pull_request) Successful in 1m34s
Details
a9a699daba 
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 / check-and-test (pull_request) Failing after 28s
Details
CI / vulncheck (pull_request) Successful in 29s
Details
a811795262 
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 24s
Details
CI / check-and-test (pull_request) Successful in 1m4s
Details
94958feb59 
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 'Move CI workflows to .forgejo/workflows' (#58) from jerry/move-workflows-to-forgejo into main
All checks were successful
CI / vulncheck (push) Successful in 28s
Details
CI / check-and-test (push) Successful in 1m6s
Details
CI / vulncheck (pull_request) Successful in 26s
Details
CI / check-and-test (pull_request) Successful in 1m0s
Details
2ddfda718b
linus merged commit d4827b9f70 into develop 2026-10-18 03:10:10 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
blocked
Stuck. The assignee needs a decision or an unblock; see the latest comment.

  
bug
Something is not working

  
draft
Draft for review — do not merge without Eva review

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
help wanted
Need some help

  
invalid
Something is wrong

  
question
More information is needed

  
wontfix
This won't be fixed

No labels
blocked
bug
draft
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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
s1d3sw1ped/steamcache2!60
No description provided.