-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Connor Prussin
committed
Oct 26, 2017
1 parent
d12830b
commit f28a9bf
Showing
3 changed files
with
15 additions
and
12 deletions.
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
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 |
---|---|---|
@@ -1,21 +1,22 @@ | ||
# HTTPure Releasing Guide | ||
# HTTPure Releasing Guide | ||
|
||
1. Check out the release series branch (or `master` if you are releasing the | ||
next major/minor version). Ensure all relevant commits and PRs have been | ||
merged. | ||
2. Update [History.md](History.md) by changing "unreleased" to the new | ||
2. Update [History.md](./History.md) by changing "unreleased" to the new | ||
version/date. Example diff: | ||
```diff | ||
-unreleased | ||
-========== | ||
+1.0.0 / 2017-07-10 | ||
+================== | ||
``` | ||
3. Commit your update to [History.md](History.md). Use the message `Release | ||
3. Commit your update to [History.md](./History.md). Use the message `Release | ||
notes for v<new version number>`. | ||
4. Run `pulp version` in the project root. This will check the project for any | ||
issues and create a new version tag and empty checkpoint commit. | ||
5. Push the release notes and version commit and version tag. | ||
6. If you are pushing a non-patch release, create and push a branch named with | ||
the version series, i.e. `v0.1.x`. | ||
7. [Create the release on github](https://github.com/cprussin/purescript-httpure/releases/new). | ||
7. [Create the release on | ||
github](https://github.com/cprussin/purescript-httpure/releases/new). |