Repository navigation
Update CI every month: the workflows' actions and the golangci-lint pin #1020
Description
Epic: NobleFactor/noblefactor-ops#142 · Feature: #1019 · Schedule: #916, lane 35, after PR C, then monthly
A recurring chore: once a month, CI's tools go to their latest releases. The owner, 2026-10-02: "my experience: update regularly or get stuck."
Each month
- every
uses:in.github/workflows/at its action's latest release, its release notes read for breaking changes -
GOLANGCI_LINT_VERSIONin theMakefileat the latest golangci-lint, and any new findings fixed rather than suppressed - the pull request's CI green on every platform, Windows included, and a comment here recording what moved
It does not close. Each month's pull request says Part of this issue.
The first run, measured 2026-10-02
| Tool | Now | Latest |
|---|---|---|
actions/checkout, 14 uses |
v4 | v7.0.1 |
actions/setup-go, 6 uses |
v5 | v7.0.0 |
actions/create-github-app-token, 3 uses |
v1 | v3.2.0 |
golangci-lint, pinned in the Makefile |
v2.13.2 | v2.14.0 |
Plan and design documents
| Kind | Document |
|---|---|
| Plan | no plan yet |
| Design | none |
Activity
fix(install): install.sh takes --option value, exits with a status fo…
David-Noble-at-work commentedon Oct 10, 2026
golangci-lint's pin moved from v2.13.2 to v2.14.0 in #1039 (lane 62 of #916), ahead of this chore's first run: v2.13.2 cannot read Go 1.27.2's standard library ("export data version 5 is greater than maximum supported version 4"), and v2.14.0's gocritic took two
%#qformats incmd/writ/writ/migrate/session.go, fixed rather than suppressed. CI installs the pinned version; v2.14.0 is installed on Danoble-MBP-A (/usr/local/bin), danoble-ud24-1.local (~/.local/bin) and danoble-wd11-3 (WinGet). The workflows' actions did not move; they and the next golangci-lint release are this chore's monthly run.