Skip to content

Fix/discovery release go toolchain - #26

Merged
juicycleff merged 2 commits into
mainfrom
fix/discovery-release-go-toolchain
Aug 27, 2026
Merged

juicycleff merged 2 commits into
mainfrom
fix/discovery-release-go-toolchain

Conversation

@juicycleff

@juicycleff juicycleff commented Aug 26, 2026 •

Copy link
Copy Markdown
Contributor

Description

Type of Change

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Other changes that don't modify src or test files

Breaking Change

  • Yes, this PR contains a breaking change
  • No, this PR does not contain a breaking change

Checklist

  • My code follows the project's code style
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings or errors
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published
  • I have checked for race conditions with go test -race
  • I have run golangci-lint run and fixed all issues

Testing

Related Issues

Closes #

Additional Notes

discovery/etcd and discovery/mdns declare go 1.25.0, forced by their
golang.org/x/net, x/sys and x/text requirements, which came in with the
advisory fix in 0aa9069. actions/setup-go pins GOTOOLCHAIN=local, so the
job's Go 1.23 refused to build them:

    go: go.mod requires go >= 1.25.0 (running go 1.23.12; GOTOOLCHAIN=local)

The other four discovery modules stay at go 1.23.0 and build fine on a
1.25 toolchain, so the job now uses the highest directive across the set.
The discovery modules are separate Go modules, so the root `go test ./...`
never reached them. Their first build was the post-merge release job, which
is how the go 1.25.0 directive bump in 0aa9069 reached main before anything
tried to compile it.

Modules are enumerated with find rather than hardcoded, so a new submodule
is covered automatically -- the release job's fixed list would skip it. The
loop visits every module before exiting non-zero, so one broken module does
not hide the rest.
@juicycleff
juicycleff merged commit 60397fc into main Aug 27, 2026
27 checks passed
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.

1 participant