You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .cursor/rules/rules.main.mdc
+8-6Lines changed: 8 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -63,12 +63,14 @@ alwaysApply: true
63
63
---
64
64
65
65
## Changelog rules:
66
-
- add an entry under `## [Unreleased]` in `CHANGELOG.md` for `feat:` and `fix:` PRs; skip for `chore:`, `ci:`, `refactor:`, `test:`, `docs:` unless the change is user-facing
67
-
- use standard Keep a Changelog categories: `### Added`, `### Changed`, `### Deprecated`, `### Removed`, `### Fixed`, `### Security`
68
-
- append `#PR_NUMBER` at the end of each changelog entry when the PR number is known
69
-
- place new entries at the top of their category section (newest first)
70
-
- never modify released version sections — only edit `## [Unreleased]`
71
-
- create category headings on demand (don't add empty stubs)
66
+
- never edit `CHANGELOG.md` in normal feature/fix PRs; release automation collects changelog fragments into it
67
+
- add exactly one changelog fragment for user-facing `feat:` and `fix:` PRs; skip for `chore:`, `ci:`, `refactor:`, `test:`, `docs:` unless the change is user-facing
68
+
- put normal release fragments in `changelog.d/next/` and hotfix fragments in `changelog.d/hotfix/`
69
+
- name fragments `<issue-or-pr>.<category>.md`, where category is one of `added`, `changed`, `deprecated`, `removed`, `fixed`, or `security`
70
+
- write the fragment as one polished user-facing sentence without a leading bullet and without a PR number
71
+
- never add multiple changelog fragments for the same PR — summarize all changes in one concise fragment
72
+
- release commits consume fragments with `scripts/collect-changelog.sh --target next|hotfix`, update `CHANGELOG.md`, and delete consumed fragment files
- ALWAYS add exactly ONE entry per PR under `## [Unreleased]` in `CHANGELOG.md` for `feat:` and `fix:` PRs; skip for `chore:`, `ci:`, `refactor:`, `test:`, `docs:` unless the change is user-facing
244
-
- NEVER add multiple changelog lines for the same PR — summarize all changes in a single concise entry
245
-
- USE standard Keep a Changelog categories: `### Added`, `### Changed`, `### Deprecated`, `### Removed`, `### Fixed`, `### Security`
246
-
- ALWAYS append `#PR_NUMBER` at the end of each changelog entry when the PR number is known
247
-
- ALWAYS place new entries at the top of their category section (newest first)
248
-
- NEVER modify released version sections — only edit `## [Unreleased]`
- NEVER edit `CHANGELOG.md` in normal feature/fix PRs; release automation collects changelog fragments into it
244
+
- ALWAYS add exactly ONE changelog fragment for user-facing `feat:` and `fix:` PRs; skip for `chore:`, `ci:`, `refactor:`, `test:`, `docs:` unless the change is user-facing
245
+
- PUT normal release fragments in `changelog.d/next/` and hotfix fragments in `changelog.d/hotfix/`
246
+
- NAME fragments `<issue-or-pr>.<category>.md`, where category is one of `added`, `changed`, `deprecated`, `removed`, `fixed`, or `security`
247
+
- WRITE the fragment as one polished user-facing sentence without a leading bullet and without a PR number
248
+
- NEVER add multiple changelog fragments for the same PR — summarize all changes in one concise fragment
249
+
- Release commits consume fragments with `scripts/collect-changelog.sh --target next|hotfix`, update `CHANGELOG.md`, and delete consumed fragment files
0 commit comments