@silverassist/agents-toolkit 2.3.0 → 2.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,74 +0,0 @@
1
- ---
2
- description: Prepare a new release for a Silver Assist WordPress plugin (version bump, changelog, tag, PR)
3
- agent: agent
4
- tools:
5
- - run_in_terminal
6
- - read_file
7
- - replace_string_in_file
8
- - create_file
9
- ---
10
-
11
- # Prepare Release
12
-
13
- Prepare a new version release for the current Silver Assist plugin.
14
-
15
- ## Inputs
16
-
17
- Ask the user:
18
- 1. **Version type** — Is this a `patch`, `minor`, or `major` release? (default: patch)
19
- 2. **Changelog entry** — What changed? (or offer to generate from recent commits)
20
-
21
- ## Steps
22
-
23
- 1. **Detect plugin** — Find the plugin root, main plugin file, and current version.
24
-
25
- 2. **Determine new version** — Based on the version type, calculate the next semantic version.
26
-
27
- 3. **Run quality checks** — Execute `./scripts/run-quality-checks.sh --skip-wp-setup phpcs phpstan` to verify the code is clean before release. Do NOT proceed if checks fail.
28
-
29
- 4. **Update version** — Run the version update script:
30
- ```bash
31
- ./scripts/update-version.sh X.Y.Z
32
- ```
33
- Or if the plugin uses the simple variant:
34
- ```bash
35
- ./scripts/update-version-simple.sh X.Y.Z
36
- ```
37
- This updates the version in the main plugin file, `readme.txt` (if present), and `composer.json`.
38
-
39
- 5. **Update CHANGELOG.md** — Add a new entry at the top following this format:
40
- ```markdown
41
- ## [X.Y.Z] - YYYY-MM-DD
42
-
43
- ### Added/Changed/Fixed
44
- - Description of change
45
- ```
46
-
47
- 6. **Create release branch and commit** — Following the branch naming convention:
48
- ```bash
49
- git checkout -b release/vX.Y.Z
50
- git add -A
51
- git commit -m "chore: bump version to X.Y.Z"
52
- ```
53
-
54
- 7. **Push and create PR** — Push the branch and create a PR:
55
- ```bash
56
- git push origin release/vX.Y.Z
57
- gh pr create --title "Release vX.Y.Z" --body "## Changes\n\n- changelog entry" | cat
58
- ```
59
-
60
- 8. **Post-merge instructions** — Remind the user:
61
- - After merging the PR, create the tag from the main/master branch:
62
- ```bash
63
- git checkout main && git pull
64
- git tag vX.Y.Z
65
- git push origin vX.Y.Z
66
- ```
67
- - The GitHub Actions release workflow will automatically build the ZIP and create the GitHub Release.
68
-
69
- ## Important
70
-
71
- - **NEVER reuse an existing tag** — tags are immutable. If a tag exists, bump to the next version.
72
- - The release-management skill has full documentation — use it for troubleshooting.
73
- - Some plugins use `master` instead of `main` (e.g., silver-assist-post-revalidate).
74
- - Always verify the default branch with `git branch --show-current` or `gh repo view --json defaultBranchRef | cat`.