Skip to content

auto-update: follow a dist-tag channel (updateTag) instead of always latest #602

Closed

Description

@ranxianglei

Problem

The auto-updater always follows the latest dist-tag. There is no way to pin an update channel (e.g. dev) for early adopters or rollouts.

Impact

Users who want (or are asked to test) pre-release builds must disable auto-update entirely and upgrade manually.

Suggested fix

updateTag config key + env override: which dist-tag the update check compares against and installs. PR #204 carries the original implementation (+125/−16) — needs rebase, and note the AGENTS.md §5 rule: changes to src/update.ts must ship behind a no-op release first.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions