Add support for quick-xml 0.38 and update CI to Rust 1.85

[Copilot]

• Understand the issue with quick-xml 0.38 whitespace handling
• Create custom deserializers to trim whitespace from numeric and string fields
• Update the Bmap struct to use the custom deserializers
• Test with quick-xml 0.37 to ensure backward compatibility
• Test with quick-xml 0.38 to ensure the fix works
• Verify all tests pass with both versions
• Run final security check with CodeQL
• Update CI to use Rust 1.85 (Debian Trixie stable)
• Fix clippy and fmt errors for Rust 1.85

Summary

Successfully updated bmap-parser to support quick-xml 0.38 and updated CI to use Rust 1.85 to match Debian Trixie stable. Fixed all clippy and fmt errors introduced by Rust 1.85.

Changes:

• Added two custom deserializer functions in xml.rs to trim whitespace
• Applied deserializers to all numeric and string fields that have whitespace in XML
• Updated Cargo.toml to use quick-xml 0.38.0
• Updated CI workflow to use Rust 1.85 for all jobs (check, fmt, test, clippy)
• Fixed operator precedence warning in xml.rs
• Replaced deprecated as_slice() calls with slice syntax &[..]
• Fixed implied bounds in block_map() return type
• Added .truncate(true) to file open operations for clippy compliance

Testing:

• All tests pass with quick-xml 0.38.3 ✓
• All tests pass with quick-xml 0.37.5 (backward compatibility verified) ✓
• All tests pass with Rust 1.85.1 ✓
• cargo fmt passes ✓
• cargo clippy passes with -D warnings ✓
• No security vulnerabilities found ✓

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Support for quick-xml 0.38</issue_title>
<issue_description>Hi,

I'm currently investigating updating rust-quick-xml in Debian to 0.38, while we do have a mechanism for packaging multiple versions of a crate it is something we try to avoid where possible.

the tests for bmap-parser pass successfully with 0.37 but after bumping the dependency to 0.38 they fail with.

called Result::unwrap() on an Err value: XmlParsError(Custom("invalid type: string " 16777216 ", expected u64"))

Any help would be appreciated.</issue_description>

<agent_instructions>Please test with both quick-xml versions as mentioned in the ticket; </agent_instructions>

Comments on the Issue (you are @copilot in this section)

Fixes #91

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[sjoerdsimons]

@copilot Please update rust toolchain in the github workflows to the version in Debian stable and test compilation with that version specifically

[Copilot]

@copilot Please update rust toolchain in the github workflows to the version in Debian stable and test compilation with that version specifically

Could you clarify which Rust version is in Debian stable? I tested with Rust 1.63.0 (the original Bookworm release), but it fails due to dependency requirements:

• syn v2.0.107 requires rustc 1.68+
• native-tls v0.2.14 requires rustc 1.80+

The CI currently uses Rust 1.70, which works successfully. Should I:

1. Keep it at 1.70 if that's now in Debian stable (through backports/updates)?
2. Update to a different specific version?
3. Adjust dependencies to work with an older version?

Please let me know the target version and I'll update accordingly.

[sjoerdsimons]

@copilot Debian stable is Debian Trixie, which has rust 1.85; So please update to match that

[Copilot]

@copilot Debian stable is Debian Trixie, which has rust 1.85; So please update to match that

Updated the CI workflow to use Rust 1.85 to match Debian Trixie stable. All jobs (check, fmt, test, clippy) now use toolchain "1.85". Tested successfully with Rust 1.85.1 - all tests pass. (commit: see latest commit)

[sjoerdsimons]

@copilot the rustc version updates is cause cargo fmt and clippy errors; please resolve those. Overall make sure the github actions test can succeed

[Copilot]

@copilot the rustc version updates is cause cargo fmt and clippy errors; please resolve those. Overall make sure the github actions test can succeed

Fixed all clippy and fmt errors for Rust 1.85. Changes include:

• Fixed operator precedence in xml.rs
• Replaced deprecated as_slice() with slice syntax
• Fixed implied bounds in return type
• Added .truncate(true) to file operations
• Applied rustfmt formatting

All CI checks now pass: cargo check ✓, cargo fmt ✓, cargo test ✓, cargo clippy ✓ (commit: see latest)