You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* fix: 2026.06 polish batch (#137, #138, #139, #140, #143)
- #137: document the always-re-sign dispatch contract in
ActionHandler.DispatchAction and drop the dead lint stubs.
- #138: change indexer health-addr default from :8082 to :8090 so it
no longer collides with control's InternalListenAddr default on
single-host dev setups.
- #139: distinguish jwt.ErrTokenExpired from other ValidateToken
failures so the web client can pick refresh-and-retry vs
forced-relogin instead of treating every failure as expired.
- #140: ToSnakeCase now keeps acronyms intact via SDK update; bumps
SDK pin to 16f6ede929e7 and updates the validator-error assertion
from "i_d must be a valid ULID" to "id must be a valid ULID".
- #143: errors_parity_test strips // and /* */ comments before
scanning sdk/ts/errors.ts so a commented-out export no longer
counts as live and skews the parity check.
* test(auth): align interceptor tests with #139 expired-vs-invalid split
The "invalid or expired token" wording was a single message for both
JWT failure modes — the #139 split swapped it for distinct
"token expired" / "invalid token" messages so the web client can pick
refresh-and-retry vs forced-relogin instead of treating every 401 as
expired. Update the existing tests to:
- TestAuthInterceptor_InvalidToken: assert "invalid token" + assert
the error does NOT contain "expired" (locks the disjoint behavior).
- TestAuthInterceptor_ExpiredToken: assert "token expired" so the
refresh-and-retry path stays covered.
- TestAuthInterceptor_WrongSecret: assert "invalid token" + assert
not "expired" — signature-invalid is a hard reject, not refreshable.
CI caught the stale assertion on PR #241 (Unit Tests job) — fix
applied as a follow-up so the polish bundle stays single-PR.
0 commit comments