Bump pinned pixi version from v0.58.0 to v0.81.0

[mkitti]

Summary

• Bumps the hardcoded Pixi.PIXI_VERSION pin in src/appose/tool/pixi.py from v0.58.0 to v0.81.0 (current latest release).
• pixi v0.58.0 fails intermittently with io error: unexpected end of file while fetching conda-forge repodata for some platforms during pixi install, breaking appose-managed environment builds (e.g. via skop.runner.Runner.ensure_environment).

Verification

• Reproduced the failure directly: cleared the shared rattler repodata cache and ran the bundled v0.58.0 pixi binary against a real failing pixi.toml manifest (4 platforms: win-64, osx-64, osx-arm64, linux-64) — consistently failed with io error: unexpected end of file after fetching only 2 of the 4 platforms' repodata.
• Confirmed the fix: downloaded pixi v0.81.0, cleared the repodata cache again, and ran it against the same manifest — resolved and installed cleanly for all 4 platforms.

Test plan

• Reproduced the underlying bug with the current pin (v0.58.0)
• Confirmed the new pin (v0.81.0) resolves it against the same manifest
• CI / maintainer review of full test suite (tests/builder/test_pixi.py etc.)

[mkitti]

Local run of tests/builder/test_pixi.py with the v0.81.0 pin: 11 passed in 529.89s (all environment-build tests, including test_pixi, test_pixi_activate, test_build_installs_env, etc.).

[mkitti]

This resulted from trying to resolve issues encountered in @bnorthan 's workshop at I2K x BINA 2026. The old pixi binary here interferes with the newer pixi binary I have installed on the system level.

[Copilot]

Copilot review overview

🟢 Approval recommended

The release and required platform assets exist, and the focused version update is internally consistent.

Review effort: Balanced
Findings: None

What changed in this PR

Updates Appose’s bundled Pixi version to resolve intermittent environment-build failures.

Changes:

• Bumps Pixi from v0.58.0 to verified release v0.81.0.

File	Description
src/​appose/​tool/​pixi.py	Updates the pinned Pixi download version.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[ctrueden]

Now added an automatic self-update step (2a11025 and apposed/appose-java@6be9f7c).

[mkitti]

I wonder if a new problem might now arise. Is it possible that the appose pixi might be newer than the system pixi?

[ctrueden]

Is it possible that the appose pixi might be newer than the system pixi?

Sure. Users can, of course, also update their system pixi to resolve the bugs of older versions.

Are there specific issues you foresee that would not be resolved by updating the system pixi?