Feature Request: Stable Release Channel for Copilot CLI #5203

Describe the feature or problem you'd like to solve

The rapid release cycle tends to introduce regressions, breaking daily use

Proposed solution

Introduction of separate release channels, similar to many other developer tools?

For example:

• Stable: recommended for day-to-day work, updated less frequently and focused on reliability
• Preview: rapid feature delivery and early access to changes

Example prompts or workflows

No response

Additional context

Recently, my workflow was broken by a regression that appears to be related to #5173. As a workaround, I pinned Copilot CLI to version 1.0.98.

Frequent releases can occasionally introduce regressions that impact day-to-day workflows.

A stable channel would allow users who prioritize reliability to upgrade at a slower pace, while users who want new features immediately could continue using a preview channel.