[Obsidian] Handle Expired Account Errors#94
Merged
Conversation
rasulkireev
marked this pull request as ready for review
May 14, 2026 14:13
rasulkireev
force-pushed
the
codex/obsidian-expired-account-error
branch
from
May 14, 2026 14:37
a5ac062 to
5f1fa8c
Compare
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.
Summary
error: "account_expired".messagein the normal Obsidian notice/status UI, with a small fallback message if the response omits one.3.0.3by updatingpackage.json,package-lock.json,manifest.json,versions.json, and the plugin client version constant.Backend dependency
This expects the backend response from readwiseio/rekindled#9358:
{ "error": "account_expired", "message": "...", "upgrade_url": "..." }Release
After this PR merges, create and push tag
3.0.3to run the existing release workflow. The workflow builds the plugin and creates a draft GitHub release withmain.js,manifest.json, andstyles.css.Validation
npm testnpm run ciThe build passes. It still prints the existing non-fatal dotenv
preventAssignmentwarning.