Skip to content

CP-49944: Bump bundled Alloy to v1.21.0, Go to 1.27.2, x/net to v0.61.0 - #1092

Merged
evan-cz merged 3 commits into
developfrom
CP-49944-alloy-v1.21.0
Oct 21, 2026
Merged

evan-cz merged 3 commits into
developfrom
CP-49944-alloy-v1.21.0

Conversation

@evan-cz

@evan-cz evan-cz commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

Why?

The image vulnerability scan fails on every open PR because of new Critical/High advisories (GO-2026-6612 and others) in the Go standard library and golang.org/x/net. The findings come from three sources, and the scan stays red until all three are fixed. No single Dependabot PR fixes them all, so this PR stacks them:

  1. CP-29639: Bump golang from 1.27.1-alpine to 1.27.2-alpine in /docker #1079: golang image 1.27.1-alpine → 1.27.2-alpine
  2. CP-29639: Bump cloudzero/alloy from v1.20.1 to v1.21.0 in /docker #1086: Alloy v1.20.1 → v1.21.0. v1.20.1 bundles a go1.26.7 binary; v1.21.0 is built with Go 1.27.2 and x/net v0.61.0.
  3. This PR, which targets develop

What

On top of the two Dependabot bumps:

  • Go directives: the four go.mod files and the two test Dockerfiles move to 1.27.2. scripts/ci-checks.sh requires them to match docker/Dockerfile.
  • x/net → v0.61.0 in the root, .tools and tests modules. go get also pulled in the related golang.org/x/* minor bumps.
  • prometheus-config-reloader v0.93.1 → v0.94.1. Upstream still resolves x/net v0.58.0, so the reloader stage now pins x/net v0.61.0, plus x/crypto v0.58.0, which that x/net requires.

How Tested

🤖 Generated with Claude Code

https://claude.ai/code/session_01X8oDs1PNgjMKCk3RFyazm6

Top of the stack that clears the image scan's new Critical/High findings
(GO-2026-6612 and others), with the Go 1.27.2 image bump and the Alloy
v1.21.0 bump stacked below it:

- go.mod directives and the test Dockerfiles move to Go 1.27.2, which
  scripts/ci-checks.sh requires to match docker/Dockerfile.
- golang.org/x/net moves to v0.61.0 in the root, .tools and tests
  modules.
- prometheus-config-reloader moves from v0.93.1 to v0.94.1. Upstream
  still resolves x/net v0.58.0, so the reloader stage pins x/net v0.61.0
  and the x/crypto v0.58.0 it requires.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X8oDs1PNgjMKCk3RFyazm6
@evan-cz
evan-cz requested a review from a team as a code owner October 21, 2026 16:35
dependabot Bot added 2 commits October 21, 2026 12:36
Bumps [cloudzero/alloy](https://github.com/cloudzero/alloy) from v1.20.1 to v1.21.0.
- [Changelog](https://github.com/Cloudzero/alloy/blob/main/CHANGELOG.md)
- [Commits](https://github.com/cloudzero/alloy/commits)

---
updated-dependencies:
- dependency-name: cloudzero/alloy
  dependency-version: v1.21.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps golang from 1.27.1-alpine to 1.27.2-alpine.

---
updated-dependencies:
- dependency-name: golang
  dependency-version: 1.27.2-alpine
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@greptile-apps

greptile-apps Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issue was found in the changes.

Summary

Updates the bundled binaries and Go dependencies to address the reported vulnerability-scan failures.

  • The agent image now builds with Go 1.27.2 and bundles newer Alloy and reloader binaries.
  • The app, tools, and test builds now use the updated Go and x/* versions.

No actionable issues were found. Builds, tests, and image scans were not run during this review.

Reviews (2) · Last reviewed commit: "CP-29639: Bump golang from 1.27.1-alpine..." · Reviewed by Greptile

@evan-cz
evan-cz added this pull request to the merge queue Oct 21, 2026
Merged via the queue into develop with commit 0c03eea Oct 21, 2026
46 checks passed
@evan-cz
evan-cz deleted the CP-49944-alloy-v1.21.0 branch October 21, 2026 17:32
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