ConnectOnionRelease Channels
Stable stays safe while the next feature train moves through alpha, beta, and release candidates.
Current stable
v1.6.0
Installed by normal pip commands.
Current preview
v1.7.0a1
Available only to users who explicitly opt in.
A version is a compatibility promise, not a progress counter.
A version such as 1.6.3 maintains stable 1.6. New 1.7 features are tested as 1.7.0aN, 1.7.0bN, and 1.7.0rcN before 1.7.0 becomes stable.
Alpha
1.7.0aNIncomplete, usable slices for opt-in developers. Interfaces may still change.
Beta
1.7.0bNFeature-complete. Testing shifts to integration, upgrades, compatibility, and real users.
Release candidate
1.7.0rcNCould become stable unchanged. Only release-blocking fixes are accepted.
Stable / LTS
1.7.0Default for normal installs. New features move to 1.8; 1.7.x receives maintenance fixes.
Install stable
Normal installs and upgrades ignore preview releases. Publishing a preview does not move existing users off stable.
Join the preview track
The --pre flag is the explicit opt-in. An exact pin such as connectonion==1.7.0a1 also opts in and does not need --pre.
Current plan
1.6.x: stable maintenance fixes only.
1.7.0 previews: validate the complete coding-agent and ACP feature train.
1.7.0: stable/LTS. ACP is not deferred to a 1.7.1 feature release.
1.8.0 previews: new remote-browser sessions and hosted execution after the 1.7 gates close.
Track the live scope in the 1.7 milestone and the exact PR inventory and phase gates in issue #792.
Design Journal
Why the preview train uses alpha, beta, and RC
Release notes explain what changed. The design journal explains why 1.6 stays stable while ACP and coding-agent work is validated through opt-in 1.7 previews.
Read the design decision