36
36
runs-on : ubuntu-latest
37
37
steps :
38
38
- uses : actions/checkout@v4
39
- - uses : bufbuild/buf-action@v0.1
39
+ - uses : bufbuild/buf-action@v0.2
40
40
with :
41
41
username : ${{ secrets.BUF_USERNAME }}
42
42
token : ${{ secrets.BUF_TOKEN }}
@@ -57,7 +57,7 @@ To customize the behavior of the action, you can set the following parameters in
57
57
Add these parameters under the `with` section of the `uses` step in the workflow file.
58
58
59
59
` ` ` yaml
60
- - uses: bufbuild/buf-action@v0.1
60
+ - uses: bufbuild/buf-action@v0.2
61
61
with:
62
62
...
63
63
` ` `
@@ -101,7 +101,7 @@ To disable parts of the workflow, each step corresponds to a boolean flag in the
101
101
For example to disable formatting set the parameter `format` to `false` :
102
102
103
103
` ` ` yaml
104
- - uses: bufbuild/buf-action@v0.1
104
+ - uses: bufbuild/buf-action@v0.2
105
105
with:
106
106
format: false
107
107
` ` `
@@ -113,7 +113,7 @@ See [action.yml](action.yml) for all available parameters.
113
113
For reproducible builds, you can pin to an explicit version of `buf` by setting `version`.
114
114
115
115
` ` ` yaml
116
- - uses: bufbuild/buf-action@v0.1
116
+ - uses: bufbuild/buf-action@v0.2
117
117
with:
118
118
version: 1.34.0
119
119
` ` `
@@ -135,7 +135,7 @@ The `username` and `token` values should be
135
135
The `token` value can be [generated from the BSR UI](https://buf.build/docs/bsr/authentication#create-an-api-token).
136
136
137
137
` ` ` yaml
138
- - uses: bufbuild/buf-action@v0.1
138
+ - uses: bufbuild/buf-action@v0.2
139
139
with:
140
140
username: ${{ secrets.BUF_USERNAME }}
141
141
token: ${{ secrets.BUF_TOKEN }}
@@ -166,7 +166,7 @@ jobs:
166
166
runs-on: ubuntu-latest
167
167
steps:
168
168
- uses: actions/checkout@v4
169
- - uses: bufbuild/buf-action@v0.1
169
+ - uses: bufbuild/buf-action@v0.2
170
170
with:
171
171
username: ${{ secrets.BUF_USERNAME }}
172
172
token: ${{ secrets.BUF_TOKEN }}
@@ -179,7 +179,7 @@ To run the action for parameters not declared at the root of the repository,
179
179
set the parameter `input` to the directory of your `buf.yaml` file.
180
180
181
181
` ` ` yaml
182
- - uses: bufbuild/buf-action@v0.1
182
+ - uses: bufbuild/buf-action@v0.2
183
183
with:
184
184
input: <path/to/module>
185
185
` ` `
@@ -188,7 +188,7 @@ Breaking change detection by default will use the `input` value as a subdirector
188
188
To customize this behavior, set the parameter `breaking_against` to the desired input.
189
189
190
190
` ` ` yaml
191
- - uses: bufbuild/buf-action@v0.1
191
+ - uses: bufbuild/buf-action@v0.2
192
192
with:
193
193
input: <path/to/module>
194
194
breaking_against: ${{ github.event.repository.clone_url }}#format=git,commit=${{ github.event.pull_request.base.sha }},subdir=<path/to/module>
@@ -205,7 +205,7 @@ and then set the value of `breaking_against` to the path of the base.
205
205
with:
206
206
path: base
207
207
ref: ${{ github.event.pull_request.base.sha }}
208
- - uses: bufbuild/buf-action@v0.1
208
+ - uses: bufbuild/buf-action@v0.2
209
209
with:
210
210
input: head/<path/to/module>
211
211
breaking_against: base/<path/to/module>
@@ -220,7 +220,7 @@ This will install `buf` and optionally login to the schema registry but no addit
220
220
Subsequent steps will have `buf` available in their $PATH and can invoke `buf` directly.
221
221
222
222
` ` ` yaml
223
- - uses: bufbuild/buf-action@v0.1
223
+ - uses: bufbuild/buf-action@v0.2
224
224
with:
225
225
setup_only: true
226
226
- run: buf build --error-format github-actions
@@ -234,7 +234,7 @@ To trigger steps on different events use the GitHub action context to deduce the
234
234
For example to enable formatting checks on both pull requests and push create an expression for the parameter `format` :
235
235
236
236
` ` ` yaml
237
- - uses: bufbuild/buf-action@v0.1
237
+ - uses: bufbuild/buf-action@v0.2
238
238
with:
239
239
format: ${{ contains(fromJSON('["push", "pull_request"]'), github.event_name) }}
240
240
` ` `
@@ -247,7 +247,7 @@ To conditionally run checks based on user input, use the GitHub action context t
247
247
For example to disable breaking change detection on commits, create an expression on the parameter `breaking` to check the contents of the commit message :
248
248
249
249
` ` ` yaml
250
- - uses: bufbuild/buf-action@v0.1
250
+ - uses: bufbuild/buf-action@v0.2
251
251
with:
252
252
breaking: |
253
253
contains(fromJSON('["push", "pull_request"]'), github.event_name) &&
0 commit comments