Version compatibility and upgrades
Graftcode Alpha does not guarantee backward compatibility across major Gateway, protocol, SDK, and generated-package releases.
Inventory
Record:
- Gateway release and platform;
- Receiver artifact/version and runtime;
- generated package name/version in each Caller ecosystem;
- Hypertube runtime dependency version;
- enabled transports and configuration sources.
Upgrade procedure
- Read release notes and select an explicit Gateway release.
- Rebuild the Receiver with its supported runtime.
- Start the new Gateway in an isolated environment and verify discovery/publication.
- Generate fresh packages for every Caller ecosystem from that Gateway.
- Compile/type-check Callers and run representative in-memory and remote calls.
- Test errors, auth, tracing, retries, proxies, and stateful behavior used by the workload.
- Deploy a stateless canary; keep the previous set available for rollback.
- Drain old instances before removal and upgrade stateful workloads in a maintenance window.
Never infer compatibility from a matching public method signature alone; the Graftcode Engine and runtime protocols also participate.
There is no exhaustive compatibility table or automatic contract-drift rejection. Treat Vision and smoke tests from the deployed version as authoritative.