Skip to content

ci: fix Hive Go version patching for non-alpine base images#19851

Merged
yperbasis merged 1 commit into
mainfrom
fix/hive-go-version-patch
Mar 12, 2026
Merged

ci: fix Hive Go version patching for non-alpine base images#19851
yperbasis merged 1 commit into
mainfrom
fix/hive-go-version-patch

Conversation

@yperbasis

Copy link
Copy Markdown
Member

Summary

  • The Hive workflow sed pattern only matched golang:X.Y.Z-alpine, but the upstream Hive Dockerfile.git uses golang:X.Y.Z-trixie
  • This caused the Go version to never be patched, so when deps: upgrade gnark-crypto v0.19.1 → v0.20.0 #19808 bumped go.mod from go 1.25.0 to go 1.25.7, the Hive container still had Go 1.25.0 and the build failed with go: ../../go.mod requires go >= 1.25.7
  • Fix: match any distro suffix (s|golang:[0-9.]*-|golang:${go_version}-|) instead of hardcoding -alpine

Fixes the Hive EEST failure from #19808. Once merged, the gnark-crypto v0.20.0 upgrade can be re-landed.

Test plan

  • Verify Hive tests pass on this branch (the workflow fix itself is exercised when the Hive job runs)
  • After merge, re-land gnark-crypto v0.20.0 upgrade and confirm Hive EEST passes

🤖 Generated with Claude Code

The sed pattern only matched `golang:X.Y.Z-alpine` but the upstream
Hive Dockerfile.git uses `golang:X.Y.Z-trixie`. This caused the Go
version to never be patched, breaking builds when go.mod requires a
newer Go than the Hive Dockerfile's default.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@yperbasis yperbasis merged commit 8656902 into main Mar 12, 2026
36 checks passed
@yperbasis yperbasis deleted the fix/hive-go-version-patch branch March 12, 2026 10:34
AskAlexSharov pushed a commit that referenced this pull request Apr 8, 2026
The cherry-pick from release/3.4 reverted the sed pattern to only match
-alpine suffixes, but upstream Hive now uses -trixie. Restore the generic
pattern (golang:[0-9.]*-) so all distro suffixes are handled.

https://claude.ai/code/session_015vdXynCZ9mbKiDUfZx9Y1F
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