Prepare for v0.1.3 (#17)

Release fix for archive commands.

README.md

@@ -34,7 +34,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3
         with:
           username: ${{ secrets.BUF_USERNAME }}
           token: ${{ secrets.BUF_TOKEN }}
@@ -81,7 +81,7 @@ This will install `buf` and optionally login to the schema registry but no addit
 Subsequent steps will have `buf` available in their $PATH and can invoke `buf` directly.
 
 ```yaml
-- uses: bufbuild/[email protected].2
+- uses: bufbuild/[email protected].3
   with:
     setup_only: true
 - run: buf build --error-format github-actions
@@ -93,7 +93,7 @@ To skip or disable parts of the workflow, each step corresponds to a boolean fla
 For example to disable linting set the input `lint` to `false`:
 
 ```yaml
-- uses: bufbuild/[email protected].2
+- uses: bufbuild/[email protected].3
   with:
     lint: false
 ```
@@ -106,7 +106,7 @@ To trigger steps on different events use the GitHub action context to deduce the
 For example to enable formatting checks on both pull requests and push create an expression for the input `format`:
 
 ```yaml
-- uses: bufbuild/[email protected].2
+- uses: bufbuild/[email protected].3
   with:
     format: ${{ contains(fromJSON('["push", "pull_request"]'), github.event_name) }}
 ```
@@ -119,7 +119,7 @@ To conditionally run checks based on user input, use the GitHub action context t
 For example to disable breaking change detection on commits, create an expression on the input `breaking` to check the contents of the commit message:
 
 ```yaml
-- uses: bufbuild/[email protected].2
+- uses: bufbuild/[email protected].3
   with:
     breaking: |
       contains(fromJSON('["push", "pull_request"]'), github.event_name) &&
@@ -133,7 +133,7 @@ See [GitHub Actions job context](https://docs.github.com/en/actions/reference/co
 To ensure the version of `buf` is consistent across workflows it's recommended to always use an explicit version.
 
 ```yaml
-- uses: bufbuild/[email protected].2
+- uses: bufbuild/[email protected].3
   with:
     version: 1.32.2
 ```
@@ -153,7 +153,7 @@ The `username` and `token` values can be stored as secrets in the repository set
 The `token` value can be [generated from the Buf Schema Registry UI](https://buf.build/docs/bsr/authentication#create-an-api-token).
 
 ```yaml
-- uses: bufbuild/[email protected].2
+- uses: bufbuild/[email protected].3
   with:
     username: ${{ secrets.BUF_USERNAME }}
     token: ${{ secrets.BUF_TOKEN }}
@@ -191,7 +191,7 @@ runs-on: ubuntu-latest
 permissions:
   contents: read
 steps:
-  - uses: bufbuild/[email protected].2
+  - uses: bufbuild/[email protected].3
     with:
       comment: false
 ```
@@ -203,7 +203,7 @@ To run the action for inputs not specified at the root of the repository, set th
 Breaking change detection will also be required to be set to include a `subdir` configured to the same input path.
 
 ```yaml
-- uses: bufbuild/[email protected].2
+- uses: bufbuild/[email protected].3
   with:
     input: protos
     breaking_against: |
@@ -220,7 +220,7 @@ Alternatively, you may wish to pre-checkout the base branch for breaking changes
   with:
     path: base
     ref: ${{ github.event.pull_request.base.sha }}
-- uses: bufbuild/[email protected].2
+- uses: bufbuild/[email protected].3
   with:
     input: head/protos
     breaking_against: base/protos
@@ -293,7 +293,7 @@ jobs:
       contents: read
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3
         with:
           version: 1.32.2
           username: ${{ secrets.BUF_USERNAME }}

RELEASE.md

@@ -8,7 +8,7 @@ We follow the best practices outlined in the [GitHub Actions documentation][gith
 2. On a new branch, run the following commands to update the version of the action:
 
 ```bash
-VERSION=X.Y.Z make update-version
+VERSION=X.Y.Z make updateversion
 ```
 
 3. Open a PR titled "Prepare for vX.Y.Z". Once it's reviewed and CI passes, merge it.

examples/buf-ci.yaml

@@ -13,7 +13,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3
         with:
           username: ${{ secrets.BUF_USERNAME }}
           token: ${{ secrets.BUF_TOKEN }}

examples/only-checks.yaml

@@ -11,4 +11,4 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3

examples/only-setup-defaults.yaml

@@ -14,7 +14,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3
         with:
           setup_only: true
       - env:

examples/only-setup.yaml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3
         with:
           # Add username or token secrets to your repository settings to
           # authenticate with the Buf Schema Registry.

examples/only-sync.yaml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3
         with:
           username: ${{ secrets.BUF_USERNAME }}
           token: ${{ secrets.BUF_TOKEN }}

examples/push-on-changes.yaml

@@ -17,7 +17,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3
         with:
           username: ${{ secrets.BUF_USERNAME }}
           token: ${{ secrets.BUF_TOKEN }}

examples/skip-on-commits.yaml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3
         with:
           username: ${{ secrets.BUF_USERNAME }}
           token: ${{ secrets.BUF_TOKEN }}

examples/skip-on-labels.yaml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3
         with:
           username: ${{ secrets.BUF_USERNAME }}
           token: ${{ secrets.BUF_TOKEN }}

examples/validate-push.yaml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3
         with:
           # Username and token are required to authenticate with the Buf Schema Registry.
           username: ${{ secrets.BUF_USERNAME }}

examples/version-env.yaml

@@ -11,7 +11,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3
         with:
           setup_only: true
       - run: buf version

examples/version-input.yaml

@@ -9,7 +9,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3
         with:
           setup_only: true
           version: 1.32.2

examples/version-latest.yaml

@@ -9,7 +9,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/[email protected].2
+      - uses: bufbuild/[email protected].3
         with:
           setup_only: true
       - run: buf version