Repository navigation
chore(release): v0.7.35 - #447
Merged
Merged
Conversation
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.
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
Cuts v0.7.35. Release-only change: the version string moves in the five carriers
deploy_gateguards, andCHANGELOG.mdgets its new section. No code, no test, no schema.Two commits landed since v0.7.34, and both are user-visible:
api_keys.statuspreviously had just two written values,activeat create/get andrevokedon soft delete, while the settings list filtered onstatus = '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 addspaused, widens the list toactive + paused, and leaves authentication acceptingactiveonly — 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 andget_or_create_api_keyis untouched.by_keyarray on the existingGET /api/transactionsresponse, sharing the samewhere_sqland binds assummary, so the groups add up to it structurally rather than by two parameter lists staying in step. It reads thetx_factsview, groups on the view'sapi_key_id, counts entries asSUM(row_count), keeps keyless rows as an explicit group ordered last, and takes the key name through a scalar subquery because a fourthLEFT JOINwould abandon the covering index (0.21s → 22.6s on the dev database).No schema change (still 18) — #445 needed none, since
api_keys.statusalready 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.35heading inCHANGELOG.md.Files
Cargo.toml,Cargo.lock— 0.7.34 → 0.7.35Dockerfile,docker-compose.yml— the same, three and two placesCHANGELOG.md— new section, in the repository's Chinese-prose conventionTests
cargo test— 614 passed, 0 failed (605 at v0.7.34)cargo fmt --check— cleancargo clippy --all-targets -- -D warnings— clean, and it reportsaitokenpool v0.7.35, so the manifest carrier did take effect rather than being a stale copythe_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.tomldeclares.