Release v0.1.31 - #17
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Burnly v0.1.31
Introduces graceful cloud session expiration handling, secure OS keyring credential eviction on terminal auth errors, background sync quiescence, and an inline desktop re-authentication recovery flow.
Highlights
AUTH_REFRESH_TOKEN_EXPIRED,AUTH_REFRESH_TOKEN_INVALID,AUTH_REFRESH_TOKEN_REUSED,AUTH_SESSION_REVOKED), Burnly immediately purges expired credentials from memory and the OS keyring.<email> · Session expiredwith an actionable[Sign in again]button, allowing users to re-authenticate directly via PKCE without requiring an initial manual sign-out step.AUTH_REFRESH_TOKEN_EXPIRED) from cluttering the settings view.Privacy
Burnly continues to read usage-only metadata. It selects model identity, token
counters, and generation timestamps; it never reads prompt text, response
content, tool invocations, project paths, or sensitive credentials.
Install
Linux
Run:
curl -fsSL https://github.com/fikrilal/burnly/releases/latest/download/install-linux.sh | shFor a pinned install of this release:
curl -fsSL https://github.com/fikrilal/burnly/releases/download/v0.1.31/install-linux.sh | BURNLY_VERSION=v0.1.31 shWindows Preview
Download the Windows x64 installer from this release:
The Windows preview installer is not Authenticode-signed. Windows may show an
unknown publisher or SmartScreen warning. Only download Burnly from the
official GitHub release and verify the published
SHA256SUMS. Tauri updaterartifacts remain cryptographically signed.
macOS Preview
Run:
curl -fsSL https://github.com/fikrilal/burnly/releases/latest/download/install-macos.sh | shFor a pinned install of this release:
curl -fsSL https://github.com/fikrilal/burnly/releases/download/v0.1.31/install-macos.sh | BURNLY_VERSION=v0.1.31 shManual
.dmginstallation is also available:The macOS preview is unsigned and not notarized. If Gatekeeper blocks the
downloaded app, clear quarantine once after copying it to Applications:
Verification
This release was verified with local unit and integration tests across
CloudSession,AccountService, Tauri IPC contracts, and React UI components, including concurrencybarrier tests for race conditions between in-flight refresh and concurrent sign-in/out.
Release artifacts include
SHA256SUMS, GitHub build provenance, signed updaterartifacts,
latest.json, and thelatest-linux.jsoncompatibility alias.