Bump the kpt homebrew version

[liamfallon]

This PR bumps the Homebrew kpt version to v1.0.0-beta.61

[netlify]

✅ Deploy Preview for kptdocs ready!

Name	Link
🔨 Latest commit	e68673a
🔍 Latest deploy log	https://app.netlify.com/projects/kptdocs/deploys/6995c8fda126910008609482
😎 Deploy Preview	https://deploy-preview-4399--kptdocs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull request overview

This PR updates the kpt Homebrew formula from version v1.0.0-beta.59 to v1.0.0-beta.61, enabling Homebrew users to install the latest beta release of kpt. The kpt project has a dedicated tool (release/formula/main.go) that automatically generates the formula by downloading the release tarball and computing its SHA256 hash, ensuring accuracy.

Changes:

• Updated the kpt version URL from v1.0.0-beta.59 to v1.0.0-beta.61
• Updated the corresponding SHA256 hash for the new release tarball

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dosubot]

Documentation Updates

3 document(s) were updated by changes in this PR:

_index

View Changes

@@ -20,11 +20,11 @@
 Let's revisit the Wordpress example:
 
 ```shell
-kpt pkg get https://github.com/kptdev/kpt.git/package-examples/wordpress@v1.0.0-beta.59
+kpt pkg get https://github.com/kptdev/kpt.git/package-examples/wordpress@v1.0.0-beta.61
 ```
 
 A package in a Git repo can be fetched by specifying a branch, tag, or commit SHA. In this case, we are specifying tag
-`v1.0.0-beta.59`.
+`v1.0.0-beta.61`.
 
 Refer to the [get command reference](../../reference/cli/pkg/get/) for usage.
 
@@ -42,14 +42,14 @@
   git:
     repo: https://github.com/kptdev/kpt
     directory: /package-examples/wordpress
-    ref: v1.0.0-beta.59
+    ref: v1.0.0-beta.61
   updateStrategy: resource-merge
 upstreamLock:
   type: git
   git:
     repo: https://github.com/kptdev/kpt
     directory: /package-examples/wordpress
-    ref: package-examples/wordpress/v1.0.0-beta.59
+    ref: package-examples/wordpress/v1.0.0-beta.61
     commit: b9ea0bca019dafa9f9f91fd428385597c708518c
 info:
   emails:
@@ -113,7 +113,7 @@
 For example, the following fetches the packages to a directory named `mywordpress`:
 
 ```shell
-kpt pkg get https://github.com/kptdev/kpt.git/package-examples/wordpress@v1.0.0-beta.59 mywordpress
+kpt pkg get https://github.com/kptdev/kpt.git/package-examples/wordpress@v1.0.0-beta.61 mywordpress
 ```
 
 The _name of a package_ is given by its directory name. Since the Kptfile is a KRM resource and follows the familiar
@@ -281,7 +281,7 @@
   git:
     repo: https://github.com/kptdev/kpt
     directory: /package-examples/wordpress
-    # Change this from v1.0.0-beta.59 to main
+    # Change this from v1.0.0-beta.61 to main
     ref: main
   updateStrategy: resource-merge
 ```

_index

View Changes

@@ -196,7 +196,7 @@
 To keep the example concrete, we use the WordPress package. You can fetch it locally with:
 
 ```shell
-$ kpt pkg get https://github.com/kptdev/kpt/package-examples/wordpress@v1.0.0-beta.59
+$ kpt pkg get https://github.com/kptdev/kpt/package-examples/wordpress@v1.0.0-beta.61
 ```
 
 ### Render-only build
@@ -224,7 +224,7 @@
         kpt fn render ${_PACKAGE_DIR}
 
 substitutions:
-  _KPT_VERSION: v1.0.0-beta.59
+  _KPT_VERSION: v1.0.0-beta.61
   _PACKAGE_DIR: wordpress
 ```
 
@@ -266,7 +266,7 @@
         KUBECONFIG=/workspace/kubeconfig kpt live apply ${_PACKAGE_DIR}
 
 substitutions:
-  _KPT_VERSION: v1.0.0-beta.59
+  _KPT_VERSION: v1.0.0-beta.61
   _PACKAGE_DIR: wordpress
 
 # Define where the secret comes from

_index

View Changes

@@ -61,7 +61,7 @@
 First, let's fetch the _kpt package_ from Git to your local filesystem:
 
 ```shell
-kpt pkg get https://github.com/kptdev/kpt/package-examples/nginx@v1.0.0-beta.59
+kpt pkg get https://github.com/kptdev/kpt/package-examples/nginx@v1.0.0-beta.61
 ```
 
 Subsequent commands are run from the `nginx` directory:

^{How did I do? Any feedback?}