chore(release): prepare v0.5.0 - #186
Merged
Merged
Conversation
- CHANGELOG: add [0.5.0] section (litellm, x_search, MiniMax-M3, 1M context, content-blocks, attachment MIME, Python SDK 0.7.0, cache-aware billing, gpt-5.1 priority, playwright profile, #173 proto fix, 429 fix, cache-TTL) - install.sh: default SHANNON_VERSION v0.4.0 -> v0.5.0 - docker-compose.release.yml: bump example header to v0.5.0 - docs/rocky-linux-quickstart: note committed proto runtime files supersede the manual generation workaround (#173) - .dockerignore: exclude generated **/*.pb.go so a stale dev-tree copy can't clobber buf-generated protos during image builds
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release prep for v0.5.0. Version bump + changelog + a build-hygiene fix. No code/runtime changes beyond
.dockerignore.This does not publish anything. The release images + GitHub release are produced by
release.ymlwhen av0.5.0tag is pushed (after this merges tomain).Changes
[0.5.0]section covering work since v0.4.1: LiteLLM provider, xAIx_search, MiniMax-M3, Anthropic 1M context, content-blocks passthrough, attachment MIME classification, Python SDK 0.7.0, cache-aware quota/billing (1h/5m TTL,cache_aware_total_tokens), gpt-5.1 priority, optionalplaywright-serviceprofile, the Missing runtime files #173 proto fix, 429 rate-limiter fix, cache-TTL uniformity, desktop libs.SHANNON_VERSIONv0.4.0→v0.5.0.v0.5.0.grpc_tools.protocworkaround; regenerate viamake proto-local(pinned protobuf 5.x), never an arbitrary protoc version.**/*.pb.goso a stale dev-tree copy can't clobber buf-generated protos during Go image builds (Pythongrpc_gen_pb2.pyare committed and intentionally not matched).Local verification (before this PR)
mainworktree (mirrors CI).5.29.2,grpc_genimports OK, cache-token fields present at runtime (Missing runtime files #173 proven)./health, orchestrator/readiness, and/api/v1/toolsall green (keyless infra smoke)..dockerignorehardening validated — orchestrator builds even from a dirty tree with stale.pb.go.Release steps after merge (separate, explicit)
v0.5.0on mergedmain→ triggersrelease.yml(builds/pushes 5 images +latest, creates GitHub release).