janhoy commented on PR #865: URL: https://github.com/apache/solr-operator/pull/865#issuecomment-6390349534
Rebased on a newer Go toolchain so kustomize is no longer held back. kustomize v5.8.3 requires Go 1.27 while go.mod pinned 1.26, so the previous commit took v5.8.0 to avoid silently pulling a second toolchain. This bumps Go to 1.27 (current stable; 1.26 remains upstream-supported) and takes v5.8.3. The toolchain moves in four places at once — go.mod, build/Dockerfile, and the go-version matrix in check.yaml and smoke-tests.yaml — because the Makefile's version gate rejects a mismatch in either direction, a newer toolchain included. Nothing else was being held back: re-running the upgrade detector against the new floor reports every module and tool pin current. make prepare produced no generated-file churn, as kustomize only drives the deploy kustomization and not manifest generation. This is also the first change to follow the skill's new rule from #864: resolve the Go toolchain before judging any other candidate, so dependencies are evaluated against the Go version you are moving to, not the one you are moving from. make list-upgrades now annotates any candidate that needs a newer Go than go.mod pins, which is how this case surfaced rather than being discovered by hand. The changelog entries are also reworded to the tighter style that skill now requires. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
