Skip to main content

​
Current published releases

Last verified: July 12, 2026 Grantex packages are versioned independently. There is no single version number that represents every SDK, integration, service, and protocol artifact in this repository.
SurfaceCurrent releaseStatusRuntime requirement
TypeScript SDK@grantex/sdk@0.3.13Published to npmNode.js 18+; ESM
Python SDKgrantex==0.3.14Published to PyPIPython 3.9+
Go SDKgithub.com/mishrasanjeev/grantex-go@v0.1.10Published with known limitationsGo 1.26.1+
MCP Auth server@grantex/mcp-auth@2.0.2Published with known limitationsNode.js 18+; ESM
OpenAPI contract0.3.12Repository API-contract versionIndependent of SDK-only patches
The SDK patch versions differ because each language package is released on its own schedule. A newer package version does not imply a newer protocol or API contract version.

​
Known limitations in the current published artifacts

Go SDK v0.1.10: registration responses use agentId, but the published Agent.ID field expects JSON id, so it remains empty. Derive the agent ID from the returned did:grantex:<agentId> value for this release. Its LogAuditParams also lacks the API-required agentDid and principalId; submit audit records with the REST API or CLI.
MCP Auth 2.0.2: use a single process for evaluation only. Authorization codes are always process-local, consentUi does not create a page, onTokenIssued is not called, middleware/introspection do not check current revocation state, and the Grantex authorization code is not persisted for the token handler. See MCP Auth Server for the detailed endpoint and deployment matrix.

​
Reproducible installation

Pin exact versions in applications, examples, CI, and deployment manifests: 
npm install @grantex/sdk@0.3.13

python -m pip install grantex==0.3.14

go get github.com/mishrasanjeev/grantex-go@v0.1.10

npm install @grantex/mcp-auth@2.0.2 @grantex/sdk@0.3.13
Unpinned npm install, pip install, and go get commands resolve according to their registries and module proxy. Use the pinned commands above when the build must be repeatable.

​
How to read release information

​
Upgrade checklist

  1. Read the package-specific notes in the compatibility matrix and changelog.
  2. Confirm the required Node.js, Python, or Go toolchain version.
  3. Update the exact dependency version and regenerate the relevant lockfile.
  4. Run your authorization, token-verification, scope-enforcement, and revocation tests before deployment.
  5. For self-hosted environments, verify the API contract used by your service; an SDK-only patch does not upgrade the service automatically.
Do not infer publication from a repository manifest or marketing page alone. Confirm the exact artifact on its public registry before promoting a release.