2ec5e6826d
Previously this was done in Travis CI but there's really no good reason to manually push branches and let CI publish instead of just using the publish command directly.
1022 B
1022 B
HTTPure Releasing Guide
- 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. - Update History.md by changing "unreleased" to the new version/date. Example diff:
-unreleased
-==========
+1.0.0 / 2017-07-10
+==================
- Commit your update to History.md. Use the message
Release notes for v<new version number>
. - 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. - Run
pulp publish
in the project root. This will publish the commits & tag to github, will publish the package to bower, and will push documentation to pursuit. - If you are pushing a non-patch release, create and push a branch named with
the version series, i.e.
v0.1.x
. - Create the release on github.