SentryKnown publishergetsentry/sentry-symfony/.cursor/rules/release-process.mdc

sentry-symfony / rules

Cursor rule737 starsChanged 14 months agoMITView on GitHub

To prepare a new release (e.g., version 4.14.0): After updating CHANGELOG.md:

We split this release-process.mdc into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Update master branch: Always ensure master is up-to-date first
line 11
Very specific:
Create release branch: Create a branch named prepare-X.Y.Z
line 17
Distinctive:
Find changes since last release: Check commits since the last version tag
line 22
Distinctive:
Update CHANGELOG.md: Add new version section with:
line 27
Distinctive:
Use simple commit message format
line 60
Distinctive:
Don't include additional descriptions or generated tags
line 61
Distinctive:
Check git status: git status
line 65
Distinctive:
Update from remote: git pull origin master
line 68

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

release-process.mdc

---
globs: CHANGELOG.md
alwaysApply: false
---
# Sentry Symfony SDK Release Process

## Release Process

To prepare a new release (e.g., version 4.14.0):

1. **Update master branch**: Always ensure master is up-to-date first
   ```bash
   git checkout master
   git pull origin master
   ```

2. **Create release branch**: Create a branch named `prepare-X.Y.Z`
   ```bash
   git checkout -b prepare-4.14.0
   ```

3. **Find changes since last release**: Check commits since the last version tag
   ```bash
   git log --oneline --no-merges 4.13.0..HEAD
   ```

4. **Update CHANGELOG.md**: Add new version section with:
   - Version number and announcement text
   - Features section for new features
   - Bug Fixes section for bug fixes
   - Misc section for documentation/readme updates
   - Use format: `- Description [(#PR)](mdc:https:/github.com/getsentry/sentry-symfony/pull/PR)`

## CHANGELOG.md Format

```markdown
## X.Y.Z

The Sentry SDK team is happy to announce the immediate availability of Sentry PHP SDK vX.Y.Z.

### Features

- New feature description [(#1234)](mdc:https:/github.com/getsentry/sentry-php/pull/1234)

### Bug Fixes

- Bug fix description [(#1235)](mdc:https:/github.com/getsentry/sentry-php/pull/1235)

### Misc

- Documentation/misc changes [(#1236)](mdc:https:/github.com/getsentry/sentry-php/pull/1236)
```

## Committing Changes

After updating CHANGELOG.md:

1. **Stage only the changelog**: `git add CHANGELOG.md`
2. **Create simple commit**: `git commit -m "Prepare X.Y.Z"`
   - Use simple commit message format
   - Don't include additional descriptions or generated tags

## Common Commands

- Check git status: `git status`
- View recent commits: `git log --oneline -10`
- Create branch: `git checkout -b branch-name`
- Update from remote: `git pull origin master`

Download now (ZIP)

Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free