Repository navigation
oc-box 1.6.101 — easier upgrades and refreshed getting-started guides
Stable release from master, source
43dc12bf8cf32c76ea1c9416aeaaf1d3bb6889f0
(1.6.101+g43dc12b, full-history commit count 130).
Highlights
- Add optional tooling during upgrades.
upgrade --vaultandupgrade --tui
are independent, additive dependency requests. Use either or both when
selecting a supporting development release, including from stable:
oc-box upgrade --devel --vault --tui. - Enable extras without reinstalling through curl. A selected release can
gain missing optional dependencies even when it is already installed. Requests
preserve existing supported extras, verify the installation owner and target
capabilities, and retain nonmutating--checkbehavior. - A clearer first-install experience. The README and task-oriented guides
now lead with the GitHub installation path, alongside illustrated development
TUI documentation and a separate retained OpenCode 1.x legacy guide. - Publishing and CI maintenance. Temporary Ubuntu CI configuration uses the
working HTTPS Azure mirror with IPv4, retaining certificate, archive-signature
and freshness checks. A per-release announcement opt-out prevents a duplicate
stable social post for a rollout already covered by its development release.
Upgrade
Existing channel-aware GitHub installations can select stable with:
oc-box upgrade --stableAfter updating to this launcher, add vault dependencies on the saved channel:
oc-box upgrade --vaultTo select development and add either or both independent extras:
oc-box upgrade --devel --vault
oc-box upgrade --devel --tui
oc-box upgrade --devel --vault --tuiOlder launchers must perform their normal owning-manager update before accepting
the new flags. Recognized uv tool and pipx installations delegate to that
verified owner, not to the GitHub installer. Ambiguous source/plain-pip/shared
installations retain explicit manual guidance and all root/container refusals.
These flags install optional dependencies only: they do not initialize or unlock
a vault, change workspace credential policy, start a workspace or launch the UI.
Add --check for a nonmutating capability preview.
Stable/development boundary
The optional dashboard and other 1.7 development runtime features are not
promoted into stable. This stable package still provides the vault extra only;
an explicit TUI request against an unsupported stable target refuses. An
inherited TUI preference can survive a stable interval for a later return to
development.
Explicit channel switches can replace the launcher with an older release.
Launcher replacement does not roll back workspace/session state.
Validation and scope
- Source/package checks on Python 3.10 and 3.13, retained native OpenCode
1.19.5/2.2.6 integration, and the separate native 2.3.0 V2-only profile:
exact-source CI. - All seven supported distro package-provider checks:
distro matrix. - Clean-source wheel/sdist, optional-vault installation, source-identity,
checksum and build-only publication validation:
build-only gate. - Focused upgrade regressions include same-release additions, independent
vault/TUI requests, capability previews, ownership and downgrade refusals,
receipt verification, real offline Git/immutable installation and uv/pip
fixtures. The unavailable local native pipx fixture remains a recorded skip,
not a fabricated live pass.
Changes since the prior stable v1.6.94 are limited to upgrade selection/tooling,
guidance, documentation and CI/publication maintenance. Workspace execution,
history/recovery, credential delivery, backup/restore and dependency-provider
mappings are unchanged. Existing source-scoped host evidence retains its
original identity; no new Podman lifecycle, interactive UI, real-provider or
security-certification claim is made.
The release assets contain the publishing workflow's exact wheel and sdist,
validated-identity.json and SHA256SUMS; the matching packages are published
to the existing oc-box PyPI project.