Skip to content

chore: update RELEASING #191

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 1, 2025
Merged

chore: update RELEASING #191

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 15 additions & 14 deletions RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,23 +20,24 @@ separate `v8` tag. Should automatically get `v8`, `v8.0`, `v8.0.0` as well as

- [ ] Create/push a new patch tag for fixes/changes to `dagger-for-github`

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

NEXT_VERSION=vX.Y.Z # e.g. v1.2.3
NEXT_VERSION=vX.Y.Z # e.g. v1.2.3

# Sign the tag, using the date as the comment, e.g. 2024-07-22
git tag --sign -m $(date '+%Y-%m-%d') $NEXT_VERSION
git push origin $NEXT_VERSION #shouldn't need to force since new tag
```
# Sign the tag, using the date as the comment, e.g. 2024-07-22
git tag --sign -m $(date '+%Y-%m-%d') $NEXT_VERSION
git push origin $NEXT_VERSION #shouldn't need to force since new tag
```

- [ ] Create a new release from the patch tag (auto-fill release notes via the
GitHub UI or via the `gh` CLI)
- [ ] Submit PR to change the version mentioned in Dagger docs. See example [here](https://github.com/dagger/dagger/pull/9705/files)

```console
# --verify-tag will ensure the last tag creation step was done
gh release create --generate-notes --verify-tag <NEXT_PATCH_VERSION>
```
```console
# --verify-tag will ensure the last tag creation step was done
gh release create --generate-notes --verify-tag <NEXT_PATCH_VERSION>
```
Comment on lines +38 to +41
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These code blocks weren't indented correctly, and this one specifically was under the wrong item.


- [ ] Submit PR to change the version mentioned in Dagger docs. See example [here](https://github.com/dagger/dagger/pull/9705/files)