Update Releasing notes
This commit is contained in:
parent
7dfc1ba32b
commit
e6c12b9cf7
11
Releasing.md
11
Releasing.md
@ -12,12 +12,9 @@
|
|||||||
```
|
```
|
||||||
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>`.
|
notes for v<new version number>`.
|
||||||
4. Run `pulp version` in the project root. This will check the project for any
|
4. Follow the instructions on
|
||||||
issues and create a new version tag and empty checkpoint commit.
|
https://discourse.purescript.org/t/how-i-publish-a-purescript-package/2482.
|
||||||
5. Run `pulp publish` in the project root. This will publish the commits & tag
|
5. If you are pushing a non-patch release, create and push a branch named with
|
||||||
to github, will publish the package to bower, and will push documentation to
|
|
||||||
pursuit.
|
|
||||||
6. If you are pushing a non-patch release, create and push a branch named with
|
|
||||||
the version series, i.e. `v0.1.x`.
|
the version series, i.e. `v0.1.x`.
|
||||||
7. [Create the release on
|
6. [Create the release on
|
||||||
github](https://github.com/cprussin/purescript-httpure/releases/new).
|
github](https://github.com/cprussin/purescript-httpure/releases/new).
|
||||||
|
Loading…
Reference in New Issue
Block a user