Repository navigation
feat(update): add updateTag config to follow a dist-tag channel - #204
Merged
Merged
Conversation
Contributor
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)npm install -g billion-context@pr-204Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf billion-context-pr204.tgz
npm install -g packageThis comment is automatically updated on each push. |
Owner
Author
|
Review vs master 3cd85b6: ✅ design correct — needs rebase (conflict in Code findings:
Pre-merge checklist:
Related: #606 (three-state mode from #86) wants the same config surface — worth merging the config plumbing once. (tracking: #602) |
…se-aware comparison Rework of PR#204 (issue #602) onto current master: - updateTag config (file key `updateTag`, env `ACP_UPDATE_TAG`, default `latest`): the auto-updater and `bili update` fetch the configured channel's registry document instead of always /latest. PR preview tags (pr-N) are only followed when explicitly configured. - isVersionNewer replaces the 3-part numeric compare: prereleases now order older than their release (0.1.46-pr.202.1 < 0.1.46) and prerelease parts compare numeric-then-lexicographic — fixes a beta install never seeing its own final release (0.1.47-beta.1 == 0.1.47 under the old compare). - Conflicts resolved by union with #609 (resolveProxy egress wiring kept; channel rides the same fetch) and #327 (staleInstallStatus branch kept). - Tests: pure-helper coverage via exported registryUrlFor/normalizeUpdateTag (the old fetch-mocked tests predate the #327 source-checkout guard, which short-circuits checkForUpdate before fetch in any git checkout). - Docs: CONFIGURATION.md/.zh-CN.md rows for ACP_UPDATE_TAG. Fixes #602
ranxianglei
force-pushed
the
2026-08-23_auto-update-by-channel
branch
from
September 7, 2026 13:13
628cf33 to
d5680a0
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.
Rework of #204 (fixes #602) onto current master — single commit
d5680a0, mergeable.What (unchanged from the original PR)
updateTagconfig — file keyupdateTag, envACP_UPDATE_TAG, defaultlatest. Both the background auto-updater andbili updatefetch the configured channel's registry document instead of always/latest. PR-preview dist-tags (pr-N) are only followed when explicitly configured, so publishing a PR preview never pulls a stable user forward.isVersionNewerreplaces the 3-part numeric compare: prereleases order older than their release (0.1.46-pr.202.1 < 0.1.46), prerelease parts compare numeric-then-lexicographic. Fixes a real edge: a beta install (0.1.47-beta.1) parsed equal to its final (0.1.47) and would never see the release.Rework notes
resolveProxyegress wiring kept (the channel rides the samefetchWithEgress), 在omp环境下使用,出现异常情况 #327staleInstallStatusbranch kept.checkForUpdatebefore any fetch when running inside a git checkout — they can never pass on CI. Coverage moved to exported pure helpersregistryUrlFor/normalizeUpdateTag(channel follow, default+trim, encodeURIComponent for exotic tags).CONFIGURATION.md/CONFIGURATION.zh-CN.mdrows forACP_UPDATE_TAG.This touches
src/update.ts— the updater itself. Per §5 it must not ride the next release directly: