Skip to content

Adopt go1.26 across CI and formatting - #5465

Merged
norman-abramovitz merged 2 commits into
cloudfoundry:developfrom
nabramovitz:chore/adopt-go1.26
Jun 17, 2026
Merged

Adopt go1.26 across CI and formatting#5465
norman-abramovitz merged 2 commits into
cloudfoundry:developfrom
nabramovitz:chore/adopt-go1.26

Conversation

@nabramovitz

Copy link
Copy Markdown
Contributor

Aligns the repo on the Go version go.mod already declares (go 1.26.3).

Changes

  • CI Go version → 1.26 in all three workflows: pr.yml and backend_tests.yml (were 1.25) and release.yml (was 1.21). go.mod requires 1.26.3, so the older pins were inconsistent with the module's minimum — release at 1.21 was either failing the version requirement or silently auto-downloading 1.26.
  • gofmt under go1.26 for the two files that still carried go1.25 formatting: api/structs.go (struct field alignment) and plugins/cfapppush/vcs.go (standalone comment). Whitespace and comment only, no behavior change. The rest of the backend tree was already 1.26-clean.

No functional code changes.

go.mod declares go 1.26.3, but api/structs.go (struct field alignment)
and plugins/cfapppush/vcs.go (standalone comment) still carried go1.25
gofmt output. Whitespace and comment only, no behavior change.
go.mod declares go 1.26.3 but CI ran older toolchains (pr + backend
tests on 1.25, release on 1.21). Align all three workflows to 1.26 so
CI matches the module's required version and its gofmt baseline.

@norman-abramovitz norman-abramovitz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@norman-abramovitz
norman-abramovitz merged commit 212fd8c into cloudfoundry:develop Jun 17, 2026
12 checks passed
@nabramovitz
nabramovitz deleted the chore/adopt-go1.26 branch June 17, 2026 08:06
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.

2 participants