chore: bump github.com/maximhq/bifrost/core from 1.7.13 to 1.8.4 in /authbridge/authlib - #830
Conversation
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps [github.com/maximhq/bifrost/core](https://github.com/maximhq/bifrost) from 1.7.13 to 1.8.4. - [Release notes](https://github.com/maximhq/bifrost/releases) - [Changelog](https://github.com/maximhq/bifrost/blob/dev/docs/release-cadence.mdx) - [Commits](maximhq/bifrost@core/v1.7.13...core/v1.8.4) --- updated-dependencies: - dependency-name: github.com/maximhq/bifrost/core dependency-version: 1.8.4 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
fbd8325 to
d5087bf
Compare
Auto-tidied by dependabot-tidy workflow to keep cmd/* go.sum files in sync with authlib after a Dependabot bump. Signed-off-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
bifrost/core v1.8.0 raised its own go directive to 1.27.0, which Go propagates into every module in the workspace. #830 (v1.8.4) therefore rewrote 'go 1.26.5' to 'go 1.27.0' in all seven go.mod files and failed CI against go.work, which still says 1.26.5. Adopting v1.8.x is a Go 1.27 migration rather than a dependency bump: it needs authbridge/go.work bumped and the four digest-pinned golang:1.26-alpine builders in cmd/*/Dockerfile moved to 1.27. Those set GOWORK=off but not GOTOOLCHAIN, so they would not fail — they would silently download the 1.27 toolchain mid-build and ship images where a pinned 1.26 base bootstraps an unpinned 1.27. Expressed as a version range rather than update-types so v1.7.x patches keep flowing; #840 takes v1.7.15, the newest release still on go 1.26.5. There is no API break waiting — v1.8.4 was built and tested against authlib with go.work at 1.27.0 and the full suite passed — so this gates only the toolchain decision. Applied to the three directories that require bifrost and have a Dependabot entry: authlib directly, authbridge-proxy and authbridge-envoy indirectly via authlib. Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com> Signed-off-by: Hai Huang <huang195@gmail.com>
|
Superseded by #840, which takes v1.7.15 instead — the last release that does not force a Go toolchain migration. Why this failed: bifrost v1.8.0 raised its own That also explains the odd file list here — seven The version boundary:
v1.7.15 gets two patch releases with no toolchain change. Dependabot only proposes the newest version, so that middle ground never surfaced. What v1.8.x would actually cost — not the one-line And it buys nothing today: authlib touches exactly three bifrost symbols — Good news for later: I built and tested v1.8.4 locally with #838 gates Assisted-By: Claude Code |
Supersedes #830, which proposed v1.8.4. bifrost v1.8.0 raised its go directive to 1.27.0, and Go propagates that into every module in the workspace, so Dependabot's PR rewrote `go 1.26.5` to `go 1.27.0` in all seven go.mod files while authbridge/go.work stayed at 1.26.5. CI failed with: go: module . listed in go.work file requires go >= 1.27.0, but go.work lists go 1.26.5 v1.7.15 is the last release still on go 1.26.5, so this takes two patch releases with no toolchain change. Verified: every module's go directive and go.work are untouched, all modules build and vet, and the full authlib suite passes (48 packages). Adopting v1.8.x is a Go 1.27 migration rather than a dependency bump. It needs authbridge/go.work bumped AND the four digest-pinned `golang:1.26-alpine` builders in cmd/*/Dockerfile moved to 1.27 — those set GOWORK=off but not GOTOOLCHAIN, so they would not fail, they would silently download the 1.27 toolchain mid-build and ship images where a pinned 1.26 base bootstraps an unpinned 1.27. It also commits every developer to Go 1.27.0, roughly a month old at time of writing. None of that buys anything today: authlib touches exactly three bifrost symbols — bschemas.ModelProvider, bschemas.Anthropic and bschemas.OpenAI — in one six-line function in plugins/contextguru/plugin.go. Nothing in bifrost 1.8 is reachable from our code, and #830 is not a security update. The code side of v1.8.x is already clear, for whenever the toolchain move happens deliberately: v1.8.4 was built and tested locally with go.work at 1.27.0 and the full authlib suite passed, so there is no API break waiting. Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com> Signed-off-by: Hai Huang <huang195@gmail.com>
bifrost/core v1.8.0 raised its own go directive to 1.27.0, which Go propagates into every module in the workspace. #830 (v1.8.4) therefore rewrote 'go 1.26.5' to 'go 1.27.0' in all seven go.mod files and failed CI against go.work, which still says 1.26.5. Adopting v1.8.x is a Go 1.27 migration rather than a dependency bump: it needs authbridge/go.work bumped and the four digest-pinned golang:1.26-alpine builders in cmd/*/Dockerfile moved to 1.27. Those set GOWORK=off but not GOTOOLCHAIN, so they would not fail — they would silently download the 1.27 toolchain mid-build and ship images where a pinned 1.26 base bootstraps an unpinned 1.27. Expressed as a version range rather than update-types so v1.7.x patches keep flowing; #840 takes v1.7.15, the newest release still on go 1.26.5. There is no API break waiting — v1.8.4 was built and tested against authlib with go.work at 1.27.0 and the full suite passed — so this gates only the toolchain decision. Applied to the three directories that require bifrost and have a Dependabot entry: authlib directly, authbridge-proxy and authbridge-envoy indirectly via authlib. Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com> Signed-off-by: Hai Huang <huang195@gmail.com>
Bumps github.com/maximhq/bifrost/core from 1.7.13 to 1.8.4.
Release notes
Sourced from github.com/maximhq/bifrost/core's releases.
... (truncated)
Commits
6d60595core changelog for the release cut (#6605) --skip-cice56d2dcore changelog (#6603)b36efdbcore changelog9157bafcore version bump (#6601) --skip-core-test02aee90core version bump (#6599)16d4220docs: document KMS-encrypted S3 buckets for log object storage (#6497)e4a7d3cfix: unsupported reasoning signature to be stripped (#6593)935e759fix: unsupported reasoning signature to be stripped1cd3635fix: clear passthrough for non claude models in non native claude model provi...141e9edfix: clear passthrough for non claude models in non native claude model provi...