Operations and release

DeploySutra is a CLI, so "operations" means how to run it reliably and how the project itself is released. Runbooks here cover DeploySutra only, never your production targets.

Running in CI

Pin the version (npx -y deploysutra-ai@0.2.0), run offline, treat exit 2 as a blocking signal for human review, upload report/ as an artifact. The step needs no secrets and no network beyond fetching the package.

Local report API (optional)

export DEPLOYSUTRA_TOKEN="$(node -e "console.log(require('crypto').randomBytes(32).toString('hex'))")"
npx deploysutra-ai serve --report report/deploy-readiness.json --port 4318

Rotate the token by restarting with a new value. It serves one preloaded verified report; there is nothing to back up.

Incident handling for the tool itself

SituationAction
A rule gives a wrong resultOpen an issue with the smallest sanitized manifest; it becomes a corpus case
A report contains something sensitiveDelete it, rotate the exposed value, file a private advisory if the tool leaked it
A tampered report is suspecteddeploysutra verify; regenerate from the source files
Package compromise suspectedPin to a known digest, compare npm pack output with the repository tag

Release process

  1. npm test and npm run proof pass locally (no failures; skips explained).
  2. Update CHANGELOG.md, versions in package.json, .claude-plugin/plugin.json, CITATION.cff and packages/core/util.mjs (a test checks they match).
  3. git tag vX.Y.Z && git push --tags. The Release workflow runs tests, checks tag = version, and publishes to npm with provenance via trusted publishing (OIDC, no stored token). If trusted publishing is not configured the publish is done manually and the release notes say so.
  4. Create a GitHub release with notes copied from the changelog.
  5. Rebuild documents: npm run proof then node build.mjs in the documents folder.

Rollback of the tool

npm versions are immutable. To roll back, publish a fixed patch and deprecate the bad version (npm deprecate deploysutra-ai@x.y.z "reason"). Consumers pinning the previous version are unaffected.

Compatibility and support policy

Node.js 20, 22 and 24 are tested in CI on Ubuntu, Windows and macOS. Rule IDs and the report envelope are stable within a minor line; breaking report changes bump schemaVersion. Volunteer-maintained, no SLA.

Cost

Free to run: no hosted service, no paid dependency, no model call.