Skip to content

chore: update rattler and rattler-build crates - #7123

Merged
Hofer-Julian merged 2 commits into
prefix-dev:mainfrom
baszalmstra:bas/update-rattler
Oct 1, 2026
Merged

Hofer-Julian merged 2 commits into
prefix-dev:mainfrom
baszalmstra:bas/update-rattler

Conversation

@baszalmstra

@baszalmstra baszalmstra commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Description

This updates pixi to the latest rattler releases (rattler 0.51, rattler_conda_types 0.55, rattler_solve 10, rattler_lock 0.34, rattler_virtual_packages 8, etc.) and to the rattler-build crates that were released on top of them (prefix-dev/rattler-build#2834). The published rattler-build crates pinned the older rattler, so both had to move together. Only major/minor bumps are in Cargo.toml; patch updates are in Cargo.lock only. All sigstore-* crates now resolve to a single version (0.14).

Most of the diff is the Platform → Subdir rename from conda/rattler#2787, applied only to rattler's type; pixi's own platform types keep their names. Subdir::current() now returns an Option. Where we used to get Platform::Unknown we now fall back to Subdir::NoArch, which answers the is_* checks the same way.

Things that change for users:

  • S3 options in the pixi config: rattler_config 0.8 replaced force-path-style with addressing-style = "path" | "virtual-host" and doesn't accept the old key, so an existing force-path-style = true in config.toml is now silently ignored. I updated the docs, the pixi config set example and the tests. The [workspace.s3-options] table in the manifest still uses force-path-style, so the two now differ. Please check whether we want a compatibility shim or a migration note for this.
  • exclude-newer: records are now compared using indexed_timestamp if present and the build timestamp otherwise, the same way rattler_solve 10 does it. That covers the lock file satisfiability check and the global environment sync check.
  • pixi publish --force to Quetz now actually forces the overwrite, since rattler_upload takes a ForceOverwrite argument.
  • Build backends: the generated recipes no longer contain files: [], because rattler-build made files optional; an empty list used to mean "package everything" and is now just left out. That's why 20 backend snapshots changed. DiscoveredOutput also gained pin_subpackages, which we fill from the rendered recipe.

How Has This Been Tested?

  • cargo clippy --workspace --all-targets --all-features -- -D warnings, cargo fmt --check, cargo shear, cargo deny (licenses) and typos all pass.
  • cargo nextest passes for pixi_cli, pixi_global, pixi_command_dispatcher, pixi_api, pixi_config, pixi_manifest, pixi_core, pixi_build_backend and all build backends. I didn't run the integration_rust tests of crates/pixi locally.
  • Manually on Windows: pixi info works. pixi config set s3-options.my-bucket '{"endpoint-url": …, "addressing-style": "path", "region": "auto"}' writes the new key, and an invalid value like "sideways" is rejected with unknown variant \sideways`, expected `virtual-host` or `path``.

AI Disclosure

  • This PR contains AI-generated content.
    • I have tested any AI-generated content in my PR.
    • I take responsibility for any AI-generated content in my PR.

Tools: Claude

Checklist:

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation

@baszalmstra
baszalmstra marked this pull request as ready for review October 1, 2026 09:29

@Hofer-Julian Hofer-Julian left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@Hofer-Julian
Hofer-Julian merged commit 85e6e34 into prefix-dev:main Oct 1, 2026
40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants