Skip to content
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.

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

Try to fix release instructions, again #169

Merged
merged 1 commit into from
Jan 22, 2024
Merged
Changes from all commits
Commits
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
13 changes: 11 additions & 2 deletions docs/development.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,13 +25,22 @@ queries. After changing an sqlc `.sql` file, generate Go with:

## Releasing a new version

1. Prepare a PR with a `CHANGELOG.md` update describing the changes. Have it reviewed and merged.
2. Next, fetch the repo locally, bump dependency versions, tag each submodule, and push those tags:
1. Fetch changes to the repo and any new tags. Export `VERSION` by incrementing the last tag. Execute `update-submodule-versions` to add it the project's `go.mod` files:

```shell
git checkout master && git pull --rebase
export VERSION=v0.0.x
go run ./internal/cmd/update-submodule-versions/main.go
```

2. Prepare a PR with the changes, updating `CHANGELOG.md` with any necessary additions at the same time. Have it reviewed and merged.

Unfortunately, the build will fail because the version in the updated `go.mod` files isn't yet available.

3. Upon merge, pull down the changes, tag each module with the new version, and push the new tags:

```shell
git pull origin master
git tag cmd/river/$VERSION -m "release cmd/river/$VERSION"
git tag riverdriver/$VERSION -m "release riverdriver/$VERSION"
git tag riverdriver/riverpgxv5/$VERSION -m "release riverdriver/riverpgxv5/$VERSION"
Expand Down
Loading