v0.0.32

What's Changed

Note

This release hardens googleDrive OAuth token lifecycle management and aligns
runtime, templates, and deployment guidance around request-time token
freshness. Updating is recommended if you stream from Google Drive, especially
in long-running deployments, multi-client scenarios, or Nginx
accel_redirect setups.

• Reworked googleDrive token handling to use a request-time OAuth token source
  instead of directly consuming cached token strings, with per-node singleflight
  refresh, reread-from-store behavior for shared config, immediate token
  persistence, and structured token blob storage including access_token,
  refresh_token, token_type, and expiry.
• Improved refresh safety and recovery by adding refresh backoff, stricter
  failure handling, 401 invalidate-and-retry behavior for request-owned Google
  API paths, and stronger minimum token lifetime enforcement before emitting
  accel_redirect handoff URLs.
• Replaced the old fixed refresh cadence with startup prewarm plus
  expiry-driven background prerefresh, reducing token-expiry windows while
  keeping request-time token acquisition as the correctness guarantee.
• Expanded automated coverage for googleDrive auth and streaming flows,
  including token blob persistence, legacy config migration, reread-store,
  singleflight concurrency, multi-instance reuse, persist-failure behavior,
  accel_redirect minimum validity, and 401 retry paths for lookup, redirect
  probing, and proxy streaming.
• Updated configuration templates, Nginx templates, and documentation to explain
  googleDrive deployment defaults, token blob write-back behavior, safer
  proxy vs accel_redirect rollout, and temporary debug logging patterns for
  internal Google Drive origin routing.

Full Changelog: v0.0.31...v0.0.32 (v0.0.31...v0.0.32)