Merged
Conversation
|
🤖 Claude security review — HEAD: 5ae5822 Scope: Update the auto-update notification example version string from ✅ No security or convention issues found. Auto-review by Claude Code Action. |
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.
Summary
The auto-update example in the How do I update? FAQ still quoted
v0.4.5— that's the old pre-migration tag scheme, which no longer exists. Bumped tov1.1.0(the actual current latest) so the example matches what a user would see.Applied symmetrically to
README.mdanddocs/README_zh.md.Why this PR
Not strictly necessary — nothing was broken — but it was misleading. Also serves as a smoke test for the full CI pipeline:
docs:)docs:is not bumping)Test plan
This is a docs-only 2-line change in a user-facing FAQ. No functional impact.