Skip to content

chore(release): v0.7.34 - #444

Merged
argszero merged 1 commit into
mainfrom
chore/release-v0.7.34
Nov 9, 2026
Merged

argszero merged 1 commit into
mainfrom
chore/release-v0.7.34

Conversation

@argszero

@argszero argszero commented Nov 9, 2026

Copy link
Copy Markdown
Owner

Summary

Release commit for v0.7.34: the version string moves in all five carriers the deployment gate guards (Cargo.toml, Cargo.lock, Dockerfile ×3, docker-compose.yml ×2) and CHANGELOG.md gains a ## v0.7.34 section folding in the ## Unreleased entry that was sitting there for the GitHub sign-in work.

This release is mostly an accounting one. Twenty-eight commits have landed since v0.7.33, and seven of them change what a request costs — the gap filed as #437. A deployment still running v0.7.33 is billed by the arithmetic that shipped before every one of those fixes:

Unreleased commit PR Effect on a v0.7.33 deployment
ada9043 #412 Weekends and configured holidays billed at the peak rate — overcharges
eadfb9f #413 Four catalogue prices wrong, one cache-hit price written as 0
496a723 #416 Tiered and cache-write prices cannot be expressed in config.toml at all
544cf86 #417 A long input settled at the first (lowest) tier regardless of length — undercharges
357ab01 #433 Cache-write tokens billed at zero, the platform absorbing the cost
41ca047 #434 The admin model editor cannot set cache_write_input_per_m
a49f130 #436 Streaming Anthropic usage reports input_tokens net of the cache-read subtraction

Also shipping: cache-write billing asserted end to end (#442), GitHub sign-in for both browserless clients and the web login page (#443), four international vendors and the current-generation models (#414, #415), unknown config keys now rejected rather than silently ignored (#439), and fifteen documentation commits (#411, #418–#431) that bring prose back in line with code.

schema 16 → 18, in two idempotent steps — #417 raised it to 17, #443 to 18 — both of them ensure_column additions, so an existing database upgrades in place.

Related Issue

References #437 — this is the release that closes its gap; the tag itself is the release decision, which is the maintainer's.

Changes

  • Version string updated in all five carriers
  • CHANGELOG.md gains ## v0.7.34, replacing the ## Unreleased section
  • No code change: this commit touches version facts and release notes only

Tests

  • cargo test — 605 passed, 0 failed
  • cargo fmt --check clean
  • cargo clippy --all-targets -- -D warnings clean
  • deploy_gate version-carrying rules pass, including the_changelog_heading_carries_the_version_the_manifest_declares

Checklist

  • Branch named per convention (chore/release-vX.Y.Z)
  • Commit message uses Conventional Commits (chore(release): v0.7.34)
  • Single responsibility — version facts and release notes only

Twenty-eight commits since v0.7.33, and most of them change what a request
costs: the seven money fixes filed as #437 all ship here, plus cache-write
billing end to end, GitHub sign-in, four international vendors and the
current-generation models. schema 16 -> 18 across two idempotent migrations.

cargo test 605/0, fmt and clippy clean.
@argszero
argszero merged commit 05716b9 into main Nov 9, 2026
2 checks passed
@argszero
argszero deleted the chore/release-v0.7.34 branch November 9, 2026 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant