chore: release

[github-actions]

🤖 New release

• atsamd-hal: 0.22.2 -> 0.23.0 (✓ API compatible changes)
• atsame54_xpro: 0.12.2 -> 0.12.3
• feather_m0: 0.19.2 -> 0.19.3
• feather_m4: 0.17.2 -> 0.17.3
• metro_m0: 0.19.2 -> 0.19.3
• metro_m4: 0.18.2 -> 0.18.3
• pygamer: 0.15.2 -> 0.15.3
• samd11_bare: 0.15.2 -> 0.15.3

Changelog

atsamd-hal

0.23.0 - 2025-08-13

Added

• (aes) Updates the cipher dependency.
• (aes) Updates the aes module:

Fixed

• [breaking] Re-add GCLK0 for CAN dependencies (#930)
• Clippy warning about null pointers in DMAC (#928)
• Remove GCLK from can::Dependencies (#919)

atsame54_xpro

0.12.3 - 2025-08-13

Other

• updated the following local packages: atsamd-hal

feather_m0

0.19.3 - 2025-08-13

Other

• updated the following local packages: atsamd-hal

feather_m4

0.17.3 - 2025-08-13

Other

• updated the following local packages: atsamd-hal

metro_m0

0.19.3 - 2025-08-13

Other

• updated the following local packages: atsamd-hal

metro_m4

0.18.3 - 2025-08-13

Other

• updated the following local packages: atsamd-hal

pygamer

0.15.3 - 2025-08-13

Other

• updated the following local packages: atsamd-hal

samd11_bare

0.15.3 - 2025-08-13

Other

• updated the following local packages: atsamd-hal

---

This PR was generated with release-plz.

[ianrrees]

The PR that triggered this bumped the version of cipher, which is publicly exported by the HAL, so I think this is actually a breaking change. Do we really need to cut a release after each update to master?

[ianrrees]

Hmm, another breaking change that wasn't detected. I wonder if this is happening because the changes are in feature-gated APIs?

[jbeaurivage]

Ohhh, I think you might be right about feature gating hiding the breaking changes from cargo-semver-checks. And no, we certainly don't have to make a release for every commit to master. I tried to release often to get the new stuff out to crates.io, but it's really not mandatory if we think it'll just bring churn more than anything else.