Skip to content

docs(#4652): clarify changeset bump guidance for type changes #4653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fullsend-ai-coder wants to merge 1 commit into
base: main
Choose a base branch
from
+8 −2
Open

docs(#4652): clarify changeset bump guidance for type changes #4653

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 8 additions & 2 deletions .fullsend/AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,14 @@ type:
- `patch` for bug fixes, refactors, chores, and internal improvements
with no user-facing behavior change.
- `minor` for new features or capabilities visible to plugin consumers.
- `major` for breaking API changes (removed exports, changed interfaces,
dropped support).
- `major` for breaking API changes that affect runtime behavior or
remove existing capabilities (removed exports, narrowed types,
removed required fields, dropped support).
- `minor` is also acceptable for additive or widening type changes
on `@public` interfaces that maintain runtime/JSON compatibility
(new optional or required fields on response types, type widening
from `string` to `string | null`). These changes are TypeScript
compile-time breaking but runtime-compatible.

Match the bump level to the issue's stated intent (title prefix,
constraints), not the size of the diff.
Loading