You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+25-25Lines changed: 25 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ GitHub Action to set up the [pixi](https://github.com/prefix-dev/pixi) package m
23
23
## Usage
24
24
25
25
```yml
26
-
- uses: prefix-dev/setup-pixi@v0.9.6
26
+
- uses: prefix-dev/setup-pixi@v0.10.0
27
27
with:
28
28
pixi-version: v0.66.0
29
29
@@ -35,7 +35,7 @@ GitHub Action to set up the [pixi](https://github.com/prefix-dev/pixi) package m
35
35
36
36
> [!WARNING]
37
37
> Since pixi is not yet stable, the API of this action may change between minor versions.
38
-
> Please pin the versions of this action to a specific version (i.e., `prefix-dev/setup-pixi@v0.9.6`) to avoid breaking changes.
38
+
> Please pin the versions of this action to a specific version (i.e., `prefix-dev/setup-pixi@v0.10.0`) to avoid breaking changes.
39
39
> You can automatically update the version of this action by using [Dependabot](https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot).
40
40
>
41
41
> Put the following in your `.github/dependabot.yml` file to enable Dependabot for your GitHub Actions:
@@ -79,7 +79,7 @@ In order to not exceed the [10 GB cache size limit](https://docs.github.com/en/a
79
79
This can be done by setting the `cache-write` argument.
The following example will install both the `py311` and the `py312` environment on the runner.
135
135
136
136
```yml
137
-
- uses: prefix-dev/setup-pixi@v0.9.6
137
+
- uses: prefix-dev/setup-pixi@v0.10.0
138
138
with:
139
139
# separated by spaces
140
140
environments: >-
@@ -157,7 +157,7 @@ For instance, the `keyring`, or `gcloud` executables. The following example show
157
157
By default, global environments are not cached. You can enable caching by setting the `global-cache` input to `true`.
158
158
159
159
```yml
160
-
- uses: prefix-dev/setup-pixi@v0.9.6
160
+
- uses: prefix-dev/setup-pixi@v0.10.0
161
161
with:
162
162
global-environments: |
163
163
google-cloud-sdk
@@ -190,7 +190,7 @@ Specify the token using the `auth-token` input argument.
190
190
This form of authentication (bearer token in the request headers) is mainly used at [prefix.dev](https://prefix.dev).
191
191
192
192
```yml
193
-
- uses: prefix-dev/setup-pixi@v0.9.6
193
+
- uses: prefix-dev/setup-pixi@v0.10.0
194
194
with:
195
195
auth-host: prefix.dev
196
196
auth-token: ${{ secrets.PREFIX_DEV_TOKEN }}
@@ -202,7 +202,7 @@ Specify the username and password using the `auth-username` and `auth-password`
202
202
This form of authentication (HTTP Basic Auth) is used in some enterprise environments with [artifactory](https://jfrog.com/artifactory) for example.
203
203
204
204
```yml
205
-
- uses: prefix-dev/setup-pixi@v0.9.6
205
+
- uses: prefix-dev/setup-pixi@v0.10.0
206
206
with:
207
207
auth-host: custom-artifactory.com
208
208
auth-username: ${{ secrets.PIXI_USERNAME }}
@@ -215,7 +215,7 @@ Specify the conda-token using the `auth-conda-token` input argument.
215
215
This form of authentication (token is encoded in URL: `https://my-quetz-instance.com/t/<token>/get/custom-channel`) is used at [anaconda.org](https://anaconda.org) or with [quetz instances](https://github.com/mamba-org/quetz).
216
216
217
217
```yml
218
-
- uses: prefix-dev/setup-pixi@v0.9.6
218
+
- uses: prefix-dev/setup-pixi@v0.10.0
219
219
with:
220
220
auth-host: anaconda.org # or my-quetz-instance.com
221
221
auth-conda-token: ${{ secrets.CONDA_TOKEN }}
@@ -227,7 +227,7 @@ Specify the S3 key pair using the `auth-access-key-id` and `auth-secret-access-k
227
227
You can also specify the session token using the `auth-session-token` input argument.
@@ -246,7 +246,7 @@ then run `pixi auth logout <auth-host>` after `pixi install` has completed but b
246
246
returns, so that later steps cannot reach the private channel anymore.
247
247
248
248
```yml
249
-
- uses: prefix-dev/setup-pixi@v0.9.6
249
+
- uses: prefix-dev/setup-pixi@v0.10.0
250
250
with:
251
251
auth-host: prefix.dev
252
252
auth-token: ${{ secrets.PREFIX_DEV_TOKEN }}
@@ -258,7 +258,7 @@ returns, so that later steps cannot reach the private channel anymore.
258
258
You can specify whether to use keyring to look up credentials for PyPI.
259
259
260
260
```yml
261
-
- uses: prefix-dev/setup-pixi@v0.9.6
261
+
- uses: prefix-dev/setup-pixi@v0.10.0
262
262
with:
263
263
pypi-keyring-provider: subprocess # one of 'subprocess', 'disabled'
264
264
```
@@ -326,15 +326,15 @@ To this end, `setup-pixi` adds all environment variables set when executing `pix
326
326
As a result, all installed binaries can be accessed without having to call `pixi run`.
327
327
328
328
```yml
329
-
- uses: prefix-dev/setup-pixi@v0.9.6
329
+
- uses: prefix-dev/setup-pixi@v0.10.0
330
330
with:
331
331
activate-environment: true
332
332
```
333
333
334
334
If you are installing multiple environments, you will need to specify the name of the environment that you want to be activated.
335
335
336
336
```yml
337
-
- uses: prefix-dev/setup-pixi@v0.9.6
337
+
- uses: prefix-dev/setup-pixi@v0.10.0
338
338
with:
339
339
environments: >-
340
340
py311
@@ -351,7 +351,7 @@ You can specify whether `setup-pixi` should run `pixi install --frozen` or `pixi
351
351
See the [official documentation](https://pixi.sh/latest/reference/cli/pixi/install/#update-options) for more information about the `--frozen` and `--locked` flags.
352
352
353
353
```yml
354
-
- uses: prefix-dev/setup-pixi@v0.9.6
354
+
- uses: prefix-dev/setup-pixi@v0.10.0
355
355
with:
356
356
locked: true
357
357
# or
@@ -370,7 +370,7 @@ The first one is the debug logging of the action itself.
370
370
This can be enabled by running the action with the `RUNNER_DEBUG` environment variable set to `true`.
371
371
372
372
```yml
373
-
- uses: prefix-dev/setup-pixi@v0.9.6
373
+
- uses: prefix-dev/setup-pixi@v0.10.0
374
374
env:
375
375
RUNNER_DEBUG: true
376
376
```
@@ -388,7 +388,7 @@ The second type is the debug logging of the pixi executable.
388
388
This can be specified by setting the `log-level` input.
389
389
390
390
```yml
391
-
- uses: prefix-dev/setup-pixi@v0.9.6
391
+
- uses: prefix-dev/setup-pixi@v0.10.0
392
392
with:
393
393
# one of `q`, `default`, `v`, `vv`, or `vvv`.
394
394
log-level: vvv
@@ -409,12 +409,12 @@ If you set `post-cleanup` to `true`, the action will delete the following files:
409
409
- the rattler cache
410
410
- other rattler files in `~/.rattler`
411
411
412
-
If nothing is specified, `post-cleanup` will default to `true`.
412
+
If nothing is specified, `post-cleanup` will default to `false`.
413
413
414
414
On self-hosted runners, you also might want to alter the default pixi install location to a temporary location. You can use `pixi-bin-path: ${{ runner.temp }}/bin/pixi` to do this.
415
415
416
416
```yml
417
-
- uses: prefix-dev/setup-pixi@v0.9.6
417
+
- uses: prefix-dev/setup-pixi@v0.10.0
418
418
with:
419
419
post-cleanup: true
420
420
# ${{ runner.temp }}\Scripts\pixi.exe on Windows
@@ -430,7 +430,7 @@ You can also use a preinstalled local version of pixi on the runner by not setti
430
430
This can be overwritten by setting the `manifest-path` input argument.
431
431
432
432
```yml
433
-
- uses: prefix-dev/setup-pixi@v0.9.6
433
+
- uses: prefix-dev/setup-pixi@v0.10.0
434
434
with:
435
435
manifest-path: pyproject.toml
436
436
```
@@ -440,7 +440,7 @@ This can be overwritten by setting the `manifest-path` input argument.
440
440
If you're working with a monorepo where your pixi project is in a subdirectory, you can use the `working-directory` input to specify where pixi should look for manifest files (`pixi.toml` or `pyproject.toml`).
441
441
442
442
```yml
443
-
- uses: prefix-dev/setup-pixi@v0.9.6
443
+
- uses: prefix-dev/setup-pixi@v0.10.0
444
444
with:
445
445
working-directory: ./packages/my-project
446
446
```
@@ -459,7 +459,7 @@ This will make pixi look for `pixi.toml` or `pyproject.toml` in the `./packages/
459
459
You can combine `working-directory` with `manifest-path` if needed:
460
460
461
461
```yml
462
-
- uses: prefix-dev/setup-pixi@v0.9.6
462
+
- uses: prefix-dev/setup-pixi@v0.10.0
463
463
with:
464
464
working-directory: ./packages/my-project
465
465
manifest-path: custom-pixi.toml
@@ -470,7 +470,7 @@ You can combine `working-directory` with `manifest-path` if needed:
470
470
If you only want to install pixi and not install the current project, you can use the `run-install` option.
471
471
472
472
```yml
473
-
- uses: prefix-dev/setup-pixi@v0.9.6
473
+
- uses: prefix-dev/setup-pixi@v0.10.0
474
474
with:
475
475
run-install: false
476
476
```
@@ -481,7 +481,7 @@ You can also download pixi from a custom URL by setting the `pixi-url` input arg
481
481
Optionally, you can combine this with the `pixi-url-headers` input argument to supply additional headers for the download request, such as a bearer token.
0 commit comments