-
Notifications
You must be signed in to change notification settings - Fork 168
Home
Releasing promscale
consists of the following steps:
- Update helm-chart/Chart.yml
- Update Promscale, PromMigrator, and supported
promscale_extension
versions inpkg/version/version.go
- Update
prom-migrator
andjaeger-query-proxy
version inbuild/.goreleaser.yml
(2 places each) - Run
./scripts/generate-deploy-script.sh
- Commit:
git commit -a -m "Prepare for the 0.1.0-alpha.4 release"
- PR & Merge
- git pull the master branch with PR merged && triple check that you have the right commit checked out.
- tag:
git tag -a 0.1.0-alpha.1 -m "Release 0.1.0-alpha.1" && git push origin 0.1.0-alpha.1
Note: Currently only @cevian can upload the charts to the s3 bucket below. Note 2: has to be done after go-releaser because it requires the docker images to be published
- Run
helm package helm-chart/
- Copy helm package into charts dir
- in charts dir run
/usr/local/bin/aws --profile <profile> s3 sync s3://charts.timescale.com .
helm repo index .
/usr/local/bin/aws --profile <profile> s3 sync --acl public-read . s3://charts.timescale.com
The goreleaser
GitHub Action will automatically create a new release with the generated binaries, docker images, and a changelog attached.
The following sections describe the different aspects of the release which should be highlighted.
Here are a couple of good examples of release notes which can be used for comparison:
Describe the major features of this release. Point to announcements or blog posts for reference.
It's nice to shout out to community members who've contributed some changes. Use the following to find all authors (and then figure out who are internal and external on your own):
git shortlog --summary --numbered --email <PREV_RELEASE>..<CURRENT_RELEASE>
Highlight functionality which has been deprecated in this release, and give and indication of when users can expect that the deprecated functionality will be removed.
Highlight functionality which has been removed in this release, and point out the alternatives (if present).
Provide any notes on special steps that users must take during the upgrade, e.g. configuration changes which must (or can) be made.
This will be automatically populated by goreleaser
. Remove all bors merge commits and dependabot version bump commits.
This will be automatically populated by goreleaser
.
- Update Version and PrevReleaseVersion in pkg/version/version.go to next devel version
- Commit:
git commit -a -m "Prepare for the next development cycle"
- PR & Merge
- Update chart/Chart.yaml: change
version
,app-version
anddependencies.timescale-prometheus.version
- Update chart/values.yml: change
promscale.image
to the appropriate tag. - Update version.go
- Update version in install-cli.sh
- Run
helm dependency update chart/
- Run
bash generate-deploy-script.sh
- Run
cd cli && go mod tidy && cd ..
- Commit:
git commit -a -m "Release 0.1.0-alpha.4"
- PR, test locally, merge
- git tag -a 0.1.0-alpha.1 -m "Release 0.1.0-alpha.1" && git push origin 0.1.0-alpha.1
- make sure goreleaser action runs (manual run:
cd cli && GITHUB_TOKEN=??? goreleaser && cd ..
) - run
helm package chart
- Copy helm package into charts dir
- in charts dir run
/usr/local/bin/aws --profile <profile> s3 sync s3://charts.timescale.com .
helm repo index .
/usr/local/bin/aws --profile <profile> s3 sync --acl public-read . s3://charts.timescale.com