Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
NEW Add ability for the upgrader to self-update (#153)
* NEW Auto compute version number on build. * Suppress warning about dependency casing. * Add a self-update command. * Update the "releasing doc" to reflect that its automated now * Update travis config to produce an md5 hash of the phar and keep older version. * Correct doc. * Implement feedback from peer review.
- Loading branch information
1 parent
c4bc609
commit 6e438ca
Showing
10 changed files
with
415 additions
and
28 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
UPGRADER_VERSION=1.3.0 |
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,2 +1,4 @@ | ||
/vendor/ | ||
upgrade-code.phar | ||
.env | ||
.idea |
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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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,12 +1,15 @@ | ||
# Releasing a new verison of the upgrader | ||
# Releasing a new version of the upgrader | ||
|
||
This document is aimed for internal consumption. To release a new version of the upgrader follow these steps. | ||
This document is aimed for internal consumption. | ||
|
||
Upgrader releases are now automated with a travis build. When the tag gets built on travis, the build script will automatically run and build a PHAR executable. The PHAR executable will be attached back to the release in GitHub and publish to this repo's github pages. | ||
|
||
|
||
To release a new version of the upgrader follow these steps: | ||
|
||
1. On your local system, clone the upgrader codebase. You need to work of the `master` branch from this point. | ||
2. Increment the version number in `src/upgrade-code`, commit your changes and push them back up to GitHub. | ||
3. Call `php build.php` on the command line. This will build the upgrader as a PHAR file. | ||
4. Move `upgrade-code.phar` to a temporary folder. | ||
5. Switch to the `gh-pages` branch. e.g.: `git checkout gh-pages` | ||
6. Overwrite the existing `upgrade-code.phar` with the one you built in step 3. | ||
7. Commit your changes to the `gh-pages` branch and push them up to GitHub. | ||
8. Create a new release on GitHub and attach `upgrade-code.phar` to it. | ||
2. Increment the version number in `src/upgrade-code`, commit your changes and push them back up to GitHub. This will only be used for people installing the upgrader with Composer. The PHAR executable gets its version number from an environment file built into it. | ||
3. In GitHub create a new release. You should provide detail about what has changed since the last release, referencing PRs ideally. | ||
4. The release won't have a PHAR executable attached to it initially. You'll have to do wait for travis to complete its build. If that build fails for whatever reason, you can delete the release and unset the tag. Fix the issue and re-release the tag. | ||
|
||
Note that we don't do patch releases for older minor releases. People are expected to always use the latest version. |
Oops, something went wrong.