You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6d6dbac
Browse filesBrowse the repository at this point in the historyBrowse files
* build(core): move to core v0.19.4
Core v0.17.0 -> v0.19.4, from the released tag, then `go mod tidy`. The
other movements (grpc v1.84.0, otel v1.47.0, go-openapi/swag v0.29.2,
genproto, x/sys, go-git) are what MVS takes from core v0.19.4's own
requirements; none was bumped by hand. kustomize api/kyaml stay at v0.21.1
and kube-openapi at d427ff9ee9ad, so no structured-merge-diff/v7 enters
the graph and the downgrade from #93 is not needed.
No call site broke. The one core surface labelled legacy that this repo
read is TestResponse.Status (runtime.proto: "Legacy flat fields",
deprecated = true); the lifecycle test now asserts the structured
TestRunResult, which service-python's Runtime.Test fills on every path.
AGENTS.md stated Go 1.27.0; go.mod has said 1.27.2 since #86.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(scout): label the releaser's Go toolchain drift as a stopgap
go.mod's `go` line is 1.27.2 (since #86) while the release runs in
goreleaser-cross:v1.27.1-1. The image sets no GOTOOLCHAIN, so the release
silently downloads go1.27.2 from the Go proxy. No goreleaser-cross tag
carries Go 1.27.2 (registry tag list: newest v1.27.1-3), so there is no
published image to pin; this labels the drift where it lives instead of
leaving it unlabelled. Not forced by the core move; predates it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(scout): pin core's shared go-service-ci workflow to v0.19.4
ci.yml called codefly-dev/core/.github/workflows/go-service-ci.yml@main,
so this repo's CI changed whenever core's main did, with nothing here
recording it. Pinned to the linked core's tag. At v0.19.4 the file is
byte-identical to core main today, and its only input is `setup-run`,
which this caller already passes. AGENTS.md names the pin and says it
moves with the core bump, as service-redis and service-vault do.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Antoine Toussaint <312536060+antoinetoussaint-byte@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments