kpt 0.39.1 brew (#1741)

Author: runewake2

Formula/kpt.rb

@@ -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
 

release/README.md

@@ -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)
@@ -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.