Repository navigation
fix: move to OpenShell 0.1.6 - #126
Merged
Merged
Conversation
Gkrumbach07
force-pushed
the
next
branch
2 times, most recently
from
October 23, 2026 01:28
134eb25 to
3d09d8d
Compare
Gkrumbach07
changed the title
Gkrumbach07
changed the title
Gkrumbach07
changed the title
Moves the OpenShell release this branch is built on from 0.1.5 to 0.1.6: the gateway and supervisor images the compatibility suite runs against, and the Go SDK at the commit upstream tagged v0.1.6 (ac7f615cd12d). OpenShell-Release: 0.1.6 Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Gkrumbach07
changed the title
Gkrumbach07
marked this pull request as ready for review
October 27, 2026 20:04
Contributor
|
/lgtm |
danreed-rh
approved these changes
Oct 30, 2026
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
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.
This is
next: the move to the upcoming OpenShell release, opened early (ADR 0005, decisions 7 and 8). The Follow upstream workflow keeps the branch and rewrites this description, so an edit made here by hand is lost.Where it is.
nextpins OpenShell0.1.6, a stable release.mainpins0.1.5. This is ready to merge once its checks pass.What moved. One commit, always the first after
main. It changesdeploy/ci/gateway-pins.json,backend/go.modandbackend/go.sum, and the generated block ofREADME.md.next0.1.6ghcr.io/nvidia/openshell/gateway:0.1.6@sha256:f0b36dba21d282c52e498c25289658cfd6cd4f343b0069fde5609e25b002cdeaghcr.io/nvidia/openshell/supervisor:0.1.6@sha256:ce859a7d77ee515d3fe0b3c7dc61286516f402eb1d25c761d806d9ae5ed96c0bv0.0.0-20261027154453-ac7f615cd12dWork that needs the upcoming release goes here. Open a pull request into
nextonly for a change that cannot build or pass onmain; everything else goes tomain. Whenmainmoves, the workflow rebasesnextonto it and force-pushes, so rebase a branch cut fromnextafter that. Commits onnextbesides the pin move: 1.CI runs on every push to
next. Itscompatjob is the compatibility suite against the release pinned here, on the SDK pinned here.Merging. Nothing merges this automatically. Use Rebase and merge, so the pin move and each commit on
nextland onmainas they are.After the merge, a release is cut by itself once CI has passed on
main. Nobody chooses its version: it is the console's next patch on the gateway release linemainthen pins.