Skip to content

OpenShell v0.1.8 compatibility (tracking) - #82

Draft
ilanh wants to merge 1 commit into
mainfrom
openshell-next
Draft

ilanh wants to merge 1 commit into
mainfrom
openshell-next

Conversation

@ilanh

@ilanh ilanh commented Nov 9, 2026

Copy link
Copy Markdown
Owner

Tracking PR for #80. Draft: do not merge until OpenShell v0.1.8 is stable. Promotion steps are in docs/RELEASING.md (added in the automation PR for #79).

openshell-next = main + the OpenShell pin moved to the newest upstream tag, prereleases included. Once #79 merges, .github/workflows/openshell-next.yml will merge main into it daily, move the pin on new upstream tags and report on #80.

Now: openshell-policy-schema and openshell-policy are on v0.1.8-pre.3 (53b8eec2, compare with v0.1.7). Nothing broke: fmt, clippy -D warnings, cargo test --locked, gateway_policies, gen-docs.sh --check and gen-actions-docs.sh --check all pass locally with no code changes.

Before promoting (checklist mirrors #80)

Pins openshell-policy-schema and openshell-policy to v0.1.8-pre.3 (53b8eec2). Upstream changes: NVIDIA/OpenShell@v0.1.7...v0.1.8-pre.3

Refs #80

Signed-off-by: Ilan Harel <ilan@Ilans-MacBook-Pro.local>
@ilanh ilanh added the openshell-next Tracking the next OpenShell release on the openshell-next branch label Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

openshell-next Tracking the next OpenShell release on the openshell-next branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant