Update Rust crate byteorder to 1.5.0

[renovate]

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.

---

This PR contains the following updates:

Package	Type	Update	Change
byteorder	dependencies	minor	1.2 -> 1.5.0

---

Release Notes

BurntSushi/byteorder (byteorder)

v1.5.0

Compare Source

v1.4.3

Compare Source

v1.4.2

Compare Source

v1.4.1

Compare Source

v1.4.0

Compare Source

v1.3.4

Compare Source

=====
This patch release squashes deprecation warnings for the try! macro, in
accordance with byteorder's minimum supported Rust version (currently at Rust
1.12.0).

v1.3.3

Compare Source

=====
This patch release adds ByteOrder::write_i8_into() as a simple, safe interface
for ordinarily unsafe or tedious code.

v1.3.2

Compare Source

=====
This patch release adds ReadBytesExt::read_i8_into() as a simple, safe interface
for ordinarily unsafe or tedious code.

v1.3.1

Compare Source

=====
This minor release performs mostly small internal changes. Going forward, these
are not going to be incorporated into the changelog.

v1.3.0

Compare Source

=====
This new minor release now enables i128 support automatically on Rust
compilers that support 128-bit integers. The i128 feature is now a no-op, but
continues to exist for backward compatibility purposes. The crate continues to
maintain compatibility with Rust 1.12.0.

This release also deprecates the ByteOrder trait methods
read_f32_into_unchecked and read_f64_into_unchecked in favor of
read_f32_into and read_f64_into. This was an oversight from the 1.2 release
where the corresponding methods on ReadBytesExt were deprecated.

quickcheck and rand were bumped to 0.8 and 0.6, respectively.

A few small documentation related bugs have been fixed.

v1.2.7

Compare Source

=====
This patch release excludes some CI files from the crate release and updates
the license field to use OR instead of /.

v1.2.6

Compare Source

=====
This patch release fixes some test compilation errors introduced by an
over-eager release of 1.2.5.

v1.2.5

Compare Source

=====
This patch release fixes some typos in the docs, adds doc tests to methods on
WriteByteExt and bumps the quickcheck dependency to 0.7.

v1.2.4

Compare Source

=====
This patch release adds support for 48-bit integers by adding the following
methods to the ByteOrder trait: read_u48, read_i48, write_u48 and
write_i48. Corresponding methods have been added to the ReadBytesExt and
WriteBytesExt traits as well.

v1.2.3

Compare Source

=====
This patch release removes the use of feature(i128_type) from byteorder,
since it has been stabilized. We leave byteorder's i128 feature in place
in order to continue supporting compilation on older versions of Rust.

v1.2.2

Compare Source

=====
This patch release only consists of internal improvements and refactorings.
Notably, this removes all uses of transmute and instead uses pointer casts.

v1.2.1

Compare Source

=====
This patch release removes more unnecessary uses of unsafe that
were overlooked in the prior 1.2.0 release. In particular, the
ReadBytesExt::read_{f32,f64}_into_checked methods have been deprecated and
replaced by more appropriately named read_{f32,f64}_into methods.

---

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• 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: native/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path native/src/rusqlite/Cargo.toml --workspace
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)