Skip to content

Commit bdd109d

Browse files
authored
Merge pull request #51 from mi-examples/pp-2787-updates
PP-2787 fix(deps): Security Updates, Dependency Upgrades & Cursor Rules
2 parents 8ca7135 + b994e40 commit bdd109d

11 files changed

Lines changed: 765 additions & 877 deletions

File tree

.cursor/rules/create-pr.mdc

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
description: Create PR message for merging current branch into target branch (default: origin/develop)
3+
alwaysApply: false
4+
---
5+
6+
# Create PR Workflow
7+
8+
When the user asks to **Create PR** (or "create pull request", "generate PR message"):
9+
10+
## Steps
11+
12+
1. **Determine target branch** – Default is `origin/develop`. If the user specifies a different branch in their message, use that instead.
13+
14+
2. **Get current branch** – Run `git branch --show-current` to get the source branch.
15+
16+
3. **Get commit range** – Compare current branch against target. Run:
17+
```bash
18+
git log origin/develop..HEAD --oneline
19+
```
20+
(Replace `origin/develop` with the target branch if changed.)
21+
22+
4. **Generate PR message** – Create a markdown PR message following the project's PR format (see `pr-message-format.mdc`). Include:
23+
- Title
24+
- Summary of changes
25+
- Key features/improvements
26+
- Included commits
27+
- Merge request line: `source-branch` → `target-branch`
28+
29+
5. **Save to file** – Write the PR message to an MD file, e.g. `PR_MESSAGE.md` or `pr-message.md` in the project root.
30+
31+
## Example output file
32+
33+
```markdown
34+
## 🚀 feat: Add minimatch override for security
35+
36+
### 📋 Summary
37+
...
38+
39+
**Merge Request:** `feature/xyz` → `origin/develop`
40+
```

.cursor/rules/create-release.mdc

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
description: Create release tag from latest origin/main with version from package.json (without beta suffix)
3+
alwaysApply: false
4+
---
5+
6+
# Create Release Workflow
7+
8+
When the user asks to **Create release** (or "create tag", "release tag"):
9+
10+
## Steps
11+
12+
1. **Read version from package.json** – Get the `version` field (e.g. `0.5.5-beta.2`).
13+
14+
2. **Strip beta suffix** – Remove `-beta.*`, `-alpha.*`, `-rc.*` etc. Examples:
15+
- `0.5.5-beta.2` → `0.5.5`
16+
- `1.0.0-rc.1` → `1.0.0`
17+
- `2.3.4` → `2.3.4` (unchanged)
18+
19+
3. **Tag name** – Use `v` + stripped version: `v0.5.5`.
20+
21+
4. **Create tag on latest origin/main** – Run:
22+
```bash
23+
git fetch origin main
24+
git tag v<version> origin/main -m "Release v<version>"
25+
```
26+
Example: `git tag v0.5.5 origin/main -m "Release v0.5.5"`
27+
28+
5. **Push tag** (if user wants to publish):
29+
```bash
30+
git push origin v<version>
31+
```
32+
33+
## Notes
34+
35+
- Tag is created from `origin/main`, not from the current branch.
36+
- Do not push the tag unless the user explicitly requests it.
37+
- Confirm the version and tag name with the user before creating/pushing.

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@ template-*/package-lock.json
1313

1414
# Pack files
1515
*-create-pp-dev-*.*.*.tgz
16+
*-create-pp-dev-latest.tgz
1617

1718
# Environment
1819
.env

0 commit comments

Comments
 (0)