v0.1.2
This release replaces the Google Drive login flow with Google’s limited-input device flow, making Google authentication work cleanly on headless machines and over SSH.
What changed
- Google auth no longer depends on a localhost callback server or an automatically opened browser.
- retentra auth google login now prints a verification URL and code that can be completed from another device.
- Token polling now follows Google’s device-code flow, including pending, slow-down, denied, and expired responses.
- Added RETENTRA_GOOGLE_DEVICE_CODE_URL for environments that need to override the default device-code endpoint.
- Updated the CLI help, README, configuration docs, and sample env file to match the new flow.
Notes
- Existing token storage behavior is unchanged:
- OS secret store remains the default
- --allow-file-token-storage is still required if you want file-backed storage
- Google Drive output behavior is unchanged outside of authentication.
Verification
- go test ./... passes