Skip to content

chore(deps): bump Go to 1.27.2 and refresh dependencies - #660

Merged
christiangda merged 3 commits into
mainfrom
chore/go-1.27.2-deps
Oct 11, 2026
Merged

christiangda merged 3 commits into
mainfrom
chore/go-1.27.2-deps

Conversation

@christiangda

@christiangda christiangda commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

Why

govulncheck fails the Test and Build job on every dependency PR — see #659 — because golang.org/x/net v0.59.0 carries five HTTP/2 advisories that govulncheck reports as reachable from this code (for example through pkg/aws/scim.go). Go 1.27.2 is also out, so this moves the toolchain and refreshes everything in one pass.

This PR supersedes #659: it contains the same six bumps at the same or newer versions, plus the fix that #659 is missing.

What changed

go.mod, go.sum, one workflow line and docs. No Go source changed.

Change From To
go directive 1.27.1 1.27.2
github.com/aws/aws-sdk-go-v2 v1.47.1 v1.47.3
…/config v1.33.6 v1.33.9
…/credentials v1.20.6 v1.20.9
…/service/s3 v1.114.0 v1.114.3
…/service/secretsmanager v1.50.1 v1.50.4
golang.org/x/sync v0.23.0 v0.24.0
google.golang.org/api v0.299.0 v0.301.0
golang.org/x/net (indirect) v0.59.0 v0.61.0
golang.org/x/crypto (indirect) v0.57.0 v0.58.0
cloud.google.com/go/auth (indirect) v0.23.3 v0.24.1
golangci-lint in build.yml v2.13.1 (pinned) latest

Other indirect modules moved with them; see the go.mod diff.

Three things that go beyond make go-mod-update

Reviewers should look at these, because the make target did not produce them on its own:

  1. golang.org/x/net was raised by hand. make go-mod-update runs go get -u on direct dependencies only, and it left x/net at the vulnerable v0.59.0. go get golang.org/x/net@latest took it to v0.61.0 (and x/crypto to v0.58.0 with it). This clears GO-2026-6603, GO-2026-6610, GO-2026-6611, GO-2026-6612 and GO-2026-6617, all fixed in v0.60.0.
  2. cloud.google.com/go/auth is pinned to the tagged v0.24.1. google.golang.org/api v0.301.0 requires the untagged pre-release commit v0.24.1-0.20261001053825-dbc26066f70a. The tagged v0.24.1 is the next release after that commit, so the Google authentication path does not run on an unreleased commit. Drop this pin if you would rather stay on exactly what upstream declares.
  3. golangci-lint is no longer pinned in the Lint job. The first push of this branch failed Lint: the pinned v2.13.1 cannot read the export data Go 1.27.2 writes (export data version 5 is greater than maximum supported version 4) and failed typecheck on every package. The job now uses version: latest, so the linter cannot go stale against the toolchain again. The trade-off is that a new linter release can fail CI with no change in the repository. The action itself stays SHA-pinned.

Verification

Local (Go 1.27.2, darwin/arm64, golangci-lint v2.14.0):

  • go mod verify — all modules verified
  • govulncheck ./... — 0 vulnerabilities called (before the x/net bump: 5). One module-level notice remains, GO-2026-5932 for the unmaintained x/crypto/openpgp package, which this code does not import and which has no fixed version.
  • go fix ./..., make go-fmt, make go-betteralign, make go-generate — no diff
  • golangci-lint run ./... — 0 issues
  • make build — both binaries build
  • make test (-race) — all packages pass
  • internal/model golden hash tests — pass unchanged, so state files and hashes are unaffected

CI on this branch: Lint, Test and Build (including govulncheck), fuzz targets and CodeQL all pass.

Release

Folded into the existing Unreleased entry in docs/Whats-New.md, which targets v0.46.0 (minor). docs/Development.md now states the correct go directive and linter requirement.

🤖 Generated with Claude Code

govulncheck fails the Build workflow on every dependency PR (see #659)
because golang.org/x/net v0.59.0 carries five HTTP/2 advisories that are
reachable from this code: GO-2026-6603, -6610, -6611, -6612 and -6617,
all fixed in v0.60.0.

- go directive 1.27.1 -> 1.27.2
- direct dependencies via `make go-mod-update` (aws-sdk-go-v2,
  golang.org/x/sync, google.golang.org/api)
- golang.org/x/net v0.59.0 -> v0.61.0, raised explicitly because
  `make go-mod-update` only upgrades direct dependencies
- cloud.google.com/go/auth pinned to the tagged v0.24.1 instead of the
  untagged pre-release commit google.golang.org/api v0.301.0 asks for

No code changes; golden hashes are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@christiangda christiangda self-assigned this Oct 11, 2026
christiangda and others added 2 commits October 11, 2026 08:17
The Lint job pinned golangci-lint v2.13.1, which cannot read the export
data Go 1.27.2 writes and fails typecheck on every package:

  export data version 5 is greater than maximum supported version 4

v2.14.0 reads it, and reports 0 issues against the committed config.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A pinned linter goes stale against the toolchain in go.mod: v2.13.1
could not read the export data Go 1.27.2 writes, so the Lint job failed
typecheck on every package until the pin was moved by hand.

Following the latest release removes that maintenance step. The
trade-off is that a new linter release can fail the job with no change
in the repository. The action itself stays SHA-pinned.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@christiangda
christiangda added this pull request to the merge queue Oct 11, 2026
Merged via the queue into main with commit fbfbebd Oct 11, 2026
7 checks passed
@christiangda
christiangda deleted the chore/go-1.27.2-deps branch October 11, 2026 06:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant