chore(deps): bump steadybit kits and drop Go patch pin - #490
Conversation
|
Claude finished @joshiste's task in 1m 1s —— View job Claude's review of PR #490
Previous review threads: Both of my earlier comments (on New changes in this diff (origin/main...HEAD):
No new bugs, security issues, or concurrency concerns found — this PR only touches dependency versions and CI toolchain configuration, no application code changed. |
69be121 to
3455bb5
Compare
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
joshiste
changed the title
Bumps the kit modules to versions declaring a floating go directive and
removes the exact-patch pin. go mod tidy normalises the directive to the
module graph minimum (1.26.0), which is still floating - any 1.26.x
satisfies it. Also drops the redundant go_version override from ci.yml
so the reusable CI default ('1.26') applies.
3455bb5 to
b454fdc
Compare
The e2e-tests job had its own setup-go hardcoding '^1.26.5', which was missed when the go_version override was dropped from the extension-ci job. That left the two jobs able to build with different toolchains. Uses '1.26' with check-latest, matching the reusable CI default.
|
1 participant
Bumps the steadybit kit modules to versions declaring a floating
godirective and removes the exact-patch pin (go 1.26.5) from this module.What the
godirective ends up as:go mod tidynormalises the directive to the minimum required by the module graph, so this lands ongo 1.26.0(not a barego 1.26). That is still floating — any1.26.xtoolchain satisfies>= 1.26.0— the exact-patch pin is what's removed.Toolchain selection is handled separately: the
go_versionoverride is dropped fromci.ymlso the reusable extension CI default ('1.26') applies, and setup-go installs the latest1.26.x. This matches the floatinggolang:1.26-*Docker base images.Note:
go-version-file: go.modwas deliberately not used — since the directive normalises to a full version, it would pin CI to the oldest patch.