Skip to content

Commit

Permalink
Merge pull request #118 from sapcc/goreleaser
Browse files Browse the repository at this point in the history
  • Loading branch information
SuperSandro2000 committed Oct 11, 2023
2 parents f1dac9f + 54e5ee2 commit d2c54e2
Show file tree
Hide file tree
Showing 4 changed files with 53 additions and 2 deletions.
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
# build artifacts
build/
dist/

# test artifacts
*.actual
4 changes: 2 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# Changelog

## v1.0.0 (2023-06-14)
## v1.0.1 - 2023-06-14

Changes:

* add automaxprocs
* update dependencies including golang

## v1.0.0 (2023-01-04)
## v1.0.0 - 2023-01-04

Initial release. We only used a rolling release up until this point.
5 changes: 5 additions & 0 deletions Makefile.maker.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -27,13 +27,18 @@ golang:
golangciLint:
createConfig: true

goReleaser:
createConfig: true

githubWorkflow:
ci:
enabled: true
coveralls: true
ignorePaths: ["**.md"] # all Markdown files
license:
enabled: true
release:
enabled: true
securityChecks:
enabled: true
spellCheck:
Expand Down
45 changes: 45 additions & 0 deletions RELEASE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
# Release Guide

We use [GoReleaser][goreleaser] and GitHub workflows for automating the release
process. Follow the instructions below for creating a new release.

1. Ensure local `master` branch is up to date with `origin/master`:

```sh
git fetch --tags && git pull --tags
```

2. Ensure all checks are passing:

```sh
make check
```

3. Update the [`CHANGELOG`](./CHANGELOG.md).
Make sure that the format is consistent especially the version heading.
We follow [semantic versioning][semver] for our releases.

You can check if the file format is correct by running [`release-info`][release-info] for the new version:

```sh
go install github.com/sapcc/go-bits/tools/release-info@latest
release-info CHANGELOG.md X.Y.Z
```

where `X.Y.Z` is the version that you are planning to release.

4. Commit the updated changelog with message: `Release <version>`
5. Create and push a new Git tag:

```sh
git tag vX.Y.Z
git push --tags
```

> [!IMPORTANT]
> Tags are prefixed with `v` and the GitHub release workflow is triggered for tags that match the `v[0-9]+.[0-9]+.[0-9]+` [gh-pattern].
[release-info]: https://github.com/sapcc/go-bits/tree/master/tools/release-info
[semver]: https://semver.org/spec/v2.0.0.html
[gh-pattern]: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#patterns-to-match-branches-and-tags
[goreleaser]: https://github.com/goreleaser/goreleaser

0 comments on commit d2c54e2

Please sign in to comment.