Update parry3d-f64 requirement from 0.25.0 to 0.26.1

[dependabot]

Updates the requirements on parry3d-f64 to permit the latest version.

Changelog

Sourced from parry3d-f64's changelog.

0.26.1

Added

• Added Bvh::traverse_indexed to traverse only a part of the subtree, and to retrieve the node’s indices (#416).

Fixed

• Fix Bvh::optimize_incremental being non-deterministic when restored from a serialized snapshot. The incremental optimization state is now stored on the Bvh itself (instead of the non-serializable BvhWorkspace) so it survives serialization/deserialization (#403).

0.26.0

Breaking changes

This release migrates parry from nalgebra to glam (via the glamx crate) for future compatibility with rust-gpu. This is a major breaking change affecting almost all public APIs.

Type renames

• Isometry → Pose (using glamx::Pose2/Pose3)
• Rotation → Rot2/Rot3 (using glamx::Rot2/Rot3)
• IsometryOps → PoseOps
• IsometryOpt → PoseOpt

Removed types

• Point<Real> - use Vector instead. Points and vectors are now unified.
• UnitVector<Real> - use Vector instead. Normalization is no longer encoded in the type.
• Translation<Real> - use Vector for translations.

Math type changes

• Vector is now glam::Vec2/Vec3/DVec2/DVec3 depending on dimension and precision features
• Matrix is now glam::Mat2/Mat3/DMat2/DMat3
• The math module now re-exports glam types and provides dimension-agnostic aliases

API signature changes

• Many functions that previously took &Point<Real> or &Vector<Real> now take Vector by value
• Functions taking &Isometry<Real> now take &Pose or Pose by value
• HalfSpace::new now takes Vector instead of Unit<Vector<Real>>
• Shape constructors like Segment::new, Triangle::new, Capsule::new now take Vector instead of Point
• Aabb::mins and Aabb::maxs are now Vector instead of Point<Real>

Migration guide

If your codebase currently relies on nalgebra, note that nalgebra and glamx provide type conversion. Enable the corresponding features:

... (truncated)

Commits

• See full diff 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)