-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
[Feature]: Support foreground extended-stable package updates #99808
Copy link
Copy link
Closed
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:ux-frictionUser-facing flow adds avoidable confusion or support burden without fully blocking progress.User-facing flow adds avoidable confusion or support burden without fully blocking progress.issue-rating: 🌊 off-meta tidepoolIssue quality rating does not apply to this item.Issue quality rating does not apply to this item.maintainerMaintainer-authored PRMaintainer-authored PRmaturity:stableIssue affects a taxonomy feature currently scored M4/M5.Issue affects a taxonomy feature currently scored M4/M5.
Description
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:ux-frictionUser-facing flow adds avoidable confusion or support burden without fully blocking progress.User-facing flow adds avoidable confusion or support burden without fully blocking progress.issue-rating: 🌊 off-meta tidepoolIssue quality rating does not apply to this item.Issue quality rating does not apply to this item.maintainerMaintainer-authored PRMaintainer-authored PRmaturity:stableIssue affects a taxonomy feature currently scored M4/M5.Issue affects a taxonomy feature currently scored M4/M5.
Type
Fields
Priority
None yet
Summary
Add a net-new
extended-stableupdate channel for foreground npm package updates and on-demand status checks.Problem to solve
OpenClaw is introducing a trailing supported-month npm release line, but the CLI currently exposes only
stable,beta, anddev. Operators cannot select, persist, inspect, or safely update to the new line without targeting a raw package spec themselves. The existingstablechannel must continue to mean npmlatest.Proposed solution
extended-stableCLI/config support without changing existing channel defaults.extended-stableselector and verify the selected exact package before installation.latest.Alternatives considered
stable: rejected becausestablealready maps to npmlatestand is a shipped config/CLI contract.--tag extended-stableonly: rejected because it does not provide persisted channel semantics, shared status behavior, Git safeguards, or startup/background boundaries.latest: rejected because it can silently install a different release line than the operator selected.Impact
Affected: Operators who want the trailing supported-month npm release.
Severity: Blocks use of the new release line through supported CLI/config workflows.
Frequency: Every install, update, or status check targeting that line.
Consequence: Without this, operators must use raw package-manager commands and cannot rely on OpenClaw's downgrade, staging, plugin-convergence, Gateway restart, or status contracts.
Evidence/examples
openclaw update --channel extended-stableupdate.channel: "extended-stable"Additional information
This is intentionally package-only and foreground/on-demand for the first release. It does not add a
dailychannel or extended-stable plugin selectors.