Skip to content

Commit f3062e6

Browse files
committed
chore: update RELEASING
Signed-off-by: Justin Chadwell <me@jedevc.com>
1 parent c8eadbd commit f3062e6

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

RELEASING.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,12 +22,14 @@ separate `v8` tag. Should automatically get `v8`, `v8.0`, `v8.0.0` as well as
2222

2323
```console
2424
# Find the latest released patch https://github.com/dagger/dagger-for-github/releases
25-
# or via the `gh` CLI. Use that to figure out the NEXT_PATCH_VERSION.
25+
# or via the `gh` CLI. Use that to figure out the NEXT_VERSION.
2626
gh release view --repo dagger/dagger-for-github --json tagName,publishedAt
2727

28+
NEXT_VERSION=vX.Y.Z # e.g. v1.2.3
29+
2830
# Sign the tag, using the date as the comment, e.g. 2024-07-22
29-
git tag --sign -m $(date '+%Y-%m-%d') <NEXT_PATCH_VERSION>
30-
git push origin <NEXT_PATCH_VERSION> #shouldn't need to force since new tag
31+
git tag --sign -m $(date '+%Y-%m-%d') $NEXT_VERSION
32+
git push origin $NEXT_VERSION #shouldn't need to force since new tag
3133
```
3234

3335
- [ ] Create a new release from the patch tag (auto-fill release notes via the

0 commit comments

Comments
 (0)