Repository navigation
chore: update rattler and rattler-build crates - #7123
Merged
Merged
Conversation
4 of 5 tasks
baszalmstra
marked this pull request as ready for review
October 1, 2026 09:29
4 tasks done
1 of 8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 inCargo.lockonly. Allsigstore-*crates now resolve to a single version (0.14).Most of the diff is the
Platform→Subdirrename from conda/rattler#2787, applied only to rattler's type; pixi's own platform types keep their names.Subdir::current()now returns anOption. Where we used to getPlatform::Unknownwe now fall back toSubdir::NoArch, which answers theis_*checks the same way.Things that change for users:
force-path-stylewithaddressing-style = "path" | "virtual-host"and doesn't accept the old key, so an existingforce-path-style = trueinconfig.tomlis now silently ignored. I updated the docs, thepixi config setexample and the tests. The[workspace.s3-options]table in the manifest still usesforce-path-style, so the two now differ. Please check whether we want a compatibility shim or a migration note for this.indexed_timestampif 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 --forceto Quetz now actually forces the overwrite, since rattler_upload takes aForceOverwriteargument.files: [], because rattler-build madefilesoptional; an empty list used to mean "package everything" and is now just left out. That's why 20 backend snapshots changed.DiscoveredOutputalso gainedpin_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) andtyposall pass.cargo nextestpasses 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 theintegration_rusttests ofcrates/pixilocally.pixi infoworks.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 withunknown variant \sideways`, expected `virtual-host` or `path``.AI Disclosure
Tools: Claude
Checklist: