Ageniti

Release Checklist

Use this checklist before publishing the package or cutting a public documentation update.

Package Checks

  • Confirm the package name and ownership on npm.
  • Confirm package.json metadata, keywords, license, and export map.
  • Confirm the package still targets Node.js 20 or newer and ESM-only usage.
  • Confirm the root export and subpath exports match the documented entry points.
  • Run npm test in the package.
  • Run npm pack --dry-run and inspect included files.
  • Review generated type declarations.

Contract Checks

  • Review README.md and docs landing copy for positioning consistency.
  • Confirm the docs still describe Ageniti as infrastructure for apps that agents can use, not an agent framework.
  • Confirm destructive and private action exposure rules are documented correctly.
  • Run the demo CLI and inspect actions, manifest, lint, and mcp output.
  • Run npx @ageniti/core doctor or the equivalent project check before shipping launchers.
  • Run your generated app CLI, for example task-app build, and inspect generated cli.mjs, mcp-stdio.mjs, and ageniti.mcp.json.
  • Confirm the local dev console still starts successfully.

Website Checks

  • Build the documentation website.
  • Confirm English and Chinese docs both have real titles and real localised content.
  • Click through internal documentation links.
  • Confirm new exports or runtime behaviours have corresponding docs updates.
## package
cd ../ageniti
npm test
npm pack --dry-run
npm publish --dry-run --access public --registry=https://registry.npmjs.org
node examples/demo.cli.js search-tasks --status open
node examples/demo.cli.js create-task --title "Follow up with design review"
node examples/demo.cli.js lint
node examples/demo.cli.js manifest
node examples/demo.cli.js mcp
node examples/demo.cli.js dev --port 4321
 
## website
cd ../website
npm run build

Publishing

npm publish --access public

Do not publish until package name, ownership, and registry target are confirmed.

If the local npm config points at a mirror, publish with:

npm publish --access public --registry=https://registry.npmjs.org
PreviousFAQ