chore(release): prepare for publishing

[devolutionsbot]

🤖 New release

• ironrdp-graphics: 0.6.0 -> 0.7.0 (⚠ API breaking changes)
• ironrdp-rdpdr: 0.4.1 -> 0.5.0 (✓ API compatible changes)
• ironrdp-rdpsnd-native: 0.4.1 -> 0.4.2 (✓ API compatible changes)
• ironrdp-server: 0.9.0 -> 0.9.1
• ironrdp-session: 0.7.0 -> 0.7.1
• ironrdp: 0.13.0 -> 0.13.1
• ironrdp-rdpdr-native: 0.4.0 -> 0.4.1

⚠ ironrdp-graphics breaking changes

--- failure enum_variant_added: enum variant added on exhaustive enum --- Description: A publicly-visible enum without #[non_exhaustive] has a new variant. ref: https://doc.rust-lang.org/cargo/reference/semver.html#enum-variant-new impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.44.0/src/lints/enum_variant_added.ron Failed in: variant RlgrError:InvalidIntegralConversion in /tmp/.tmpEVFoa8/IronRDP/crates/ironrdp-graphics/src/rlgr.rs:400 variant ZgfxError:InvalidIntegralConversion in /tmp/.tmpEVFoa8/IronRDP/crates/ironrdp-graphics/src/zgfx/mod.rs:448 

Changelog

ironrdp-graphics

[0.7.0] - 2025-11-05

Build

• Bump bytemuck from 1.23.2 to 1.24.0 (#1008) (a24a1fa9e8)

ironrdp-rdpdr

[0.5.0] - 2025-11-05

Bug Fixes

• Fix incorrect padding when parsing NDR strings (#1015) (a0a3e750c9)

  When parsing Network Data Representation (NDR) messages, we're supposed
  to account for padding at the end of strings to remain aligned on a
  4-byte boundary. The existing code doesn't seem to cover all cases, and
  the resulting misalignment causes misleading errors when processing the
  rest of the message.

Refactor

• [breaking] Enable unwrap_used clippy correctness lint (#965) (630525deae)

ironrdp-rdpsnd-native

[0.4.2] - 2025-11-05

Build

• Bump bytemuck from 1.23.2 to 1.24.0 (#1008) (a24a1fa9e8)

---

This PR was generated with release-plz.