* docs: add changeset guidelines to contributing docs Contributors and agents need to know when and how to add changesets. Without one, changes to published packages won't trigger a release. - CONTRIBUTING.md: full Changesets section with when/when-not, how to add, writing descriptions, examples for patch/minor/major - AGENTS.md: concise changeset subsection using --empty for non-interactive use, added as step in PR flow - PR template: changeset checkbox in checklist * docs: note that multiple changes need separate changesets
1.5 KiB
1.5 KiB
What does this PR do?
Closes #
Type of change
- Bug fix
- Feature (requires approved Discussion)
- Refactor (no behavior change)
- Documentation
- Performance improvement
- Tests
- Chore (dependencies, CI, tooling)
Checklist
- I have read CONTRIBUTING.md
pnpm typecheckpassespnpm --silent lint:json | jq '.diagnostics | length'returns 0pnpm testpasses (or targeted tests for my change)pnpm formathas been run- I have added/updated tests for my changes (if applicable)
- I have added a changeset (if this PR changes a published package)
- New features link to an approved Discussion: https://github.com/emdash-cms/emdash/discussions/...
AI-generated code disclosure
- This PR includes AI-generated code