Skip to content

chore(release): v0.7.35 - #447

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

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

Conversation

@argszero

Copy link
Copy Markdown
Owner

Summary

Cuts v0.7.35. Release-only change: the version string moves in the five carriers deploy_gate guards, and CHANGELOG.md gets its new section. No code, no test, no schema.

Two commits landed since v0.7.34, and both are user-visible:

  • feat(api-keys): pause and resume a key instead of only revoking it #445 — an API key can be paused and resumed instead of only revoked. api_keys.status previously had just two written values, active at create/get and revoked on soft delete, while the settings list filtered on status = 'active', so its "not active → grey pill" branch was unreachable and revocation was a one-way door the user could not even see afterwards. This adds paused, widens the list to active + paused, and leaves authentication accepting active only — a paused key stops serving, which is the point. The deliberate asymmetry is that the key currently acting as the session credential refuses to pause itself: the distribution key and the session credential are one row, so pausing it would 401 the session, which mints a fresh active key on next login and leaves nothing paused; the other direction would lock the user out. The guard sits at the API entry and get_or_create_api_key is untouched.
  • feat(transactions): break the summary down by API key #446 — the transactions page can break its summary down by API key. A by_key array on the existing GET /api/transactions response, sharing the same where_sql and binds as summary, so the groups add up to it structurally rather than by two parameter lists staying in step. It reads the tx_facts view, groups on the view's api_key_id, counts entries as SUM(row_count), keeps keyless rows as an explicit group ordered last, and takes the key name through a scalar subquery because a fourth LEFT JOIN would abandon the covering index (0.21s → 22.6s on the dev database).

No schema change (still 18) — #445 needed none, since api_keys.status already existed.

The eight version carriers: Cargo.toml (1), Cargo.lock (1), Dockerfile (3 — header, build example, run example), docker-compose.yml (2 — header, image:), and the new ## v0.7.35 heading in CHANGELOG.md.

Files

  • Cargo.toml, Cargo.lock — 0.7.34 → 0.7.35
  • Dockerfile, docker-compose.yml — the same, three and two places
  • CHANGELOG.md — new section, in the repository's Chinese-prose convention

Tests

  • cargo test — 614 passed, 0 failed (605 at v0.7.34)
  • cargo fmt --check — clean
  • cargo clippy --all-targets -- -D warnings — clean, and it reports aitokenpool v0.7.35, so the manifest carrier did take effect rather than being a stale copy
  • No new tests: a release commit changes no behaviour. The two gates that guard these carriers (the_deploy_artifacts_carry_the_version_the_manifest_declares, the_changelog_heading_carries_the_version_the_manifest_declares) are among the 614.

Related Issue

No issue — release cut on the maintainer's instruction. Tag and image follow this merge, in that order; the publish workflow refuses a tag that is not the version Cargo.toml declares.

Two commits since v0.7.34, no schema change (still 18):

- #445 lets an API key be paused and resumed instead of only revoked.
- #446 breaks the transactions summary down by API key.

The version string moves in the five carriers deploy_gate guards: Cargo.toml,
Cargo.lock, Dockerfile (three places), docker-compose.yml (two) and the new
CHANGELOG heading.
@argszero
argszero merged commit 7bbfe17 into main Nov 12, 2026
2 checks passed
@argszero
argszero deleted the chore/release-v0.7.35 branch November 12, 2026 11:40
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