Skip to content

fix: bump go toolchain to 1.24.6 - #19449

Merged
grobinson-grafana merged 1 commit into
mainfrom
grobinson/bump-toolchain
Oct 9, 2025
Merged

fix: bump go toolchain to 1.24.6#19449
grobinson-grafana merged 1 commit into
mainfrom
grobinson/bump-toolchain

Conversation

@grobinson-grafana

@grobinson-grafana grobinson-grafana commented Oct 9, 2025

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

Bump go toolchain to 1.24.6.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Checklist

  • Reviewed the CONTRIBUTING.md guide (required)
  • Documentation added
  • Tests updated
  • Title matches the required conventional commits format, see here
    • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
  • Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
  • If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR
@grobinson-grafana
grobinson-grafana requested a review from a team as a code owner October 9, 2025 14:12

@shantanualsi shantanualsi 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, thanks!

@grobinson-grafana
grobinson-grafana merged commit becdf9b into main Oct 9, 2025
68 checks passed
@loki-gh-app

loki-gh-app Bot commented Oct 9, 2025

Copy link
Copy Markdown
Contributor

Hello @grobinson-grafana!
Backport pull requests need to be either:

  • Pull requests which address bugs,
  • Urgent fixes which need product approval, in order to get merged,
  • Docs changes.

Please, if the current pull request addresses a bug fix, label it with the type/bug label.
If it already has the product approval, please add the product-approved label. For docs changes, please add the type/docs label.
If the pull request modifies CI behaviour, please add the type/ci label.
If none of the above applies, please consider removing the backport label and target the next major/minor release.
Thanks!

@loki-gh-app

loki-gh-app Bot commented Oct 9, 2025

Copy link
Copy Markdown
Contributor

Hello @grobinson-grafana!
Backport pull requests need to be either:

  • Pull requests which address bugs,
  • Urgent fixes which need product approval, in order to get merged,
  • Docs changes.

Please, if the current pull request addresses a bug fix, label it with the type/bug label.
If it already has the product approval, please add the product-approved label. For docs changes, please add the type/docs label.
If the pull request modifies CI behaviour, please add the type/ci label.
If none of the above applies, please consider removing the backport label and target the next major/minor release.
Thanks!

1 similar comment
@loki-gh-app

loki-gh-app Bot commented Oct 9, 2025

Copy link
Copy Markdown
Contributor

Hello @grobinson-grafana!
Backport pull requests need to be either:

  • Pull requests which address bugs,
  • Urgent fixes which need product approval, in order to get merged,
  • Docs changes.

Please, if the current pull request addresses a bug fix, label it with the type/bug label.
If it already has the product approval, please add the product-approved label. For docs changes, please add the type/docs label.
If the pull request modifies CI behaviour, please add the type/ci label.
If none of the above applies, please consider removing the backport label and target the next major/minor release.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment