Skip to content

Bump Go to 1.27.0 - #6

Open
github-actions[bot] wants to merge 6 commits into
mainfrom
bump-go-1.27.0
Open

Bump Go to 1.27.0#6
github-actions[bot] wants to merge 6 commits into
mainfrom
bump-go-1.27.0

Conversation

@github-actions

Copy link
Copy Markdown

This PR updates Go to the latest stable release.

  • go directive: 1.27.0
  • toolchain: (none -- go mod tidy removed it because the go directive already implies go1.27.0)

galamdring and others added 6 commits August 17, 2026 06:24
When multiple GitHub accounts are configured for the same host, gh always
uses the globally active account's token regardless of which org or user
owns the current repo. This causes commands to silently authenticate as
the wrong user.

This change adds an owner-to-user mapping stored in hosts.yml, and
automatically selects the correct token based on the repo owner resolved
from git remotes at HTTP client construction time. A new command
'gh auth set-user --owner <owner> <username>' manages the mappings.

Fixes cli#12885
NewIsolatedTestConfig now takes a cfgString param, and HttpClientFunc now
takes a remotesFunc param (added in the per-owner account mapping commit).
Fork-added tests were never updated for these, so they failed to compile
once rebased onto the current upstream/trunk.
The scheduled rebase onto upstream/trunk has been failing every week for
the last 2.5 months on the same unresolved conflict, with nothing but a
red check nobody was watching. Abort cleanly on conflict and file (or
update) a tracking issue summarizing what needs manual resolution.
actions/setup-go locks GOTOOLCHAIN=local after installing the toolchain
from the pre-bump go.mod. When bump-go.sh then edits go.mod to require a
newer Go release, `go mod tidy` refuses to fetch it and the job fails
(this also breaks upstream cli/cli's own Bump Go workflow whenever a new
minor Go version ships). Restore GOTOOLCHAIN=auto for just this step so
Go's normal on-demand toolchain download works as expected.
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.

3 participants