fixup! Feat: add a note to save changes before starting

Author: JPeer264

.cursor/rules/publishing_release.mdc

@@ -13,9 +13,10 @@ Use these guidelines when publishing a new Sentry JavaScript SDK release.
 The release process is outlined in [publishing-a-release.md](mdc:docs/publishing-a-release.md).
 
 1. Ensure you're on the `develop` branch with the latest changes:
-  - If you have unsaved changes, stash them with `git stash -u`.
-  - If you're on a different branch than `develop`, check out the develop branch using `git checkout develop`.
-  - Pull the latest updates from the remote repository by running `git pull origin develop`.
+   - If you have unsaved changes, stash them with `git stash -u`.
+   - If you're on a different branch than `develop`, check out the develop branch using `git checkout develop`.
+   - Pull the latest updates from the remote repository by running `git pull origin develop`.
+
 2. Make sure you are on the latest version of the `develop` branch. To confirm this, run `git pull origin develop` to get the latest changes from the repo.
 3. Run `yarn changelog` on the `develop` branch and copy the output. You can use `yarn changelog | pbcopy` to copy the output of `yarn changelog` into your clipboard.
 4. Decide on a version for the release based on [semver](mdc:https://semver.org). The version should be decided based on what is in included in the release. For example, if the release includes a new feature, we should increment the minor version. If it includes only bug fixes, we should increment the patch version. You can find the latest version in [CHANGELOG.md](mdc:CHANGELOG.md) at the very top.