@zalom/plastic 1.0.0-beta.30 → 1.0.0-beta.31
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.
- package/package.json +1 -1
- package/skills/releasing/SKILL.md +13 -1
package/package.json
CHANGED
|
@@ -104,8 +104,20 @@ Determine which files to update from project.yml:
|
|
|
104
104
|
|
|
105
105
|
Update the version string in each file, then commit:
|
|
106
106
|
|
|
107
|
+
**Cut the CHANGELOG entry.** Before committing, edit `CHANGELOG.md` at the repo root so
|
|
108
|
+
the changelog change rides this same version-bump commit and reaches the tag. Write one
|
|
109
|
+
line in the existing shape:
|
|
110
|
+
|
|
111
|
+
`` `<version>` - shipped <date>; collected <intent-id> (<one-line summary>) ``
|
|
112
|
+
|
|
113
|
+
Prepend it as the first bullet under `## Released` (newest-first). If this version was
|
|
114
|
+
sitting under `## Unreleased`, move it out of that section and into `## Released`. Keep
|
|
115
|
+
the line intent-centric narrative (which intents the cut collected and why), NOT commit
|
|
116
|
+
detail: step 5's tag-message changelog and step 7's `gh release create --generate-notes`
|
|
117
|
+
already own the commit-level detail, so do not duplicate it here.
|
|
118
|
+
|
|
107
119
|
```bash
|
|
108
|
-
git add <version-files>
|
|
120
|
+
git add <version-files> CHANGELOG.md
|
|
109
121
|
git commit -m "chore: bump version to X.Y.Z - [one-line summary]"
|
|
110
122
|
```
|
|
111
123
|
|