chore(deps): bump maxminddb from 0.27.3 to 0.28.1

[dependabot]

Bumps maxminddb from 0.27.3 to 0.28.1.

Release notes

Sourced from maxminddb's releases.

0.28.1

• Fixed: Databases with an impossible declared search tree size are now rejected during open/verify instead of causing runaway allocation during validation.
• Fixed: within() now rejects IPv6 CIDRs on IPv4-only databases instead of yielding unrelated networks.
• Fixed: Verification now rejects truncated scalar/string payloads instead of skipping past them and reporting the database as valid.
• Fixed: LookupResult::network() now uses the reader's measured IPv4 subtree depth instead of assuming it always begins at bit 96.

0.28.0

• Performance improvement: Faster search-tree traversal by dispatching on the database's record size to monomorphized node readers, replacing per-step branching on the record size.
• Performance improvement: Direct deserialization of scalars, sequences, maps, and structs through dedicated fast paths instead of routing through deserialize_any.
• Performance improvement: IPv4 and IPv6 lookups dispatch to dedicated paths, avoiding per-call address-kind checks on the hot path.
• Behavior change: Deserializing a database array into a tuple or tuple struct now returns a decoding error when the lengths do not match. Previously the mismatch was silently ignored.
• Fixed: A corrupt data pointer that would underflow during resolution now returns an InvalidDatabase error instead of panicking.

Changelog

Sourced from maxminddb's changelog.

0.28.1 - 2026-04-26

• Fixed: Databases with an impossible declared search tree size are now rejected during open/verify instead of causing runaway allocation during validation.
• Fixed: within() now rejects IPv6 CIDRs on IPv4-only databases instead of yielding unrelated networks.
• Fixed: Verification now rejects truncated scalar/string payloads instead of skipping past them and reporting the database as valid.
• Fixed: LookupResult::network() now uses the reader's measured IPv4 subtree depth instead of assuming it always begins at bit 96.

0.28.0 - 2026-04-25

• Performance improvement: Faster search-tree traversal by dispatching on the database's record size to monomorphized node readers, replacing per-step branching on the record size.
• Performance improvement: Direct deserialization of scalars, sequences, maps, and structs through dedicated fast paths instead of routing through deserialize_any.
• Performance improvement: IPv4 and IPv6 lookups dispatch to dedicated paths, avoiding per-call address-kind checks on the hot path.
• Behavior change: Deserializing a database array into a tuple or tuple struct now returns a decoding error when the lengths do not match. Previously the mismatch was silently ignored.
• Fixed: A corrupt data pointer that would underflow during resolution now returns an InvalidDatabase error instead of panicking.

Commits

• 8e86128 Prepare v0.28.1 release
• e762e0c Set release date
• b730a7c Merge pull request #113 from oschwald/greg/fixes
• 3ce5264 Use actual IPv4 subtree depth for network
• 6ce0c23 Tighten decoder verification bounds
• 536242a Reject IPv6 CIDRs in within() with IPv4 trees
• 6a74e9a Improve test coverage of bad-database handling
• 1cd81bb Validate search tree layout in reader
• df493e2 Update MaxMind-DB fixtures
• 429baa5 Prepare v0.28.0 release
• Additional commits viewable in compare view

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e5245b4cc8

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6ebe631278

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-06T20:35:49.719925Z	1f4f4d0	New commits
🔒 Security Review	✅ Completed 2026-10-06T20:36:41.090914Z	1f4f4d0	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f9e865f296

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Update the actual maxminddb dependency

This change only rewires unrelated itertools dependency edges and does not perform the advertised upgrade: Cargo.toml:461 still constrains maxminddb to the incompatible 0.27.x range, while Cargo.lock:7224-7225 still resolves it to 0.27.3. Consequently, builds using the GeoIP/MMDB features receive none of the correctness and malformed-database validation fixes from 0.28.1; update the manifest requirement and regenerate the lockfile so the maxminddb package entry itself resolves to 0.28.1.

Useful? React with 👍 / 👎.