[dependabot]

Bumps the production-dependencies group with 10 updates in the / directory:

Package	From	To
geojson	0.24.2	1.0.0
geozero	0.14.0	0.15.1
jiff	0.2.37	0.2.38
jsonschema	0.33.0	0.49.4
pest	2.9.2	2.9.4
pest_derive	2.9.2	2.9.4
serde_json	1.0.151	1.0.154
sqlparser	0.62.0	0.63.0
proptest	1.11.0	1.12.0
rstest	0.26.1	0.27.0

Updates geojson from 0.24.2 to 1.0.0

Changelog

Sourced from geojson's changelog.

v1.0.0 - 2025-03-16

• BREAKING: Position is now a struct, rather than a type alias for Vec. The new struct uses the tinyvec crate, which allows for faster GeoJSON processing in the common (2-D) case by avoiding per-coordinate heap allocations.

  // BEFORE: Position *was* a Vec. A Vec is always allocated on the heap, which is slow.
  let position: Position = vec![1.0, 2.0];
  let x = position[0];
  // AFTER: Position is its own type, buildable from a Vec.
  let position: Position = vec![1.0, 2.0].into();
  // index access is unchanged
  let x = position[0];
  // Alternatively, you can now construct from an Array, avoiding the Vec's heap allocation.
  let position: Position = [1.0, 2.0].into();
  // equivalently:
  let position = Position::from([1.0, 2.0]);
  // You can still build 3D+ Positions. These higher dimension coordinates will use Heap storage.
  let position = Position::from([1.0, 2.0, 3.0]);
  let position = Position::from(vec![1.0, 2.0, 3.0, 4.0, 5.0, 6.0]);

  • See georust/geojson#222
• Substantially speed up parsing (Benches show 30% reduction). This was essentially a rewrite of our deserialization logic. Instead of going from input -> serde_json::JsonObject -> geojson types we now go directly from input -> geojson types.
• Deserialization errors now include line number and column position. Before:

  Encountered neither number type nor string type for 'id' field on 'feature' object: {} After: Error while deserializing GeoJSON: Feature 'id' must be a string or a number at line 3 column 11

• BREAKING: geojson::Error has had many cases removed and some new cases added, reflecting the deserialization rewrite.
• BREAKING: TryInto/From implementations for serde_json::Value and serde_json::Object have been removed now that they are not used for deserialization.
• type is now the first field when serializing GeoJSON objects.
• Since feature.id is optional, we now accept "id: null", whereas previously you were required to omit the id key. Now either is acceptable.
• Fix: Return [] instead of [[]] for POLYGON EMPTY.
  • See georust/geojson#262
• Potentially breaking: De/Serializing your custom structs with serde now maps your struct's id field to Feature.id, rather than to Feature.properties.id.
• Fix geo_rect_conversion_test to conform to the correctly-wound Polygon output from geo_types::geometry::Rect.to_polygon

... (truncated)

Commits

