chore(ci): Update Pixi

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
jsonschema-rs (source)	feature-schema	minor	>=0.48.5,<0.49 → >=0.51,<0.52	0.52.1 (+1)
rattler-build	feature-python-test-deps	minor	>=0.70.0,<0.71 → >=0.73,<0.74	0.75.0 (+1)

---

Release Notes

Stranger6667/jsonschema (jsonschema-rs)

v0.51.0

Added

• ValidationOptions::with_vocabulary and the vocabularies attribute on jsonschema::validator, declaring support for a vocabulary this crate does not implement.
• The --vocabulary flag of jsonschema validate.

Changed

• Vocabulary gained the FormatAssertion variant, which its Draft 2020-12 URI parses to instead of Vocabulary::Custom, and is marked non_exhaustive.

Fixed

• The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
• The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
• A meta-schema requiring a vocabulary this crate does not implement accepted (it should be rejected).
• The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
• The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
• A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
• A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
• The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
• The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
• The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
• Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

• Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

v0.50.1

Changed

• CanonicalSchema::satisfiability answers Yes for a string whose pattern or format a matching value can be built from.
• CanonicalSchema::satisfiability answers No where a format takes no string of the length the schema asks for.

Fixed

• CanonicalSchema::negate taking apart a union that reads a definition through its own if, so a schema and its negation shared a value.
• CanonicalSchema::subtract dropping a Draft 4 array member an element demand partly takes.
• CanonicalSchema::covers answering Yes where a Draft 4 element demand refuses a member.
• A string schema whose maxLength is 0 keeping a pattern, format, or content facet unread, so the same constraints written in one object and written as an allOf reached different canonical forms.

Performance

• not over a wide object schema costs its branch count instead of its square.
• not over an object schema is linear in its property count, not quadratic.
• not over an object schema with additionalProperties: false no longer costs cubic time in its property count.

v0.50.0

Added

• CanonicalSchema::union and CanonicalSchema::subtract.
• CanonicalizationError::UnsupportedResult, reported where the canonical form does not support a set operation's result.
• OperandMismatch::DocumentRoots, reported where both operands read # and it names a different document on each side.
• CLI: jsonschema validate -i INSTANCE without a SCHEMA argument validates each instance against the schema named in its own $schema property. #​1470

Changed

• CanonicalSchema::is_satisfiable is now CanonicalSchema::satisfiability, answering Yes, No, or Unknown - Yes wherever a value can be exhibited, not only for the forms listing their members.
• CanonicalSchema::covers decides through the difference as well: No where the argument keeps values the receiver rejects, Yes where nothing is left over.
• CanonicalSchema::is_subset_of is now CanonicalSchema::covers, answering Yes, No, or Unknown for whether the receiver admits every value the argument admits.
• CanonicalSchema::negate returns Result rather than Option.
• CanonicalizationError::UnmodeledOperand is now CanonicalizationError::UnsupportedOperand, and means only that an operand is a Raw pass-through.
• A conjunction over a $ref folds through the body it names, so canonicalizing a document and combining its parts with the set operations reach one form; a document holding a reference cycle keeps the form it had.

Fixed

• Combining nodes of two different documents repointing a $ref to # at the combined result instead of the document it was written in, including one named by a definition the result keeps.
• Intersecting a $ref whose target is true or false, which panicked.
• A key constraint left un-narrowed once a run is out of intersections, which panicked on the next read of it.
• CanonicalSchema::covers answering Unknown for a schema against itself, where that schema is a $ref.
• CanonicalSchema::union keeping a $ref beside the schema it names, where the other three operations read through it.
• CanonicalSchema::covers and CanonicalSchema::subtract cancelling two nodes written the same way whose # names a different document.
• Two results accepting the same values comparing unequal over the part of their documents neither reads.
• additionalProperties reaching a key the pattern map matches when a finite key constraint closes the map, which dropped values both operands accept.
• A recursive definition stopping every other pointer in the document from being read through.
• One $defs entry read past a wider schema written out at every use, rather than kept as the pointer it was.
• Set operations rejecting one document canonicalized twice, and a pruned result rejected against the document it came from, where the maps resolve every shared reference the same way.
• Set operations comparing a $ref as a pointer instead of reading through it, so a schema written with a $ref did not cancel against the same schema written out.
• CanonicalSchema::subtract asking for a complement where the difference is one of the operands or empty, declining on schemas it can subtract.
• Set operations keeping $defs entries the result no longer references, which then showed up in the emitted schema.
• CanonicalSchema::union declining over an approximated intersection, where the union itself is exact.
• Resolving a reference against a base URI that carries a fragment, which happens when a Draft 4-7 $id contains one. #​1473
• unevaluatedProperties and unevaluatedItems ignoring an $id on a subschema they walk through, so a relative $ref inside it resolved against the enclosing resource.

Performance

• CLI: ~25% less CPU per run from compile-time meta-schema validators.

