File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change @@ -20,16 +20,12 @@ Test the notifier by running the application locally.
2020Releasing
2121=========
2222
23- 1 . Commit all outstanding changes
24- 2 . Bump the version in ` src/Configuration.php ` .
25- 3 . Update the CHANGELOG.md, and README if appropriate.
26- 4 . Check out a new branch and commit your changes
27- 5 . Open a pull request for the release
28- 6 . Once merged, pull the latest changes and then tag the release:
29- ```
30- git tag v3.x.x
31- git push --tags
32- ```
33- 7. Build a new phar package by running `make package` and attach it to the GitHub release.
34- 8. Ensure `utility/bugsnag-prepend.php` works with the example php project and attach it to the Github release.
35- 9. Update the setup guides for PHP (and its frameworks) with any new content.
23+ 1 . Merge all outstanding PRs to go into the release.
24+ 1 . Create a new release branch from ` next ` , named in the format ` release/v1.x.x ` .
25+ 1 . Bump the version in ` src/Configuration.php ` .
26+ 1 . Update the CHANGELOG.md, and README if appropriate.
27+ 1 . Open a pull request into ` master ` and get it approved.
28+ 1 . Merge the pull request using a message of the form "Release v1.x.x".
29+ 1 . Pull the latest ` master ` branch locally.
30+ 1 . Build a new phar package by running ` make package ` .
31+ 1 . Create a new release on GitHub, attaching the phar.
You can’t perform that action at this time.
0 commit comments