63
63
` ` `
64
64
65
65
> [!NOTE]
66
- > Instead of using branch pointers, like ` unstable/v1`, pin versions of Actions
67
- > that you use to tagged versions or sha1 commit identifiers.
66
+ > Pro tip: instead of using branch pointers, like ` unstable/v1`, pin versions of
67
+ > Actions that you use to tagged versions or sha1 commit identifiers.
68
68
> This will make your workflows more secure and better reproducible, saving you
69
69
> from sudden and unpleasant surprises.
70
70
@@ -79,7 +79,7 @@ Other indices that support trusted publishing can also be used, like TestPyPI:
79
79
_(don't forget to update the environment name to `testpypi` or similar!)_
80
80
81
81
> [!NOTE]
82
- > Only set the `id-token: write` permission in the job that does
82
+ > Pro tip: only set the `id-token: write` permission in the job that does
83
83
> publishing, not globally. Also, try to separate building from publishing
84
84
> — this makes sure that any scripts maliciously injected into the build
85
85
> or test environment won't be able to elevate privileges while flying under
@@ -192,7 +192,7 @@ default) setting as follows:
192
192
` ` `
193
193
194
194
> [!NOTE]
195
- > Try to avoid enabling this setting where possible. If you
195
+ > Pro tip: try to avoid enabling this setting where possible. If you
196
196
> have steps for publishing to both PyPI and TestPyPI, consider only using
197
197
> it for the latter, having the former fail loudly on duplicates.
198
198
0 commit comments