Repository navigation
chore: prepare py-rattler v0.29.0 release - #3038
Merged
Merged
Conversation
baszalmstra
force-pushed
the
prepare-py-rattler-v0.29.0
branch
3 times, most recently
from
November 9, 2026 16:33
51eb266 to
0b30a1a
Compare
baszalmstra
force-pushed
the
prepare-py-rattler-v0.29.0
branch
2 times, most recently
from
November 20, 2026 14:45
56a2c3f to
76685a6
Compare
baszalmstra
force-pushed
the
prepare-py-rattler-v0.29.0
branch
from
November 20, 2026 15:08
76685a6 to
683d6ac
Compare
baszalmstra
marked this pull request as ready for review
November 20, 2026 15:26
11 tasks
baszalmstra
approved these changes
Nov 20, 2026
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.
changelog
Description
py-rattler 0.29.0 from
main, rebased on da5a9c9 (#3218). Still a minor bump because of #2887: sharded channels and custom sources now applyPREFER_CONDAby default too, so the samesolve()/Gateway.query()call can return different records. A custom source serving only wheels now returns nothing unless you passPREFER_CONDA_WITH_WHLorALL.It also forward-ports the 0.28.1 section, which was released from a backport branch (#3037).
Since the first version of this PR I folded in #2968, #2974, #3134, #3077, #3058, #3019, #3127, #3089, #3102, #2947, the exclude-newer config work (#3020, #3024, #3082), the resolvo 0.12.2 speedup that came in through lock maintenance (#2993), plus the fixes and two security fixes (#3060, #2959) that landed in the crates.
Judgment calls, push back if you disagree:
additional_packagesoption to solver #2968 insertsadditional_packagesbeforevirtual_packages, so a fully positionalsolve()call shifts. That fails loudly, and I doubt anyone passes seven positional arguments, so it's listed as Added only.Configparsesexclude-newernow, so a config file with an invalid value (say an unquoted date) fails to load where 0.28 just ignored the key. I expect very few config files to have one. It's listed under Changed.ExcludeNewer#2985 (exemptions with their own cutoff) is still left out.solve(exclude_newer=...)only takes a datetime or a timedelta, so Python can't use exemptions in a solve.chore: release, rattler_vfs/exec/upload work that py-rattler doesn't depend on, or dependency bumps that don't change behavior.Nothing is pending anymore. #2671 is still open, but this release doesn't wait for it.
How Has This Been Tested?
I built
mainat 1d14168 in WSL and ran the new highlight snippets (additional_packages,ChannelPriority.VersionFirst) andsolve(..., package_format_selection=PackageFormatSelection.ALL)against conda-forge/bioconda. TheGateway.query(..., PREFER_CONDA_WITH_WHL)line needs a custom source, so I only checked it against the signature. For the exclude-newer entries I built 0.28.1 and 35b8bd2 and ran the sameConfig.from_toml_with_unused_keys(),keys(),set()andto_toml()calls on both.AI Disclosure
Tools: Claude Code