feat(update): show an install-origin-aware update command in the notice#140
Merged
Conversation
The passive "update available" notice pointed at a bare releases URL. Replace it with a copy-pasteable update command chosen by how the binary was installed, so the hint is directly actionable and the operator keeps running the verified channel themselves (no in-place self-update — forja update stays a deferred design-target): - npm installs (binary under node_modules/@lex0c/) hand off to the package manager, pinned to the announced version (npm i -g @lex0c/forja@<version>). - standalone installs re-run install.sh, carrying --prefix <dir> so a custom prefix is replaced in place, not duplicated at ~/.local/bin. - stock Windows (no POSIX sh) falls back to the releases page URL. The GitHub /releases/latest response stays untrusted: only the semver-validated version is response-derived; the command/URL is a build-time constant, never the tag_name. Notice remains cache-first, fail-silent, REPL-only, off in CI/--json, and once-per-release. Spec aligned (SECURITY_GUIDELINE 11.4, UI 4.10.9); 11.1-11.3 untouched.
Owner
Author
|
@codex review |
|
Codex Review: Didn't find any major issues. You're on a roll. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
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.
The passive "update available" notice pointed at a bare releases URL. Replace it with a copy-pasteable update command chosen by how the binary was installed, so the hint is directly actionable and the operator keeps running the verified channel themselves (no in-place self-update — forja update stays a deferred design-target):
The GitHub /releases/latest response stays untrusted: only the semver-validated version is response-derived; the command/URL is a build-time constant, never the tag_name. Notice remains cache-first, fail-silent, REPL-only, off in CI/--json, and once-per-release.
Spec aligned (SECURITY_GUIDELINE 11.4, UI 4.10.9); 11.1-11.3 untouched.