• f6eafed prepare for 1.0.0 release
• 8c12816 prepare for 0.25.0 release
• c64043f simpler docs
• fa96c26 update to rust 2024 (#273)
• 3c362b4 Additional ergonomic constructors (for Geometry and FeatureCollection) (#271)
• f5fffd0 Remove methods related to json to/from now that we ser/de directly (#270)
• de445d9 Speed up parsing by deserializing directly to geojson (without intermediate s...
• a7870db Move code around - no new functionality (#268)
• 37ea3c9 Merge branch 'mkirk/derive-serialization-3'
• 67c07a1 derive Serialization rather than manual impls
• Additional commits viewable in compare view

Updates geozero from 0.14.0 to 0.15.1

Commits

• See full diff in compare view

Updates jiff from 0.2.37 to 0.2.38

Changelog

Sourced from jiff's changelog.

0.2.38 (2026-10-06)

This release updates Jiff's bundled copy of the [IANA Time Zone Database] to 2026e. See the 2026e release announcement for more details.

Commits

• 4ce3e20 0.2.38
• bca7bb9 jiff-tzdb-0.1.9
• 374afc2 jiff-tzdb: update to tzdb 2026e
• 5416198 doc: include readme in published crate
• See full diff in compare view

Updates jsonschema from 0.33.0 to 0.49.4

Release notes

Sourced from jsonschema's releases.

[CLI] Release 0.49.4

No release notes provided.

[Python] Release 0.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.

[Ruby] Release 0.49.4

[0.49.4] - 2026-08-04

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.

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.49.4] - 2026-08-04

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.

[0.49.3] - 2026-08-02

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.

... (truncated)

Commits

• 796a27e chore(rust): Release 0.49.4
• a35cc7e feat: Canonicalization of not a string format, which the string leaf carrie...
• b1d7f1a chore: Misc canonicalization improvements
• c8f7cc7 fix: An integer past 2^53 admitted by a bound f64 rounds onto it
• bc47249 perf: Cache intersections
• 5dd6483 feat: Canonicalization of not an existential demand, which an array fails e...
• 433adcd feat: Canonicalization of not a string value set, which the string leaf car...
• 4f0e406 test: Add fuzzing for canonicalization
• 08394f3 feat: Canonicalization of not an array element schema, which an array fails...
• c6146e4 ci: Revert wall-time benchmark job for the jsonschema package
• Additional commits viewable in compare view

Updates pest from 2.9.2 to 2.9.4

Release notes

Sourced from pest's releases.

v2.9.4

What's Changed

• add Cargo.lock for reproducible builds (fixes #1161) by @​tomtau in pest-parser/pest#1230
• validator: reject repetitions that loop because of the stack by @​yuxi-liu-wired in pest-parser/pest#1227
• Fix typos in three-string fast path of skip_until by @​shivampwm2020 in pest-parser/pest#1231

New Contributors

• @​yuxi-liu-wired made their first contribution in pest-parser/pest#1227
• @​shivampwm2020 made their first contribution in pest-parser/pest#1231

Full Changelog: pest-parser/pest@v2.9.3...v2.9.4

Warning: Semantic Versioning

Note that the node tag feature in 2.6.0 was a technically semver-breaking change even though it is a backwards-compatible / non-breaking change in the meta-grammar. There may be similar non-breaking changes to the meta-grammar between minor versions in the future. These non-breaking changes, however, may translate into semver-breaking changes due to the additional variants propagated from the generated Rule enum.

This new feature caused issues in some Cargo version resolution situations where Cargo mixed different versions of pest dependencies. For this reason, these "grammar non-breaking but semver-breaking" changes are now available only under the "grammar-extras" feature flag. If you would like to use node tags (or other future grammar features), you can do so by enabling this flag on the pest_derive crate in your Cargo.toml:

...
pest_derive = { version = "2.9", features = ["grammar-extras"] }

v2.9.3

What's Changed

• bump syn to 3 by @​tomtau in pest-parser/pest#1210
• Detect left recursion behind a prefix that can match empty (fixes #411) by @​breken-ai in pest-parser/pest#1211
• Limit parse depth by @​tomtau in pest-parser/pest#1212
• Remove reqwest dependency from pest_debugger by @​tomtau with @​Copilot in pest-parser/pest#1209

New Contributors

• @​breken-ai made their first contribution in pest-parser/pest#1211

Full Changelog: pest-parser/pest@v2.9.2...v2.9.3

Warning: Semantic Versioning

Note that the node tag feature in 2.6.0 was a technically semver-breaking change even though it is a backwards-compatible / non-breaking change in the meta-grammar. There may be similar non-breaking changes to the meta-grammar between minor versions in the future. These non-breaking changes, however, may translate into semver-breaking changes due to the additional variants propagated from the generated Rule enum.

This new feature caused issues in some Cargo version resolution situations where Cargo mixed different versions of pest dependencies. For this reason, these "grammar non-breaking but semver-breaking" changes are now available only under the "grammar-extras" feature flag. If you would like to use node tags (or other future grammar features), you can do so by enabling this flag on the pest_derive crate in your Cargo.toml:

...
pest_derive = { version = "2.9", features = ["grammar-extras"] }

Commits

• 66a059c Fix typos in the three-string fast path of skip_until (#1231)
• b4882ad validator: reject repetitions that loop because of the stack (#1227) (fixes 1...
• 7e779b7 add Cargo.lock for reproducible builds (fixes #1161) (#1230)
• 4248cbd bump version to 2.9.3 (#1228)
• 429e893 Limit parse depth (#1212)
• 3cdface Detect left recursion behind a prefix that can match empty (fixes #411) (#1211)
• 9124917 Add AI contribution and usage policy (#1221)
• 9abf9e5 bump syn to 3 (#1210)
• acf7fd9 Remove reqwest dependency from pest_debugger (#1209)
• c32c2da Remove workflow-wide actions write permission (#1208)
• See full diff in compare view

Updates pest_derive from 2.9.2 to 2.9.4

Release notes

Sourced from pest_derive's releases.

v2.9.4

What's Changed

• add Cargo.lock for reproducible builds (fixes #1161) by @​tomtau in pest-parser/pest#1230
• validator: reject repetitions that loop because of the stack by @​yuxi-liu-wired in pest-parser/pest#1227
• Fix typos in three-string fast path of skip_until by @​shivampwm2020 in pest-parser/pest#1231

New Contributors

• @​yuxi-liu-wired made their first contribution in pest-parser/pest#1227
• @​shivampwm2020 made their first contribution in pest-parser/pest#1231

Full Changelog: pest-parser/pest@v2.9.3...v2.9.4

Warning: Semantic Versioning

Note that the node tag feature in 2.6.0 was a technically semver-breaking change even though it is a backwards-compatible / non-breaking change in the meta-grammar. There may be similar non-breaking changes to the meta-grammar between minor versions in the future. These non-breaking changes, however, may translate into semver-breaking changes due to the additional variants propagated from the generated Rule enum.

This new feature caused issues in some Cargo version resolution situations where Cargo mixed different versions of pest dependencies. For this reason, these "grammar non-breaking but semver-breaking" changes are now available only under the "grammar-extras" feature flag. If you would like to use node tags (or other future grammar features), you can do so by enabling this flag on the pest_derive crate in your Cargo.toml:

...
pest_derive = { version = "2.9", features = ["grammar-extras"] }

v2.9.3

What's Changed

• bump syn to 3 by @​tomtau in pest-parser/pest#1210
• Detect left recursion behind a prefix that can match empty (fixes #411) by @​breken-ai in pest-parser/pest#1211
• Limit parse depth by @​tomtau in pest-parser/pest#1212
• Remove reqwest dependency from pest_debugger by @​tomtau with @​Copilot in pest-parser/pest#1209

New Contributors

• @​breken-ai made their first contribution in pest-parser/pest#1211

Full Changelog: pest-parser/pest@v2.9.2...v2.9.3

Warning: Semantic Versioning

Note that the node tag feature in 2.6.0 was a technically semver-breaking change even though it is a backwards-compatible / non-breaking change in the meta-grammar. There may be similar non-breaking changes to the meta-grammar between minor versions in the future. These non-breaking changes, however, may translate into semver-breaking changes due to the additional variants propagated from the generated Rule enum.

This new feature caused issues in some Cargo version resolution situations where Cargo mixed different versions of pest dependencies. For this reason, these "grammar non-breaking but semver-breaking" changes are now available only under the "grammar-extras" feature flag. If you would like to use node tags (or other future grammar features), you can do so by enabling this flag on the pest_derive crate in your Cargo.toml:

...
pest_derive = { version = "2.9", features = ["grammar-extras"] }

Commits

• 66a059c Fix typos in the three-string fast path of skip_until (#1231)
• b4882ad validator: reject repetitions that loop because of the stack (#1227) (fixes 1...
• 7e779b7 add Cargo.lock for reproducible builds (fixes #1161) (#1230)
• 4248cbd bump version to 2.9.3 (#1228)
• 429e893 Limit parse depth (#1212)
• 3cdface Detect left recursion behind a prefix that can match empty (fixes #411) (#1211)
• 9124917 Add AI contribution and usage policy (#1221)
• 9abf9e5 bump syn to 3 (#1210)
• acf7fd9 Remove reqwest dependency from pest_debugger (#1209)
• c32c2da Remove workflow-wide actions write permission (#1208)
• See full diff in compare view

Updates serde_json from 1.0.151 to 1.0.154

Release notes

Sourced from serde_json's releases.

v1.0.154

• Support preserve_order in no_std builds (#1333, thanks @​razmser)

v1.0.153

• Report invalid UTF-8 at the first bad byte (#1345, thanks @​00200200)

v1.0.152

• Preserve sign of -0 in arbitrary_precision mode (#1346, thanks @​yuxi-liu-wired)
• Fix comparison of large non-integer values with f32::INFINITY (#1347, thanks @​yuxi-liu-wired)

Commits

• 20572a6 Release 1.0.154
• a91bfaf Fix RandomState links in map documentation
• 3c932c0 Merge pull request #1333 from razmser/no-std-preserve-order
• 4b2d726 Release 1.0.153
• 83335ee Touch up PR 1345
• 4b4810a Resolve range_plus_one pedantic clippy lint
• 8af71cc Merge pull request #1345 from 00200200/fix-invalid-utf8-error-column
• 452afa2 Correct multiline raw UTF-8 error positions and simplify indexing
• c9f1e3b Release 1.0.152
• 854fc70 Touch up PR 1347
• Additional commits viewable in compare view

Updates sqlparser from 0.62.0 to 0.63.0

Commits

• 85b1a6f chore: Bump version to 0.63.0 and add changelog (#2481)
• dc8f0c4 Update sqlparser_derive to syn 3.0 (#2483)
• 16cd393 Visit function clauses in source order (#2477)
• eb61422 Databricks: enable query and nested type syntax (#2478)
• bd0f36f Parse expression-valued LIKE ESCAPE clauses (#2476)
• 5c974dd Add recursion checks for parse_data_type (#2411)
• f68211b Parse PostgreSQL MERGE DO NOTHING actions (#2468)
• 66bc6b3 Apply recursion limit without std (#2465)
• cbade61 Visit CreateView name as a relation (#2442)
• 0821cbd Preserve numeric compound field access display (#2463)
• Additional commits viewable in compare view

Updates proptest from 1.11.0 to 1.12.0

Commits

• 70cf37d Merge pull request #675 from proptest-rs/prep-1.12
• 729e0ff prepare next releases and fix panic handling
• 28c1fad Merge pull request #664 from Expyron/main
• 5ddd9a4 Merge pull request #668 from toddATavail/fix-fork-persisted-failure
• a6a9ac7 Merge pull request #673 from glaziermag/fix-book-deploy
• d57d88b Replace rand_chacha with chacha20
• 9411213 Deploy the book on pushes to main
• 1719745 fix: terminate the fork replay when a persisted failure fails
• 0f55b7a test: a persisted failure in a forked test must be reported
• 4b0594e Merge pull request #669 from proptest-rs/no-fail-fast
• Additional commits viewable in compare view

Updates rstest from 0.26.1 to 0.27.0

Release notes

Sourced from rstest's releases.

v0.27.0

[0.27.0] 2026/9/6

Changed

• Bump msrv to 1.85.0 both for rstest and rstest_reuse
• Disabled default features of futures-util

Added

• Doc comments before #[values(...)] entries can be used to override the generated matrix test names (both for the legacy arg => [..] syntax and the new attribute form). See #321 thanks to @​orhun.

Fixed

• Use fully-qualified core import. See #336.
• Fix mut arguments failing to compile with #[trace]. See #345 thanks to @​super-cooper.
• Fix compilation under bazel by upgrading proc-macro-crate to 3.4.0.

Changelog

Sourced from rstest's changelog.

[0.27.0] 2026/9/6

Changed

• Bump msrv to 1.85.0 both for rstest and rstest_reuse
• Disabled default features of futures-util

Added

• Doc comments before #[values(...)] entries can be used to override the generated matrix test names (both for the legacy arg => [..] syntax and the new attribute form). See #321 thanks to @​orhun.

Fixed

• Use fully-qualified core import. See #336.
• Fix mut arguments failing to compile with #[trace]. See #345 thanks to @​super-cooper.
• Fix compilation under bazel by upgrading proc-macro-crate to 3.4.0.

Commits

• 59cd3d1 Release 0.27.0
• 0821ebc test: Add E2E test for mut arguments with #[trace]
• 509ffef fix: mut arguments with #[trace]
• 043437d fix: Resolve clippy warnings and truncate long test project names
• 9aa8d1a fix: Suppress nightly cargo lints in test scaffolding
• 3d3c76c fix: Bump rstest_test MSRV to 1.85 and mark as unpublished
• d9ae990 chore: Add changelog entry
• 05d4b1a fix: Use fully-qualified core import
• 6da56a1 Bump msrv to 1.85 also for rstest_reuse (#342)
• 1e9963b Add CLAUDE.md for Claude Code guidance (#340)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions