Skip to content

Commit

Permalink
kpt 0.39.1 brew (#1741)
Browse files Browse the repository at this point in the history
  • Loading branch information
runewake2 committed Apr 13, 2021
1 parent 7c80674 commit b61a816
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions Formula/kpt.rb
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,8 @@
class Kpt < Formula
desc "Toolkit to manage,and apply Kubernetes Resource config data files"
homepage "https://googlecontainertools.github.io/kpt"
url "https://github.com/GoogleContainerTools/kpt/archive/v0.38.1.tar.gz"
sha256 "9313cc49a6957e294f560049d41765ee6ee8e56fe6cf62c2bbddb67777bac0df"
url "https://github.com/GoogleContainerTools/kpt/archive/v0.39.1.tar.gz"
sha256 "358640a523384a6fd110357721cf33373091793ea611dcaf3dabbde499be6940"

depends_on "go" => :build

Expand Down
4 changes: 2 additions & 2 deletions release/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ To cut a new kpt release perform the following:
- `git tag v0.MINOR.0`
- `git push upstream v0.MINOR.0`
- Update the Homebrew release
- `go run ./release/formula/main.go v0.MINOR.0`
- `go run ./release/formula/main.go v0.MINOR.0` (when running on a Mac you may need to `brew install coreutils` to get some of the required tools)
- `git add . && git commit -m "update homebrew to v0.MINOR.0"`
- create a PR for this change and merge it
- [example PR](https://github.com/GoogleContainerTools/kpt/pull/331/commits/baf33d8ed214f2c5e106ec6e963ad736e5ff4d98#diff-d69e3adb302ee3e84814136422cbf872)
Expand Down Expand Up @@ -119,4 +119,4 @@ From the kpt directory you can run the following to validate your release:
goreleaser release --skip-validate --skip-publish -f release/tag/goreleaser.yaml
```

The resulting release artifacts will be stored in the `./dist` directory.
The resulting release artifacts will be stored in the `./dist` directory.

0 comments on commit b61a816

Please sign in to comment.