GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — fix: bump Go version from 1.26.5 to 1.26.9 (backport 2.36) by droopy4096 · Pull Request #30810 · coder/coder

Conversation

@droopy4096

@droopy4096 droopy4096 commented Oct 14, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

Backport of #30807 to release/2.36.

Bumps the Go toolchain from 1.26.5 to 1.26.9. Tracked in Linear: ENT-210 (Iron Bank fix-by date 2026-10-29 for the Critical finding). Same approach as the Terraform 1.16.5 backports (#30516 and its backports).

Files changed: go.mod, mise.toml, mise.lock (toolchain pin plus the per-platform archive URLs and SHA-256 checksums from the official go.dev/dl list).

Not built or scanned locally; CI will build it.

Companion PR: the module side of GO-2026-6612 (Critical), -6603, -6610, -6611 and -6617 is fixed by golang.org/x/net v0.60.0, backported in #30816 (ENT-211). This PR alone does not clear them; both are needed.

Opened by Superblink on behalf of @droopy4096.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@droopy4096 droopy4096 added community Pull Requests and issues created by the community. cherry-pick/v2.36 Cherry-pick PR targeting release/2.36 labels Oct 14, 2026
@github-actions

github-actions Bot commented Oct 14, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@github-actions github-actions Bot assigned droopy4096 Oct 14, 2026
@linear-code

linear-code Bot commented Oct 14, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown

ENT-210

ENT-212

ENT-215

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@droopy4096 droopy4096 mentioned this pull request Oct 14, 2026
fix: bump Go version from 1.26.5 to 1.26.9 #30807
Merged
@droopy4096 Linear Code

droopy4096 commented Oct 15, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor Author

I have read the CLA Document and I hereby sign the CLA

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@droopy4096 Linear Code

droopy4096 commented Oct 15, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor Author

recheck

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@droopy4096 @coder
fix: bump Go version from 1.26.5 to 1.26.9
c67ea20
(cherry picked from commit bb52628)
@coder
coder Bot force-pushed the backport/go-1.26.9-release-2.36 branch from 16ee509 to c67ea20 Compare October 15, 2026 14:23
@coder

coder Bot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

About the failing Analyze PR for Documentation Updates Needed check: this failure is unrelated to the Go bump in this PR.

PRs run the .github/workflows/doc-check.yaml from their base branch. On release/2.34 to release/2.37 that workflow pins coder/agents-chat-action v0.3.0 or older, which calls the /api/experimental/chats routes. Those were removed in #29548 (the API moved to /api/v2 in #28496), so the first chat lookup fails with Coder API error: Not Found. main and release/2.38 pin v0.5.1 (see #29732) and pass.

The check isn't part of required, so it doesn't block merging. A fix that limits doc-check to PRs into main (docs are published from main, so backports need no docs review) is being opened for main and release/2.34 to release/2.37; a link will follow here.

Posted by Superblink on behalf of @droopy4096.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@coder coder Bot mentioned this pull request Oct 15, 2026
ci: bump agents-chat-action to v0.5.1 in doc-check (backport 2.36) #30848
Merged
@coder

coder Bot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

Correction to the comment above: the fix doesn't limit doc-check to main. It fixes the cause instead: #30848 bumps coder/agents-chat-action in doc-check.yaml on release/2.36 to v0.5.1, which uses the /api/v2 chat routes (same change as #29732 on main). Once it merges, a rerun of this check should pass.

Posted by Superblink on behalf of @droopy4096.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@coder
coder Bot requested a review from denisra October 15, 2026 15:46
droopy4096 added a commit that referenced this pull request Oct 15, 2026
@coder @droopy4096
ci: bump agents-chat-action to v0.5.1 in doc-check (backport 2.36) (#…
fbafb7f
…30848)

Bumps the pinned `coder/agents-chat-action` in
`.github/workflows/doc-check.yaml` on `release/2.36` from v0.3.0 to
v0.5.1 (`9b3ac42`). Same change as #29732 on `main`.

## Why

The `Analyze PR for Documentation Updates Needed` job fails on every PR
into `release/2.36` (e.g. #30810) with `Coder API error: Not Found`. The
pinned version calls `/api/experimental/chats`, which #29548 removed
after the chat API moved to `/api/v2` (#28496). v0.5.1 calls
`/api/v2/chats`.

v0.5.1 accepts every input this workflow passes (its inputs are a
superset of v0.3.0's), so no other workflow changes are needed. The
doc-check run on this PR is the end-to-end test.

## Changes

- `.github/workflows/doc-check.yaml`: one `uses:` line.

Related:
[ENT-210](https://linear.app/codercom/issue/ENT-210/ironbank-critical-bump-go-to-1269-fix-by-2026-10-29)
(surfaced on the Go 1.26.9 backports).

Opened by Superblink on behalf of @droopy4096.

Co-authored-by: Dmytro Makovey <[email protected]>
@droopy4096
Merge branch 'release/2.36' into backport/go-1.26.9-release-2.36
94821b0
droopy4096 added a commit that referenced this pull request Oct 15, 2026
@droopy4096
fix: bump Go version from 1.26.5 to 1.26.9 (#30807)
d36c153
Bump the Go toolchain from 1.26.5 to 1.26.9 ([released
2026-10-02](https://go.dev/doc/devel/release#go1.26.9)).

Tracked in Linear:
[ENT-210](https://linear.app/codercom/issue/ENT-210/ironbank-critical-bump-go-to-1269-fix-by-2026-10-29).
Iron Bank fix-by date for the Critical finding is **2026-10-29**.

Go 1.26.9 includes fixes for the findings Iron Bank reported against
`coder/coder-enterprise/coder-service-2:2.38.0`. Of the 19 still-valid
advisories, 12 are only fixed in 1.26.9, including the Critical one:

- Critical: [GO-2026-6612](https://pkg.go.dev/vuln/GO-2026-6612) /
CVE-2026-78663 (HTTP/2 server double flow-control refund)
- High: GO-2026-6603, -6605, -6607, -6608, -6609, -6610, -6611, -6613
- Low: GO-2026-6599, -6600, -6617

The other 7 (GO-2026-5026, -5942, -6088, -6089, -6090 High; -6091, -6218
Medium) are fixed since 1.26.6. The full list with links is in ENT-210.

## Changes

Same file set as #27157:

- `go.mod`: `go 1.26.5` to `go 1.26.9`
- `mise.toml` / `mise.lock`: Go toolchain pin and the archive URLs and
SHA-256 checksums for each platform (taken from the official `go.dev/dl`
release list)

## Verification

- `go build ./enterprise/cmd/coder` with go1.26.9 succeeds; `go mod tidy
-diff` is clean.
- `govulncheck -mode binary` on the resulting binary reports none of the
19 advisories above. The same scan of the released 2.38.0 binary
(go1.26.5) reports all 19.

## Not in this PR

`golang.org/x/net` v0.60.0 (the module-side half of GO-2026-6603, -6610,
-6611, -6612 and -6617) is already on `main` via #30772 and is
backported to the release branches in #30814 (2.38), #30815 (2.37),
#30816 (2.36), #30817 (2.35) and #30818 (2.34), tracked in
[ENT-211](https://linear.app/codercom/issue/ENT-211/ironbank-critical-bump-golangorgxnet-to-v0600-on-release-branches-fix).
The Go 1.27.1 bump (#30288) stays a separate, larger change. Go
backports: #30808 (2.38), #30809 (2.37), #30810 (2.36), #30813 (2.35),
#30811 (2.34).

Opened by Superblink on behalf of @droopy4096.
denisra
denisra approved these changes Oct 15, 2026
View reviewed changes
@droopy4096
droopy4096 merged commit 676a147 into release/2.36 Oct 15, 2026
31 checks passed

Uh oh!

There was an error while loading. Please reload this page.

@droopy4096
droopy4096 deleted the backport/go-1.26.9-release-2.36 branch October 15, 2026 19:34
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 15, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@denisra denisra denisra approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

@droopy4096 droopy4096

Labels

cherry-pick/v2.36 Cherry-pick PR targeting release/2.36 community Pull Requests and issues created by the community.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@droopy4096 @denisra
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.