Repository navigation
chore(deps): bump OpenShell to v0.1.6-rhaiv.2 - #874
Conversation
Bump the pinned OpenShell gateway/supervisor/sandbox/CLI images from v0.1.5-rhaiv.3 to v0.1.6-rhaiv.2 and vendor the matching Helm chart. Triage of the 57-commit range found only additive, opt-in changes: new suspend/resume sandbox RPCs, a shared supervisor pool/HA feature, an additional destination-CA trust option, an opt-in hashed service-routing hostname format, and required-middleware-binding enforcement. None of these are set by HyperShell's Helm values builder, so no RBAC escalation or code change is needed. go build/vet/test and all make check components pass. The gateway's rhaiv.4+ change to refuse startup without an auth mechanism (tracked in issue 809, still needs a maintainer decision) is present in this range too; not resolved here. The console dashboard pin is left at v0.1.1 pending quay.io digest resolution for the newer v0.1.3 release (tracked in issue 760); this is a missing-feature gap, not a breaking one, since every proto change in this range is additive. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
hypershell-builder
Bot
added
the
agent/reviewable-code
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
 |
HyperShell environment destroyedThis ephemeral OpenShift environment has been destroyed. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #874 +/- ##
=======================================
Coverage 45.04% 45.04%
=======================================
Files 388 388
Lines 30641 30641
=======================================
Hits 13801 13801
Misses 15094 15094
Partials 1746 1746
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
A fresh scheduled run resolved the same target (v0.1.6-rhaiv.2) this PR already covers and found three more stale open PRs (#810, #822, #845) from earlier runs that were never flagged for cleanup. Add a check-for- an-open-PR step to the skill so future runs stop duplicating PRs when the resolved target hasn't changed, and record the finding in the Learnings log. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Re-ran the scheduled Stale PRs to close: while checking, found three older open PRs from earlier runs that this PR already supersedes and that were never flagged:
All three target tags that are no longer current; a maintainer can close them. On the failing "Unit / Shell" check: reproduced Pushed a small follow-up commit to this branch adding a "check for an already-open PR before creating a new one" step to |
|
Scheduled Per the duplicate-PR guard this PR's own branch added yesterday, no new branch or PR was opened. This PR is still Added a note to this PR's description listing the three earlier bump attempts (#810, #822, #845) it supersedes, so a maintainer can close them in one pass. |
Summary
This change moves HyperShell to a newer OpenShell gateway version.
v0.1.5-rhaiv.3v0.1.6-rhaiv.2The change updates the pinned gateway, supervisor, sandbox, and CLI image tags. It also updates the vendored Helm chart in
charts/openshell/to match. No control-plane code changes were needed.What changed in the new OpenShell version
The new version range has 57 upstream commits. All contract-facing changes are additive and optional. They do not break HyperShell:
None of these new options are set by HyperShell's Helm values. The new Helm chart does not add any required permission that HyperShell's controller is missing.
Known issue carried forward (not fixed in this PR)
Starting with an earlier patch in this version line, the OpenShell gateway refuses to start if no login method (OIDC, mTLS, operator auth, or token) is configured and "allow unauthenticated users" is not explicitly turned on. HyperShell can still reconcile a gateway into exactly that state today. This needs a maintainer decision on how to handle it. It is tracked in issue #809. This PR does not change that behavior.
Console dashboard (not bumped in this PR)
The per-gateway console dashboard image is still pinned to its current release. A newer release exists and is built and tested against this new gateway version, but this agent could not reach
quay.iofrom its sandbox to look up the new image's digest. This gap is already tracked in issue #760; a comment was added there with the newer release name. This is a missing-feature gap only. The current console still works correctly with the new gateway, because every gateway API change in this version is additive.Supersedes earlier bump attempts
This PR replaces three earlier automated bump attempts that targeted
tags the upstream tag list has since moved past. Each was opened by an
earlier scheduled run before the tag advanced again the next day. They
are stale and a maintainer can close them:
v0.1.5-rhaiv.4) - conflicts withmainv0.1.6-rhaiv.0) - conflicts withmainv0.1.6-rhaiv.1) - superseded by this PR'sv0.1.6-rhaiv.2Testing performed
go build,go vet, andgo testfor the control plane: all pass.make checkpolicy checks (forbidden terms, Kind API conformance, dependency pins, CI component registration, deploy-manifest orphans, dependency age, OpenShell version sync, CLI/TUI generator drift, spec ID citations, CI impact scopes, release bundle, coverage report): all pass.Follow-ups
🤖 Generated with Claude Code