v0.49.9

Added

• Canonicalization of a oneOf whose branches name object targets a required constant tells apart, which degrades to a union.

Changed

• CanonicalSchema::to_json_schema on a definition emits only the definitions that one names, not the whole document's.

Fixed

• Canonicalization running without end on a conjunction over unions; past a ceiling on the meets it takes, the document stays unmodeled.

v0.49.5

Added

• Canonicalization of not an integer schema under Draft 4, which the number leaf carries as barred integers.
• Canonicalization of not a multipleOf, which numeric leaves carry as barred divisors.
• Canonicalization of not an integer schema, where a barred divisor of one spells the non-integer numbers.
• Canonicalization of not a pattern, which string leaves carry as barred patterns.
• Canonicalization of not a typed value set under Draft 4, such as {"type": "integer", "enum": [1, 2]}.
• CanonicalSchema::is_subset_of, whether the other schema admits every value this one admits.
• Canonicalization of a reference cycle carrying no assertion, which admits every value.

Fixed

• CanonicalSchema::is_subset_of failing to prove a union of array branches a subset of itself.
• CanonicalSchema::intersect admitting values one side rejects when its additionalProperties governs the keys the other side's patternProperties match.
• A satisfiable multipleOf schema collapsing to the empty set when f64 rounds its bounds together.
• Two spellings of one number canonicalizing to different texts under arbitrary-precision when the fraction exceeds the expansion cap.
• Numeric bounds and multipleOf comparing values through a lossy f64 conversion under arbitrary-precision, such as 1e-400 passing {"maximum": 0}.
• A union branch left unabsorbed when a sibling complement shed a conjunct from another branch.
• A union keeping an integer branch beside a number branch that admits every value of it.

v0.49.4

Added

• Canonicalization of not a string format, which the string leaf carries as barred formats.
• Canonicalization of not an existential demand, which an array fails exactly when no element matches.
• Canonicalization of not a string value set, which the string leaf carries as excluded values.
• Canonicalization of unevaluatedItems beside contains, where the elements it matches are evaluated and the tail admits either.
• Canonicalization of unevaluated* beside anyOf or oneOf, where every branch evaluating the same keys or indexes pins what is left over.
• Canonicalization of not an array element schema, which an array fails exactly when one element violates it.
• CanonicalSchema::intersect, the values both schemas admit.
• CanonicalSchema::negate, the values a schema rejects.
• CanonicalSchema::definition, one reference target by URI.

Fixed

• An integer past i64 admitted by a fractional bound f64 rounds it onto, such as -10000000000000000000000000 under {"maximum": -10000000000000000000000000.1}.
• An integer past 2^53 admitted by a bound f64 rounds onto it, such as 9007199254740992 under {"minimum": 9007199254740993}.
• A contains subschema beside both minContains and maxContains overwriting a sibling keyword of the same name, such as items.

Performance

• CanonicalSchema hashing and equality cost the node instead of the whole document.

v0.49.3

Added

• Canonicalization of a recursive schema with no finite witness, which now folds to false.
• Canonicalization of $dynamicRef and $recursiveRef, which resolve through the dynamic scope and stay symbolic like any other reference. A dangling $dynamicRef errors rather than staying Raw.
• Canonicalization of minContains under uniqueItems, where a demand asking for more matches than its own schema has distinct values now folds to false.
• Canonicalization of a Draft 4 patternProperties coverage closed by additionalProperties: false, spelled as the closed map it was parsed from.
• Canonicalization of a oneOf whose branches repeat, where a repeated branch can never contribute exactly one match.
• Canonicalization of a $ref whose target is an empty schema, which now folds to false.
• Canonicalization of unevaluatedItems beside allOf, where every branch must pass and so the indexes they evaluate are known without the instance.
• Canonicalization of unevaluatedProperties beside allOf, where every branch must pass and so what they evaluate is known without the instance.
• Canonicalization of a Draft 4 type list holding integer beside other types with enum, which previously modeled only when spelled as an allOf.
• Canonicalization of patternProperties patterns matching finitely many keys, such as ^a$ and ^(a|b)$.
• Canonicalization of unevaluatedProperties and unevaluatedItems when no in-place applicator sits beside them.

Fixed

• additionalItems values that are not schemas silently ignored beside an array-form items (they should fail the build like additionalProperties).
• additionalItems beside a boolean items rejecting every instance, such as {"additionalItems": false, "items": false}.
• additionalItems beside a non-array items value failing schema compilation with an error blaming additionalItems (the keyword should be ignored).
• Draft 4 rejecting a size bound at or past 2^64, such as {"maxItems": 18446744073709551616}.
• An integer past the f64 range admitted by a fractional bound it exceeds, such as 1e400 under {"exclusiveMaximum": 0.1}.
• A $ref at the root of an $id-bearing subresource dropped as a self-reference when its pointer matched the one that reached that subresource.
• Canonicalization reusing one definition's body for a same-named definition in another resource, when the name spells a canonical URI.
• unevaluatedItems counting prefixItems as evaluating elements before Draft 2020-12, where it is not a keyword.

