@@ -5,7 +5,7 @@ gh-action-sigstore-python
5
5
[ ![ Self-test] ( https://github.com/sigstore/gh-action-sigstore-python/actions/workflows/selftest.yml/badge.svg )] ( https://github.com/sigstore/gh-action-sigstore-python/actions/workflows/selftest.yml )
6
6
7
7
A GitHub Action that uses [ ` sigstore-python ` ] ( https://github.com/sigstore/sigstore-python )
8
- to sign Python packages .
8
+ to generate Sigstore signatures .
9
9
10
10
## Index
11
11
@@ -23,24 +23,22 @@ Simply add `sigstore/gh-action-sigstore-python` to one of your workflows:
23
23
jobs :
24
24
selftest :
25
25
runs-on : ubuntu-latest
26
+ permissions :
27
+ id-token : write
26
28
steps :
27
29
- uses : actions/checkout@v3
28
30
- name : install
29
31
run : python -m pip install .
30
- - uses : sigstore/gh-action-sigstore-python@v0.2 .0
32
+ - uses : sigstore/gh-action-sigstore-python@v0.3 .0
31
33
with :
32
34
inputs : file.txt
33
35
` ` `
34
36
35
- Your workflow must have permission to request the OIDC token to authenticate with. This can be done
36
- by having a top-level ` permission` setting for your workflow.
37
+ Note: Your workflow ** must** have permission to request the OIDC token to authenticate with.
38
+ This can be done by setting ` id-token: write` on your job (as above) or workflow.
37
39
38
- ` ` ` yaml
39
- permissions:
40
- id-token: write
41
- ` ` `
42
-
43
- More information about permission settings can be found [here](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#adding-permissions-settings).
40
+ More information about permission settings can be found
41
+ [here](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#adding-permissions-settings).
44
42
45
43
# # Configuration
46
44
@@ -55,15 +53,15 @@ provided.
55
53
To sign one or more files :
56
54
57
55
` ` ` yaml
58
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
56
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
59
57
with:
60
58
inputs: file0.txt file1.txt file2.txt
61
59
` ` `
62
60
63
61
The `inputs` argument also supports file globbing :
64
62
65
63
` ` ` yaml
66
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
64
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
67
65
with:
68
66
inputs: ./path/to/inputs/*.txt
69
67
` ` `
@@ -76,7 +74,7 @@ The `identity-token` setting controls the OpenID Connect token provided to Fulci
76
74
workflow will use the credentials found in the GitHub Actions environment.
77
75
78
76
` ` ` yaml
79
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
77
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
80
78
with:
81
79
inputs: file.txt
82
80
identity-token: ${{ IDENTITY_TOKEN }} # assigned elsewhere
@@ -92,7 +90,7 @@ Server during OAuth2.
92
90
Example :
93
91
94
92
` ` ` yaml
95
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
93
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
96
94
with:
97
95
inputs: file.txt
98
96
oidc-client-id: alternative-sigstore-id
@@ -108,7 +106,7 @@ Connect Server during OAuth2.
108
106
Example :
109
107
110
108
` ` ` yaml
111
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
109
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
112
110
with:
113
111
inputs: file.txt
114
112
oidc-client-secret: alternative-sigstore-secret
@@ -124,7 +122,7 @@ when signing multiple input files.
124
122
Example :
125
123
126
124
` ` ` yaml
127
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
125
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
128
126
with:
129
127
inputs: file.txt
130
128
signature: custom-signature-filename.sig
@@ -133,7 +131,7 @@ Example:
133
131
However, this example is invalid :
134
132
135
133
` ` ` yaml
136
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
134
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
137
135
with:
138
136
inputs: file0.txt file1.txt file2.txt
139
137
signature: custom-signature-filename.sig
@@ -149,7 +147,7 @@ work when signing multiple input files.
149
147
Example :
150
148
151
149
` ` ` yaml
152
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
150
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
153
151
with:
154
152
inputs: file.txt
155
153
certificate: custom-certificate-filename.crt
@@ -158,7 +156,7 @@ Example:
158
156
However, this example is invalid :
159
157
160
158
` ` ` yaml
161
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
159
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
162
160
with:
163
161
inputs: file0.txt file1.txt file2.txt
164
162
certificate: custom-certificate-filename.crt
@@ -174,7 +172,7 @@ from. This setting cannot be used in combination with the `staging` setting.
174
172
Example :
175
173
176
174
` ` ` yaml
177
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
175
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
178
176
with:
179
177
inputs: file.txt
180
178
fulcio-url: https://fulcio.sigstage.dev
@@ -190,7 +188,7 @@ cannot be used in combination with the `staging` setting.
190
188
Example :
191
189
192
190
` ` ` yaml
193
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
191
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
194
192
with:
195
193
inputs: file.txt
196
194
rekor-url: https://rekor.sigstage.dev
@@ -206,7 +204,7 @@ in combination with the `staging` setting.
206
204
Example :
207
205
208
206
` ` ` yaml
209
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
207
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
210
208
with:
211
209
inputs: file.txt
212
210
ctfe: ./path/to/ctfe.pub
@@ -222,7 +220,7 @@ be used in combination with `staging` setting.
222
220
Example :
223
221
224
222
` ` ` yaml
225
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
223
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
226
224
with:
227
225
inputs: file.txt
228
226
ctfe: ./path/to/rekor.pub
@@ -238,7 +236,7 @@ instead of the default production instances.
238
236
Example :
239
237
240
238
` ` ` yaml
241
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
239
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
242
240
with:
243
241
inputs: file.txt
244
242
staging: true
@@ -261,7 +259,7 @@ and `verify-oidc-issuer` settings. Failing to pass these will produce an error.
261
259
Example :
262
260
263
261
` ` ` yaml
264
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
262
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
265
263
with:
266
264
inputs: file.txt
267
265
verify: true
@@ -284,7 +282,7 @@ This setting may only be used in conjunction with `verify-oidc-issuer`.
284
282
Supplying it without `verify-oidc-issuer` will produce an error.
285
283
286
284
` ` ` yaml
287
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
285
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
288
286
with:
289
287
inputs: file.txt
290
288
verify: true
@@ -309,7 +307,7 @@ Supplying it without `verify-cert-identity` will produce an error.
309
307
Example :
310
308
311
309
` ` ` yaml
312
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
310
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
313
311
with:
314
312
inputs: file.txt
315
313
verify: true
@@ -331,7 +329,7 @@ workflow artifact retention period is used.
331
329
Example :
332
330
333
331
` ` ` yaml
334
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
332
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
335
333
with:
336
334
inputs: file.txt
337
335
upload-signing-artifacts: true
@@ -356,7 +354,7 @@ permissions:
356
354
357
355
# ...
358
356
359
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
357
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
360
358
with:
361
359
inputs: file.txt
362
360
release-signing-artifacts: true
@@ -383,7 +381,7 @@ permissions:
383
381
Example :
384
382
385
383
` ` ` yaml
386
- - uses: sigstore/gh-action-sigstore-python@v0.2 .0
384
+ - uses: sigstore/gh-action-sigstore-python@v0.3 .0
387
385
with:
388
386
inputs: file.txt
389
387
internal-be-careful-debug: true
0 commit comments