You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
sandbox: upgrade OpenShell dependency from v0.0.63 to v0.0.67 #2550
Fullsend pins OpenShell v0.0.63 in .github/scripts/openshell-version.sh. The latest release is v0.0.67 (4 minor versions behind). The gap widens with each OpenShell release, and fullsend cannot use upstream features like --runtime-credentials (available since v0.0.61, needed for #776).
What should happen
Fullsend should run on OpenShell v0.0.67. The version pin and install SHA should target the latest release.
Breaking changes between v0.0.63 and v0.0.67
There are no breaking changes in this range. All changes are additive or internal to OpenShell:
changed the title [-]sandbox: upgrade OpenShell dependency from v0.0.54 to v0.0.67[/-][+]sandbox: upgrade OpenShell dependency from v0.0.63 to v0.0.67[/+]on Jun 23, 2026
This is a straightforward dependency version bump with no breaking changes in the upgrade range.
Problem: The OpenShell version pin in .github/scripts/openshell-version.sh is at v0.0.63, four minor versions behind the latest v0.0.67.
Fix: Update OPENSHELL_VERSION to 0.0.67 and OPENSHELL_SHA to the SHA for the v0.0.67 release tag. The reporter confirmed all changes between v0.0.64–v0.0.67 are additive or internal.
Impact: Unblocks access to upstream features (e.g., --runtime-credentials), which is a prerequisite for #776.
Note: A code agent run completed successfully on this issue. If that work produced a branch, a PR should be opened from it.
# Proposed test verification
1. Source the updated openshell-version.sh and confirm OPENSHELL_VERSION=0.0.67
2. Confirm OPENSHELL_SHA matches the v0.0.67 tag in NVIDIA/OpenShell
3. Run CI to verify sandbox environments start correctly with v0.0.67
Labels: Issue already has correct labels (type/chore, dependencies, component/sandbox, component/ci); adding priority/low since this is a non-breaking dependency bump.
Activity
maruiz93 commentedon Jun 23, 2026
/fs-code
fullsend-ai-coder commentedon Jun 23, 2026
🤖 Finished Code · ✅ Success · Started 11:17 AM UTC · Completed 11:23 AM UTC
Commit:
4e21a60· View workflow run →[-]sandbox: upgrade OpenShell dependency from v0.0.54 to v0.0.67[/-][+]sandbox: upgrade OpenShell dependency from v0.0.63 to v0.0.67[/+]fullsend-ai-triage commentedon Jun 23, 2026
🤖 Finished Triage · ✅ Success · Started 11:33 AM UTC · Completed 11:35 AM UTC
Commit:
4e21a60· View workflow run →fullsend-ai-triage commentedon Jun 23, 2026
Triage Summary
This is a straightforward dependency version bump with no breaking changes in the upgrade range.
Problem: The OpenShell version pin in
.github/scripts/openshell-version.shis at v0.0.63, four minor versions behind the latest v0.0.67.Fix: Update
OPENSHELL_VERSIONto0.0.67andOPENSHELL_SHAto the SHA for the v0.0.67 release tag. The reporter confirmed all changes between v0.0.64–v0.0.67 are additive or internal.Impact: Unblocks access to upstream features (e.g.,
--runtime-credentials), which is a prerequisite for #776.Note: A code agent run completed successfully on this issue. If that work produced a branch, a PR should be opened from it.
Labels: Issue already has correct labels (type/chore, dependencies, component/sandbox, component/ci); adding priority/low since this is a non-breaking dependency bump.
maruiz93 commentedon Jun 23, 2026
This should have been done by renovate. Related: #2483