Skip to content

Keeping current: CI's actions, the linter and the Go modules are updated every month #1019

Open

Description

@David-Noble-at-work

Epic: NobleFactor/noblefactor-ops#142

The owner, 2026-10-02: "we should be updating to the latest and greatest libraries on a regular cadence", then "my experience: update regularly or get stuck", and "a one-month cadence sounds right."

What it is

Two recurring chores keep devlore-cli's dependencies current, once a month, each run its own pull request:

  • Update CI: the GitHub Actions the workflows use, and the golangci-lint version the Makefile pins.
  • Update Go modules: the direct modules within their major versions, in one pull request, and the Go toolchain; each new major version, or moved module, becomes an issue of its own.

Neither chore closes. Each month's pull request says Part of its chore, and a comment on the chore records what moved.

State on 2026-10-02

Go 1.27.1 is current. Behind: golangci-lint v2.13.2 (v2.14.0 is out); actions/checkout v4 (v7.0.1), actions/setup-go v5 (v7.0.0) and actions/create-github-app-token v1 (v3.2.0); 13 of 26 direct Go modules within their major versions, three that need code changes, and one that moved. Nothing automates it today: no Dependabot or Renovate configuration, and no make target.

Plan and design documents

Kind Document
Plan no plan yet
Design none: the process is the two chores' bodies

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Epic:Ops:ProcessTooling axis: process work; never closesfeatureDeliverable unit within an epic

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions