Skip to content

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

Open
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/4652-clarify-bump-guidance
Open

docs(#4652): clarify changeset bump guidance for type changes#4653
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/4652-clarify-bump-guidance

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

Refine the major/minor bump criteria in .fullsend/AGENTS.md to distinguish between runtime-breaking and TypeScript-only-breaking API changes. The previous guidance listed changed interfaces as major, which caused the review agent to repeatedly flag minor bumps on additive type changes that are TypeScript compile-time breaking but runtime/JSON-compatible.

The updated guidance specifies major for changes that affect runtime behavior or remove capabilities (removed exports, narrowed types, removed fields), and minor as acceptable for additive or widening type changes on public interfaces that maintain runtime/JSON compatibility. This aligns with established repo practice (e.g., PR #4582) and eliminates the ambiguity that caused repeated false-positive missing-version-bump findings.


Closes #4652

Post-script verification

  • Branch is not main/master (agent/4652-clarify-bump-guidance)
  • Secret scan passed (gitleaks — c380e6b99bfdc49fd073ce3b27744ce06fbf473d..HEAD)
  • Pre-commit hooks passed (authoritative run on runner)
  • Tests ran inside sandbox

Refine the major/minor bump criteria in .fullsend/AGENTS.md to
distinguish between runtime-breaking and TypeScript-only-breaking
API changes. The previous guidance listed changed interfaces as
major, which caused the review agent to repeatedly flag minor bumps
on additive type changes that are TypeScript compile-time breaking
but runtime/JSON-compatible.

The updated guidance specifies major for changes that affect
runtime behavior or remove capabilities (removed exports, narrowed
types, removed fields), and minor as acceptable for additive or
widening type changes on public interfaces that maintain
runtime/JSON compatibility. This aligns with established repo
practice (e.g., PR #4582) and eliminates the ambiguity that
caused repeated false-positive missing-version-bump findings.

Closes #4652
@fullsend-ai-coder
fullsend-ai-coder Bot requested review from a team as code owners September 9, 2026 09:52
@fullsend-ai-coder fullsend-ai-coder Bot added the ready-for-review Agent PR ready for human review label Sep 9, 2026
@codecov

codecov Bot commented Sep 9, 2026

Copy link
Copy Markdown

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

@sonarqubecloud

sonarqubecloud Bot commented Sep 9, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-review Agent PR ready for human review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify changeset bump guidance for TypeScript-level breaking type changes

0 participants