s1d3sw1ped/SwipedModSwitcher
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 5 Wiki Activity

ci: Bump tag-release golangci-lint to v8 #35

Merged
Ghost merged 1 commits from ash/ci-modernize-sms into master 2026-09-01 21:32:30 -05:00
Conversation 0 Commits 1 Files Changed 2
+58 -4
Ghost commented 2026-09-01 21:22:17 -05:00
Copy Link
Copy Source

Summary

  • Bump .gitea/workflows/tag-release.yaml Lint to golangci/golangci-lint-action@v8 + version: v2.13.2 + args: --timeout=5m (parity with push-ci / PR CI; fixes Go 1.27 vs golangci go1.24 failure).
  • Add needs: [lint, test] on the release job so publish cannot race ahead of a failing lint.
  • Keep Fyne --release linux+windows builds + upload-artifact.
  • Replace deprecated gitea.com/actions/release-action + secrets.RELEASE_TOKEN with https://gitea.com/actions/gitea-release-action@v1, job permissions: contents: write, and env.GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }} (automatic job token; empty Actions secrets UI is normal). No custom RELEASE_TOKEN.
  • Add optional .golangci.yml adapted from steamcache2 v2 skeleton (timeout 5m, modules-download-mode readonly, misspell; no steamcache path excludes; gosec deferred).

No GoReleaser. Do not rename master.

Issue

Fixes #34

Test plan

  • PR CI (pull-request-ci) green on this branch
  • After merge, re-run or push a pre-release v* tag and confirm Lint passes and release uploads only after lint+test via gitea-release-action@v1
  • If tag release still 404s after merge, ask Rex for a PAT — do not invent RELEASE_TOKEN first
## Summary - Bump `.gitea/workflows/tag-release.yaml` Lint to `golangci/golangci-lint-action@v8` + `version: v2.13.2` + `args: --timeout=5m` (parity with push-ci / PR CI; fixes Go 1.27 vs golangci go1.24 failure). - Add `needs: [lint, test]` on the release job so publish cannot race ahead of a failing lint. - Keep Fyne `--release` linux+windows builds + upload-artifact. - Replace deprecated `gitea.com/actions/release-action` + `secrets.RELEASE_TOKEN` with `https://gitea.com/actions/gitea-release-action@v1`, job `permissions: contents: write`, and `env.GITEA_TOKEN: ${{ secrets.GITEA_TOKEN }}` (automatic job token; empty Actions secrets UI is normal). No custom RELEASE_TOKEN. - Add optional `.golangci.yml` adapted from steamcache2 v2 skeleton (timeout 5m, modules-download-mode readonly, misspell; no steamcache path excludes; gosec deferred). No GoReleaser. Do not rename `master`. ## Issue Fixes https://git.s1d3sw1ped.com/s1d3sw1ped/SwipedModSwitcher/issues/34 ## Test plan - [ ] PR CI (pull-request-ci) green on this branch - [ ] After merge, re-run or push a pre-release `v*` tag and confirm Lint passes and release uploads only after lint+test via gitea-release-action@v1 - [ ] If tag release still 404s after merge, ask Rex for a PAT — do not invent RELEASE_TOKEN first
Ghost added 1 commit 2026-09-01 21:23:25 -05:00
ci: Bump tag-release golangci-lint to v8
CI / Build (pull_request) Successful in 38s
Details
CI / Lint (pull_request) Successful in 42s
Details
CI / Test (pull_request) Successful in 59s
Details
5b2affec8d
Ghost force-pushed ash/ci-modernize-sms from 5e4a10c573 to 5b2affec8d 2026-09-01 21:23:25 -05:00 Compare
Ghost merged commit 23287c7c6c into master 2026-09-01 21:32:30 -05:00
Ghost deleted branch ash/ci-modernize-sms 2026-09-01 21:32:30 -05:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ash blake eva linus moss pike s1d3sw1ped
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: s1d3sw1ped/SwipedModSwitcher#35
Delete Branch "ash/ci-modernize-sms"

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?