Public SDKs and examples for the Anyshift Graph API.
The first public SDK release is TypeScript. Python and Go SDKs are planned next, so this repository is organized as a multi-language SDK home from day one.
| Language | Package | Status |
|---|---|---|
| TypeScript | @anyshift/graph-sdk |
First public release |
| Python | anyshift-graph |
Planned |
| Go | github.com/anyshift-io/anyshift-graph-sdk/go |
Planned |
openapi/ Pinned Graph API contract snapshots used by SDK releases
typescript/ TypeScript SDK package and examples
python/ Future Python SDK
go/ Future Go SDK
This repository owns package-level documentation: installation, examples, local SDK development, and release notes.
Product documentation, onboarding guides, and use-case recipes are published on the Anyshift documentation site.
For the detailed list of what the Graph API and SDK can do, see CAPABILITIES.md.
For every deterministic query target, filter, accepted value, alias, and query form, see the Graph Query Language reference.
SDKs depend on the public Graph API contract. TypeScript types should be generated from, or
pinned to, the OpenAPI contract in openapi/.
The release prepared by this branch is @anyshift/graph-sdk@0.5.13.
After merging a versioned SDK change, create the matching typescript-vX.Y.Z
GitHub release tag at the merge commit. Then dispatch the Release TypeScript
SDK workflow with that tag. The workflow verifies the tag/package version,
runs the complete TypeScript SDK checks, and publishes the public package from
the immutable tag through the protected npm environment.
Release checklist:
- TypeScript package builds with
npm run build. - TypeScript tests pass with
npm test. - Generated OpenAPI and query-language artifacts pass
npm run check:generated. - A packed package installs, typechecks, imports, and runs in a clean consumer via
npm run test:consumer. - Package contents are verified with
npm pack --dry-run. - Developer documentation is published in the Anyshift documentation site.
Use graph.eventContributors({ firingId: "exact-firing-dedupeId", limit: 50 }) to inspect stored Sentry alert-evaluation members. Pass cursor from the returned page to continue. IDs preserve case; missing IDs may be late, expired or unobserved. Evaluation coverage remains unknown and contributor membership is not proof of infrastructure root cause.