fm-bench 0.6.0 → 0.6.1
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/docs/releasing.md +9 -2
- package/package.json +1 -1
package/docs/releasing.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Releasing
|
|
2
2
|
|
|
3
|
-
`fm-bench` uses semver tags (`v*.*.*`). Pushing a tag runs the **Release** workflow: test, lint, npm publish (with provenance), and GitHub release
|
|
3
|
+
`fm-bench` uses semver tags (`v*.*.*`). Pushing a tag runs the **Release** workflow: test, lint, npm publish (with provenance), and a GitHub release whose body is taken from the matching section in **`CHANGELOG.md`** (plus a compare link).
|
|
4
4
|
|
|
5
5
|
## Prerequisites
|
|
6
6
|
|
|
@@ -24,7 +24,14 @@ git push --follow-tags
|
|
|
24
24
|
|
|
25
25
|
## Re-run Release without republishing
|
|
26
26
|
|
|
27
|
-
If npm already has the version but GitHub release failed (or vice versa), use **Actions → Release → Run workflow** and enter the existing tag (for example `v0.5.3`). The workflow skips npm publish when that version is already on the registry
|
|
27
|
+
If npm already has the version but GitHub release failed (or vice versa), use **Actions → Release → Run workflow** and enter the existing tag (for example `v0.5.3`). The workflow skips npm publish when that version is already on the registry. If the GitHub release already exists, it **updates the release notes** from `CHANGELOG.md`.
|
|
28
|
+
|
|
29
|
+
Refresh notes locally without re-publishing:
|
|
30
|
+
|
|
31
|
+
```sh
|
|
32
|
+
node scripts/changelog-release-notes.mjs 0.6.0 > /tmp/notes.md
|
|
33
|
+
gh release edit v0.6.0 --notes-file /tmp/notes.md --repo devinoldenburg/fm-bench
|
|
34
|
+
```
|
|
28
35
|
|
|
29
36
|
## Dry run
|
|
30
37
|
|