New release 0.22.0

[lance0]

Summary

Prepares a 0.22.0 release: bumps the crate version 0.21.0 → 0.22.0 and adds a CHANGELOG section for the changes already merged to main since 0.21.0. No code changes.

Why I'm opening this

I maintain rustbgpd, a Rust BGP daemon with an EVPN/VXLAN Linux dataplane that creates and reconciles netdevs — bridges, VXLANs, VRFs, L3VXLANs, VLAN sub-interfaces, and collect-metadata "single VXLAN device" setups with bridge VLAN→VNI tunnel mappings — through rtnetlink. That work depends on netlink-packet-route 0.31 types (e.g. the InfoVxlan::Df enum and the InfoIpTunnel::CollectMetadata change).

main already moved to netlink-packet-route 0.31.0 (ceb2aff), but the latest crates.io release (0.21.0) still pins 0.30. So adopting 0.31 today means a [patch.crates-io] git pin to an unreleased commit. A published 0.22.0 would let us — and any other downstream wanting 0.31 — drop the pin and take a normal version bump.

Totally your call

This is just the version + CHANGELOG legwork to make a release easy; please treat it as a nudge, not a request to merge as-is. If you'd rather close it and cut the release yourself, batch in other pending PRs first, or adjust the version number / changelog wording, that's completely fine. The crates.io publish is of course yours.

CHANGELOG entries are derived from git log v0.21.0..main (I left out the internal thiserror bump to match the existing convention). Verified locally: cargo build --all-targets and cargo fmt --check clean. Thanks for maintaining rtnetlink!

[gemini-code-assist]

Code Review

This pull request bumps the version of the rtnetlink crate from 0.21.0 to 0.22.0 in Cargo.toml and updates the CHANGELOG with the release notes for version 0.22.0. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.