Skip to content
Agent Detective

Maintainer: releasing

Maintainer: releasing

Section titled “Maintainer: releasing”

Releases are automated with release-please — the same model as andezdev/tokenlite-mysql-mcp.

What happens automatically

Section titled “What happens automatically”

On every push to main, .github/workflows/release-please.yml:

  1. Opens or updates a Release PR with version bumps, changelogs, and manifest updates.
  2. When that PR is merged, creates a GitHub Release + git tag and publishes to npm:
    • agent-detective (CLI)
    • All @agent-detective/* packages (linked to the same version)

Maintainer steps

Section titled “Maintainer steps”
  1. Land changes on main using Conventional Commits (feat:, fix:, chore:, …).
    • Docs and landing only (docs/**, apps/docs/**, apps/landing/**, root README.md): use docs: or chore: — not fix: / feat: (those trigger npm). The commit hook and release-please exclude-paths enforce this.
    • Runtime / npm (src/, packages/, test/, etc.): use feat: / fix: as usual.
  2. Review the Release PR created by release-please.
  3. Merge the Release PR when CI is green and the changelog looks correct.
  4. Confirm the release-please workflow published to npm and created the GitHub Release.

Optional smoke after publish:

Terminal window
npm i -g agent-detective@X.Y.Z
agent-detective init
agent-detective doctor

Secrets and permissions

Section titled “Secrets and permissions”
ItemPurpose
GITHUB_TOKENRelease PR + GitHub Release (default)
npm Trusted Publishing (OIDC)pnpm publish -r uses GitHub OIDC (id-token: write in the workflow) — no long-lived NPM_TOKEN secret

Configure Trusted Publishers on npm for agent-detective and @agent-detective/* packages linked to this repository.

Configuration

Section titled “Configuration”

See also

Section titled “See also”