Repository navigation
Release the simplified Reader extension v0.2.0 - #79
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
reader | cd1517e | Oct 09 2026, 08:03 AM |
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
1 participant
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.
Bump the simplified popup-only Chrome extension to v0.2.0 so it can be distributed as the link-inbox release. Package and manifest versions match.
Validation: existing extension build/pack script passes; the ZIP contains its popup, assets, icons and v0.2.0 manifest, with no background worker, content script, or side panel. The application behavior was verified in PR #78.
Allow lint-staged to skip paths excluded from root Biome configuration. The existing extension-only exclusion previously made metadata-only extension commits fail with no files processed; the hook still checks every matched root source file. The normal commit hook passes.
Update the existing status files with the verified production deployment and the remaining direct ChatGPT OAuth authorization/write-back boundary.
pnpm docs:checkpasses.