Skip to content

Commit

Permalink
Merge pull request #434 from garden-io/release-0.8.1-rc1
Browse files Browse the repository at this point in the history
Release v0.8.1-rc1
  • Loading branch information
edvald authored Dec 10, 2018
2 parents 5f56859 + 24c884e commit 35be185
Show file tree
Hide file tree
Showing 3 changed files with 120 additions and 117 deletions.
25 changes: 14 additions & 11 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -79,14 +79,17 @@ To make a new release, set your current working directory to garden root and fol
1. Checkout out to a new release branch, e.g. `git checkout -b release-0.8.0-rc2`.
2. Update the `version` field in `./garden-service/package.json` to the new release name.
3. Run `cd garden-service && npm install && cd ..` to update `package-lock.json`.
4. Run `./garden-service/scripts/build-pkg.sh` to build the executable with Pkg.
5. Go to our Github [Releases tab](https://github.com/garden-io/garden/releases) and click the **Draft a new release** button.
6. Fill in the **Tag version** and **Release title** fields with the new release version. E.g. `v0.8.0-rc2`.
7. Upload the zip files generated by Pkg for Windows and Linux. They're located at `./garden-service/dist/`.
8. Click the **Publish release** button.
9. Pull the tag just created with `get fetch --tags` (this is needed for generating the changelog).
10. Update the changelog with `git-chglog -o=CHANGELOG.md v0.1.0..<tag-name>`, e.g. `git-chglog -o=CHANGELOG.md v0.1.0..v0.8.0-rc2`.
10. Update the `./support/install.ps1` script so that it uses the new release. You'll need to update the `$url` and `$zipPath` variables, cf. [this diff](https://github.com/garden-io/garden/pull/356/files#diff-d576dca984d0197834587b96d68867f8).
11. Commit your changes, push the branch and make a pull request.
12. Publish the NPM package with `cd garden-service && npm publish && cd ..`
13. Publish the Homebrew package with `gulp update-brew`.
4. Update the changelog with `git-chglog -o=CHANGELOG.md v0.1.0..<tag-name>`,
e.g. `git-chglog -o=CHANGELOG.md v0.1.0..v0.8.0-rc2`.
5. Make a version bump commit (e.g. `chore(release): bump version to 0.8.0-rc2`)
6. Create a new tag for the version: `git tag -a v0.8.0-rc2 -m 'chore(release): release v0.8.0-rc2'`
7. Push the new tag: `git push origin v0.8.0-rc2 --no-verify`. This will trigger the dist build process in CircleCI.
8. Open the [Garden project on CircleCI](https://circleci.com/gh/garden-io/garden).
Browse to the job marked `release-service-pkg`, open the _Artifacts_ tab and download the listed artifacts.
9. Go to our Github [Releases tab](https://github.com/garden-io/garden/releases) and click the **Draft a new release** button.
10. Fill in the **Tag version** and **Release title** fields with the new release version (same as you used for the tag).
11. Upload the downloaded artifacts.
12. Write release notes (not necessary for RCs). The notes should _at least_ contain the changelog.
13. Click the **Publish release** button.
14. Push the branch and make a pull request.
15. If you're making an RC, you're done! Otherwise, you need to update Homebrew package: `gulp update-brew`
Loading

0 comments on commit 35be185

Please sign in to comment.