Skip to content

chore: update go to 1.26.6 - #1459

Closed
bradclawsie wants to merge 1 commit into
mainfrom
chore/go-1.26.6
Closed

bradclawsie wants to merge 1 commit into
mainfrom
chore/go-1.26.6

Conversation

@bradclawsie

Copy link
Copy Markdown
Contributor

Description

Update Go to 1.26.6.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Other (security config, docs update, etc)

Checklist before merging

@bradclawsie
bradclawsie requested a review from a team as a code owner August 14, 2026 16:42
@greptile-apps

greptile-apps Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Updates the repository’s mise-managed Go toolchain from 1.26.5 to 1.26.6.

  • Changes only the Go version pin in mise.toml.
  • Leaves the remaining development-tool versions and environment settings unchanged.

Confidence Score: 5/5

The PR appears safe to merge with no actionable failures identified.

The changed mise pin consistently updates the development and CI toolchain, and the older go.mod directive remains a compatible module minimum rather than a conflicting runtime requirement.

Important Files Changed

Filename Overview
mise.toml Updates the Go toolchain patch version to 1.26.6 without introducing an actionable correctness or configuration issue.

Reviews (1): Last reviewed commit: "chore: update go to 1.26.6" | Re-trigger Greptile

Comment thread mise.toml
# SPDX-License-Identifier: AGPL-3.0-or-later OR LicenseRef-Defense-Unicorns-Commercial

[tools]
go = "1.26.5"

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.

should we also be updating the go.mod for Go 1.26.6?

Comment thread mise.toml
# SPDX-License-Identifier: AGPL-3.0-or-later OR LicenseRef-Defense-Unicorns-Commercial

[tools]
go = "1.26.5"

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.

I was wondering why this was being created manually instead of renovate opening a pr so i looked at renovate logs and it would have opened a PR for this but its waiting for the three day stability window. I probably missed something that determined we needed to update this sooner than renovate would?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

ah no! I didn't know about that! thanks Chance, I'll just close this and let renovate do its thing.

@bradclawsie

Copy link
Copy Markdown
Contributor Author

apparently renovate takes care of these

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