-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #15 from tweag/release-0.2.0
Release 0.2.0
- Loading branch information
Showing
2 changed files
with
33 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
# Maintenance instructions | ||
|
||
## Cutting a new release | ||
|
||
- Create a dedicated branch: `release-<version>` (e.g. `release-0.2.0`) | ||
- Check the changes since the last release by | ||
[comparing the heads](https://github.com/tweag/rules_sh/compare/v0.2.0...HEAD), | ||
add anything relevant to `CHANGELOG.md`, | ||
and update the version heading and unreleased heading in `CHANGELOG.md`. | ||
* Open a PR for the new release, like | ||
[#10](https://github.com/tweag/rules_sh/pull/14) | ||
* When merged, create a tag of the form `v0.2.0` on the merge commit and push it: | ||
`git push origin v0.2.0` | ||
* Create the release on GitHub, selecting the tag created above. | ||
* Add the relevant changelog section to the release notes. | ||
* Obtain the sha256 for the release archive, by downloading the blob, | ||
and calling `sha256sum` on it. | ||
* Update the release notes with a workspace setup section for the new version, | ||
such as [this example](https://github.com/tweag/rules_sh/releases/tag/v0.2.0) |