Skip to main content

Compatibility

Version requirements between Cybershuttle components, the commits this site documents, and the contracts that change only in a coordinated release. Consult it before every upgrade: the components are released separately and all before 1.0.

Documented versions​

Statements on this site describe each repository at these commits; a later build may behave differently.

ComponentRepositoryVersionCommit
Airavata session servercyber-shuttle/cs-plane0.4.20621dbe, 2026-09-30
Airavata batch serverapache/airavatamaster, unreleased8177057, 2026-09-29
CS Jupytercyber-shuttle/cs-jupyter0.1.1339050e, 2026-09-30
CS Bridgecyber-shuttle/CS-Bridge0.2.3e5543cd, 2026-09-30
Linkspancyber-shuttle/linkspan0.22.1b90dee7, 2026-09-30
Security component (Custos)apache/airavata-custosmaster, unreleasedc063f4a, 2026-09-29

Requirements​

ConsumerRequires
Airavata session serverLinkspan 0.22.0 or newer, for --tunnel-link-args and --tunnel-mode link
CS Bridge 0.2.3Linkspan 0.22.0 or newer; for the link transport, Airavata's session server at https://jupyterapi.cybershuttle.org/api/v1, fixed in src/plane.ts
CS JupyterAiravata session server 0.4.0 or newer

To see what is installed:

ComponentCommand
Session servercs version on the Airavata host
Linkspan~/.cybershuttle/bin/linkspan --version in the user's account on the login node
CS BridgeThe Extensions view of VS Code

Where login nodes reach GitHub, the session server installs the latest Linkspan at each session start; see Linkspan installation. Where Linkspan is placed by hand, replace it before upgrading the session server past a new minimum.

Contracts​

Upgrade the components on both sides of a changed contract together.

ContractBetweenDefined in
linkspan --version output, release archive name and memberAiravata, CS Bridge → LinkspanLinkspan compatibility
Linkspan flags and environmentAiravata, CS Bridge → LinkspanLinkspan configuration
The link protocolAiravata ↔ LinkspanThe link
Linkspan /api/v1 response shapesAiravata, CS Bridge → LinkspanLinkspan HTTP API
Workflow documentAiravata → LinkspanWorkflows
Airavata /api/v1 session routes, bodies and error codesCS Jupyter, CS Bridge → AiravataHTTP API
--allowed-origin and cybershuttlePlaneApiUrlCS Jupyter deployment ↔ Airavata deploymentHosting the Jupyter site

The session API is pinned by TestCanonicalRouteManifest in the session server's main_test.go, by subsystems/session/testdata/session-contract.json, and by CS Jupyter's generated types. CS Jupyter generates those TypeScript types with tygo from the session server's wire.go files at the commit pinned in tools/go.mod (8f67df7, before 0.4.0; no wire.go file has changed since).

Versioning​

ComponentSchemePublished
Airavata session servervX.Y.Z tags; Version in main.goNo binaries; build from source
CS Jupyter0.1.1 in both package.json and pyproject.tomlNothing; deployments rebuild dist/
CS BridgeX.Y.Z tags, without v; release notes name a newer Linkspan it requiresVisual Studio Marketplace
LinkspanvX.Y.Z tags, SemVer; linkspan --version omits the vGitHub releases, built with GoReleaser

These four keep a changelog in the Keep a Changelog format.