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
chore(sdk/ts): freeze core SDK changes at v0.1.9 #5684
As the maintainer moving OpenShell's TypeScript SDK to ai-openshell/sdk-typescript, I need core PRs to stop changing the imported SDK so that the two repositories do not diverge after the v0.1.9 import.
Problem Statement
Core still accepts changes under sdk/typescript/ and runs SDK build checks on PRs. The standalone repository imports that history and generates bindings from a pinned core release, so later core SDK edits require another manual import.
Impact / Why This Matters
SDK changes can land in the wrong repository and invalidate the migration snapshot. Manually checking every core PR does not enforce the freeze or tell contributors where to send their changes.
Proposed Design
Reject core PRs that add or modify sdk/typescript/, with a diagnostic directing SDK PRs to https://github.com/ai-openshell/sdk-typescript. Permit deletions for the later removal. Core proto PRs need no generated TypeScript bindings here. Remove SDK tasks from core PR checks and aggregate checks, and run protobuf lint with core's pinned Buf tool. Retain core release publication until the separate publishing cutover.
Acceptance Criteria
Branch Checks rejects added or modified TypeScript SDK files and identifies the destination repository.
Deletions and core-only proto changes pass the freeze check.
Core PR checks and aggregate checks no longer build, format, lint, or test the SDK.
Protobuf lint runs without installing SDK dependencies.
Contributor and agent guidance describes the freeze and destination.
Alternatives Considered
Keep importing subsequent core SDK changes. This requires manual reconciliation and delays ownership transfer.
Remove the SDK and publisher immediately. The standalone release automation is a separate cutover step.
@nvidia/openshell-sdk@0.1.10 is the last release of the old package: a stub that re-exports @ai-openshell/sdk@^0.1.0. @ai-openshell/sdk@0.1.10 can only be released after core tags v0.1.10, so the core Release workflow doesn't publish the stub. We publish it by hand after the SDK release.
Confirm Publish TypeScript SDK can publish @nvidia/openshell-sdk to GitHub Packages from ai-openshell/OpenShell after the repository transfer. The package is under the @nvidia scope. If the transfer broke publishing, decide whether to publish from an NVIDIA-owned repository or skip the stub.
Core Release finishes green. It no longer runs or expects publish-sdk-typescript.
sdk-typescript core-watch opens the chore(core): track v0.1.10 PR (hourly at :17, or dispatch it with tag=v0.1.10). Merge it.
sdk-typescript release publishes @ai-openshell/sdk@0.1.10 to npmjs.org with provenance.
Check that @ai-openshell/sdk@0.1.10 exports SandboxRef.applicationServiceUrls and gatewayServiceUrls, and that the generated types are reachable from both the root and /raw entry points.
Dispatch Publish TypeScript SDK in core on main with release-tag=v0.1.10, npm-version=0.1.10, make-latest=true. It fails without publishing if npmjs.org has no @ai-openshell/sdk@^0.1.0.
In a clean project, npm install @nvidia/openshell-sdk@0.1.10 resolves @ai-openshell/sdk@0.1.10, and imports from @nvidia/openshell-sdk and @nvidia/openshell-sdk/raw work.
Activity
pimlock commentedon Nov 20, 2026
v0.1.10 TypeScript SDK cutover checklist
@nvidia/openshell-sdk@0.1.10is the last release of the old package: a stub that re-exports@ai-openshell/sdk@^0.1.0.@ai-openshell/sdk@0.1.10can only be released after core tagsv0.1.10, so the core Release workflow doesn't publish the stub. We publish it by hand after the SDK release.Before tagging v0.1.10
applicationServiceUrlsandgatewayServiceUrls) with a merge commit, not squash. Its pin prerequisite is met: chore(core): track v0.1.10-pre.3 sdk-typescript#21 moved the core pin tov0.1.10-pre.3. Rebase it, regenerate bindings, and apply the maintainer DCO override for the imported commit.v0.1.10tag contains the stub, the freeze check, and the manual-onlysdk-typescript-publish.yml.Publish TypeScript SDKcan publish@nvidia/openshell-sdkto GitHub Packages fromai-openshell/OpenShellafter the repository transfer. The package is under the@nvidiascope. If the transfer broke publishing, decide whether to publish from an NVIDIA-owned repository or skip the stub.v0.1.10release notes.After core tags v0.1.10
publish-sdk-typescript.core-watchopens thechore(core): track v0.1.10PR (hourly at :17, or dispatch it withtag=v0.1.10). Merge it.releasepublishes@ai-openshell/sdk@0.1.10to npmjs.org with provenance.@ai-openshell/sdk@0.1.10exportsSandboxRef.applicationServiceUrlsandgatewayServiceUrls, and that the generated types are reachable from both the root and/rawentry points.mainwithrelease-tag=v0.1.10,npm-version=0.1.10,make-latest=true. It fails without publishing if npmjs.org has no@ai-openshell/sdk@^0.1.0.npm install @nvidia/openshell-sdk@0.1.10resolves@ai-openshell/sdk@0.1.10, and imports from@nvidia/openshell-sdkand@nvidia/openshell-sdk/rawwork.After the release
sdk/typescript/,sdk-typescript-publish.yml, and theTypeScript SDK Freezejob, along with their CI.md, CONTRIBUTING, AGENTS, and skill references. chore(sdk/go)!: remove the Go SDK, now at github.com/ai-openshell/sdk-go #5461 did the same for the Go SDK.