Repository navigation
Release Threadline v0.1.1 - #4
Merged
Merged
Conversation
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.
Threadline v0.1.1 adds durable drafts, publication history and local scheduling, along with connected profile/thread/tag navigation, notifications, account-aware actions, OAuth and MP4 video support. Following retains the approved responsive layout and now reuses provider home feeds; Bluesky batches notification lookups and reuses sessions to avoid per-item login requests.
The commits group native providers/authentication, persistence/scheduling, social workspace, Composer/media, documentation, and release metadata. UI fixtures are tracked so the suite runs from a clean checkout. The app's displayed version is derived from package metadata.
Validation: 78 browser tests and 89 native tests passed; type checks, lint, production build, Rust formatting and all-target Clippy with warnings denied passed. Final version-display assertion passed. Independent release reviews and a clean-checkout runtime audit are recorded for this head.
Production Bluesky browser OAuth still requires hosted client metadata and its registered callback; the app-password fallback remains available. Scheduling is local and overdue jobs require review. Provider tests use controlled fixtures rather than live account mutations.
After merge, the v0.1.1 tag will trigger the existing four-platform installer build, checksum and provenance-attestation workflow. No locally built installers are uploaded.