Bump prefix-dev/setup-pixi from 0.9.6 to 0.10.2 - #541
Conversation
Bumps [prefix-dev/setup-pixi](https://github.com/prefix-dev/setup-pixi) from 0.9.6 to 0.10.2. - [Release notes](https://github.com/prefix-dev/setup-pixi/releases) - [Commits](prefix-dev/setup-pixi@v0.9.6...v0.10.2) --- updated-dependencies: - dependency-name: prefix-dev/setup-pixi dependency-version: 0.10.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
blooop
left a comment
blooop
left a comment
There was a problem hiding this comment.
Reviewed against the one breaking change in this range. setup-pixi 0.10.0
changed the post-cleanup default from true to false
(prefix-dev/setup-pixi#272),
so the pixi environment now survives the job instead of being torn down at the
end.
That only bites a runner whose filesystem outlives the job. Every runs-on: in
this repository is GitHub-hosted and ephemeral — ubuntu-latest everywhere plus
ubuntu-24.04-arm in the devcontainer-prebuild matrix — so the environment
this no longer deletes is discarded with the VM either way. No self-hosted
runner to leak into.
The five call sites move together, and the three that pass cache: true/frozen: true keep doing so. ci, e2e, packaging, public-api, rust and
rust-coverage are all green on this head, which exercises three of the five.
1 participant
Bumps prefix-dev/setup-pixi from 0.9.6 to 0.10.2.
Release notes
Sourced from prefix-dev/setup-pixi's releases.
Commits
d3f436afeat: Add support for linux-riscv64 (#282)f00437fUpdate dependencies and add pnpm workspace configuration (#279)d0c199dchore(deps): bump the gh-actions group with 3 updates (#276)2253d9cchore(deps): bump the gh-actions group with 3 updates (#273)c5359a3chore(deps): bump the nodejs group with 6 updates (#274)a09b624feat: change post-cleanup default to false (#272)947fc1fchore(deps): bump the nodejs group with 6 updates (#269)36c1c8cchore(deps): bump the gh-actions group with 2 updates (#268)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)