Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .agents/skills/add-api-resource/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -82,4 +82,4 @@ node dist/index.js [v2] <resource> <verb> --help

Add or update the row in the Resources table in `README.md`, with v1 rows before v2 rows.

Follow the repository's PR template and mention the SDK bump and anything left out. Keep CLI version bumps and releases separate from resource changes.
Follow the repository's PR template and mention the SDK bump and anything left out. Do not bump the CLI version; add the release label and `## Release notes` described in `AGENTS.md`.
15 changes: 15 additions & 0 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,3 +26,18 @@
- Prettier runs as ESLint rule (no separate .prettierrc)
- No semicolons, single quotes, printWidth 100
- `no-console: error` — use proper output utilities instead

## Releases
Merging a PR to `main` with a `release:patch`, `release:minor` or `release:major` label
publishes a release, with notes from the PR's `## Release notes` section (see `RELEASE.md`).
Do not bump the version in feature PRs.

Pick one label by what CLI users get:

- `release:minor`: new commands, verbs or flags.
- `release:patch`: fixes to existing behavior, with no new public surface.
- `release:major`: removes or changes a command or flag incompatibly. `backward-compat.test.ts` blocks these, so agree on it with the team first.
- No label: changes CLI users don't get, such as tests, CI, docs or agent files.

Write `## Release notes` in English for CLI users: one bullet per change, naming what changed
(command, verb, flag or error), without internal details.
Loading