Skip to content

Usage Pace 0.4.2 — account-merging fixes

Choose a tag to compare

View all tags
@scowalt scowalt released this 23 Oct 20:28
· 6 commits to main since this release
v0.4.2
d7bdcf5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Patch release for the remaining 0.4.1 account-merging gap with bb 0.46.1's cached last-success timestamps on failed reads.

Fixes

  • Healthy quota wins over failed duplicates. Merged accounts prefer the newest healthy (status: "ok", not stale) measurement, even when a failed source reports a newer last-success timestamp. A transient machine read failure no longer makes a healthy merged account stale or turns a two-account pool into 1/2 available · 1 unknown.
  • Known accounts keep their metadata through errors. When an error keeps the resource's known identity but omits email, plan, or plan label, retain the cached fields. Email-based aliases and plan weights remain available. Explicit identity changes still discard the old account's metadata and windows; never-known identities remain separate.
  • Failures remain visible and honest. Merged hosts, sources, and source-error messages remain visible. An account whose only source fails stays stale and counts as unknown despite retaining its alias and plan. When all sources are stale, the newest observation still wins.

Release artifacts remain built with BB 0.44.0 / SDK 0.5.29; minimum requirements are unchanged. Saved resets remain read-only. The CLI JSON accounts/providers alias, nullable pace, token totals, and Codex-only --resets behavior are unchanged.

Verification

  • The final collector/merging test set produced 7 failures with 0.4.1's source and passed all 22 tests with this fix. Coverage includes realistic last-success timestamps, retained aliases/plan metadata, sole-source failures remaining unknown, unchanged all-stale ordering, and explicit login changes.
  • All 390 Vitest tests, 3 token-total tests, and TypeScript passed. TypeScript, the complete test suite, and release validation were rerun before merging.
  • Comment policy passed across 96 files with zero violations; all 13 policy regression tests passed. Staged policy, the ordinary pre-commit hook, and redacted secret scanning passed.
  • Production-only rebuilds and release validation passed with BB 0.44.0 / SDK 0.5.29 and BB's bundled npm 11.16.0, including version/SDK metadata, host digest, and isolated backend/host smoke loading. No provider requests were made by release validation.
  • Synthetic desktop/mobile browser checks retained the 2/2 pool, alias, source-error message, matching saved-reset badge, view-specific locations, and reset-reader provenance without compact-strip/dialog overflow.
  • PR, resulting-main, and release-tag Woodpecker CI passed. The annotated release tag points to merge commit d7bdcf5b16f675491726c59b6bb96cf767041de9, whose tree exactly matches the reviewed and tested PR head.
  • Not yet verified: live installation or upgrade of 0.4.2 on either bb server. The reproduction and before/after evidence use only synthetic identities and example.test addresses and are recorded in multi-account verification.

New installations

bb plugin install 'git:https://github.com/scowalt/bb-plugin-usage-pace.git@v0.4.2'
bb plugin config usage-pace set showStrip true

The second command enables the optional strip. Use @^0.4.2 instead of the exact tag to track compatible releases.

Upgrades

Inspect the requested and resolved source first:

bb plugin source usage-pace

For repository/branch-tracking installs whose branch contains 0.4.2, or a release-range install that admits this tag, update in place and keep settings:

bb plugin update usage-pace

An exact tag or commit does not advance to a newer tag with update. Moving a pinned install, or changing an existing install to a tag or range, requires removal first. Removal deletes settings, secrets, and schedules. Record the current configuration and restore your settings after reinstalling:

bb plugin config usage-pace
bb plugin remove usage-pace
bb plugin install 'git:https://github.com/scowalt/bb-plugin-usage-pace.git@v0.4.2'

Use @^0.4.2 in the final command for compatible-release tracking. Do not use plugin install as an in-place upgrade: bb 0.46.1 rejects the duplicate plugin ID.

Publishing this release does not install, update, reload, or reconfigure plugins on either live bb server.

PR #8 · Full changelog

Assets 2
Loading