Conversation
First bundle pre-release published under the release-channels model (#149, try-hola/hola ADR 0005). Pins the upstream release candidate ghcr.io/get2knowio/remo-web:4.4.0rc1 by digest (built by get2knowio/remo's new rc-image.yml from tag rc-4.4.0rc1; `latest` untouched) and follows the publishing flow in docs/release-channels.md: this PR publishes ghcr.io/try-hola/remo:0.11.0-beta.1 with the moving tag suppressed, main's package.json stays on 0.10.1, and the next catalog regeneration lists both. - manifest: two new dormant-by-default enum params for the 4.4 console surfaces, REMO_WEB_HOST_ADMIN and REMO_WEB_REGISTRY_ADMIN (remo-web treats an empty value as unset, so the default is safe); upgrade metadata now recommends a pre-upgrade backup and points at the rc release notes. - compose: image pin + the two env passthroughs. - README: a "Beta channel" section with the install command. Refs #149 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Vck5KSX2CLxhohx14nb5Sh
Rolls the beta bundle forward to the new upstream release candidate, ghcr.io/get2knowio/remo-web:4.4.0rc2, pinned by digest (built by get2knowio/remo's rc-image.yml from tag rc-4.4.0rc2; `latest` untouched). The bundle version moves beta.1 -> beta.2 rather than republishing beta.1 with different contents: beta.1 is already in GHCR and listed in the catalog, and a pre-release tag is immutable in practice — re-pushing the same version with a different image is what the channel model exists to avoid. Both betas are newer than stable 0.10.1, so the next regeneration lists both; beta.1 retires when 0.11.0 ships, or sooner by deleting its GHCR tag. Upstream rc2 adds spec 024 (discovery resilience): the console keeps a host in the left rail and its terminals mounted through an intermittent discovery failure instead of clearing the workspace, with a grace window tunable via REMO_WEB_DISCOVERY_OFFLINE_GRACE_S. - compose: image pin 4.4.0rc1 -> 4.4.0rc2 (digest re-resolved from GHCR). - manifest: version, and upgradeNotesUrl -> the rc-4.4.0rc2 release. - README: the beta-channel example names the current pair. Refs #149 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
pofallon
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What / why
Refs #149. First bundle pre-release under the release-channels model (try-hola/hola ADR 0005):
remo 0.11.0-beta.1pins upstreamghcr.io/get2knowio/remo-web:4.4.0rc1@sha256:8b43b9…(multi-arch, built by get2knowio/remo#199's newrc-image.ymlfrom tagrc-4.4.0rc1; upstreamlateststill points at 4.3.6).Per
docs/release-channels.md, this PR is meant to stay open while the beta is being tried:ghcr.io/try-hola/remo:0.11.0-beta.1from this PR with the moving tag suppressed.main'spackage.jsonstays on0.10.1, so the stable entry is unchanged.catalog.jsonon the next regeneration frommain(workflow_dispatchof Build and Publish), after whichhola install remo --channel beta --as remo-betaworks.0.11.0once upstream releases 4.4.0; abandon by closing it and deleting the GHCR package version.Bundle changes
0.11.0-beta.1; two new dormant-by-default enum params for the 4.4 console surfaces,REMO_WEB_HOST_ADMINandREMO_WEB_REGISTRY_ADMIN(remo-web treats an empty value as unset, verified inweb/config.py);upgradenowpreUpgradeBackup: recommendedwith the rc release notes URL.Verification
node bin/validate-manifest.mjs src/remo/src/manifest.jsonOK.amd64,arm64; digest matches the pin.hola install remo --channel betaon a live host (needs the catalog regeneration first).🤖 Generated with Claude Code
https://claude.ai/code/session_01Vck5KSX2CLxhohx14nb5Sh