Performance

• Up to 70% faster evaluate by building each location in a single allocation instead of two, reusing the instance location a node already built, and caching evaluation paths across instance nodes.

v0.49.2

Performance

• Faster serialization of canonicalized schemas.
• Faster macro code generation for subschemas with many keywords.
• Up to 70x faster canonicalization of multipleOf beside numeric bounds far from zero.

v0.49.1

Fixed

• jsonschema-value: Ruby builds on x64-mingw-ucrt.

prefix-dev/rattler-build (rattler-build)

v0.73.0

✨ Highlights

This release improves downstream-test reliability by selecting compatible Python builds, preserves executable-relative macOS rpaths, and makes test cleanup more robust. It also migrates the documentation toolchain from MkDocs to Zensical and corrects a documented target package name.

Documentation

• Switch from mkdocs to zensical by @​Hofer-Julian in #​2720
• Correct target package name by @​matthewfeickert in #​2726

Fixed

• Preserve executable-relative macOS rpaths by @​wolfv in #​2718
• Select compatible Python for downstream tests by @​wolfv in #​2725
• Use remove_dir_all_force helper in run_test.rs by @​lucascolley in #​2729

v0.72.2

✨ Highlights

This patch release enables trusted-publisher OIDC authentication when reading private prefix.dev channels during solving and --skip-existing all checks.

Fixed

• Authenticate private channel reads with trusted publishing by @​wolfv in #​2712

v0.72.0

✨ Highlights

This release introduces experimental build.steps as an alternative to build.script: each step is an isolated section of the build wrapper with its own if condition, interpreter, cwd, and env, so shell state no longer leaks between steps. It requires --experimental and is mutually exclusive with script. Recipes may now also carry a top-level $schema field for editor validation, and the process-execution layer gains reusable Runner and Session interfaces. Fixes cover case-insensitive RuntimeEnv lookups on Windows, deletion-only patches, Android DT_RUNPATH handling, and CEP-17 site-packages paths in SP_DIR.

Added

• Add experimental build steps by @​baszalmstra in #​2646
• Allow $schema top-level field in recipe.yaml by @​bollwyvl in #​2645
• Support steps in staging outputs by @​baszalmstra in #​2647
• Add Runner and Session execution interfaces by @​baszalmstra in #​2696

Fixed

• Ignore case when querying variables from RuntimeEnv on Windows by @​paperchalice in #​2676
• Deletion-only patches misdetected as already applied by @​wolfv in #​2695
• Use CEP-17 path for SP_DIR by @​wolfv in #​2700
• Use DT_RUNPATH instead of DT_RPATH on Android by @​wolfv in #​2699

Refactor

• Extract pure resolve_process_env by @​baszalmstra in #​2677
• Split process spawn from output handling by @​baszalmstra in #​2690
• Rename NativeShellRunner to ShellDialect by @​baszalmstra in #​2692
• Add an execution view for Directories by @​baszalmstra in #​2694
• Inject RuntimeEnv into script environment generation by @​baszalmstra in #​2691

New Contributors

• @​paperchalice made their first contribution in #​2676

v0.71.0

✨ Highlights

This release adds iOS and Android platform support and improves cross-architecture Windows command execution. It also fixes cache-output build setting inheritance and defers tests until transitive outputs are available.

Added

• Make CMD subprocesses match build_platform architecture when running emulated by @​baszalmstra in #​2664
• Add iOS and Android platform support by @​wolfv in #​2682

Fixed

• Package content tests for ios by @​wolfv in #​2684
• Defer tests until transitive outputs are built by @​wolfv in #​2686
• Stop wrapping solver errors by @​wolfv in #​2687
• Inherit all top-level build settings for cache outputs by @​Hofer-Julian in #​2641

Removed

• Remove the rattler-build-conda-compat integration API by @​Hofer-Julian in #​2675

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "on tuesday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pixi.lock

ExecError: Command failed: pixi lock --no-progress --color=never --quiet
Error:   × failed to solve requirements of environment 'python' for platform 'linux-64'
  ├─▶   × failed to solve the environment

  ╰─▶ Cannot solve the request because of: The following packages are incompatible
      ├─ rattler-build >=0.70.0,<0.71 cannot be installed because there are no viable options:
      │  ├─ rattler-build 0.70.1, which conflicts with the versions reported above.
      │  ├─ rattler-build 0.70.1, which conflicts with the versions reported above.
      │  └─ rattler-build 0.70.0, which conflicts with the versions reported above.
      └─ rattler-build >=0.73,<0.74 cannot be installed because there are no viable options:
         └─ rattler-build 0.73.0, which conflicts with the versions reported above.