0.12.0 (#33)

* Misc improvements

* Update version

CHANGELOG.md

@@ -1,12 +1,12 @@
-# Unreleased
+# 0.12.0
 
 - Improved packet loss computation algorithm
   - Handle the edge case of PTO being too high and not having a sample to use
   - Added `TransportConfig::packet_lost_threshold_factor`
 - Made each crate have its own separate version
   - For now, all crates will share the same major and minor version number, but we are now free to bump the patch for individual subcrates
 - `aeronet_replicon` properly reports backend statistics to Replicon i.e. RTT, packet loss
-- Updated `bevy_replicon` to `0.30.0`
+- Updated `bevy_replicon` to `0.30.1`
 - Updated `wtransport` to `0.5.0`, `xwt-wtransport` and `xwt-web`
 - Made integer/usize casts in `aeronet_transport` more safe and explicit
   - Replace `LaneIndex(n)` with `LaneIndex::new(n)` (works in `const`)

Cargo.toml

@@ -140,4 +140,4 @@ xwt-web = "0.15.0"
 
 # aeronet_replicon
 
-bevy_replicon = { version = "0.30.0", default-features = false }
+bevy_replicon = { version = "0.30.1", default-features = false }

README.md

@@ -137,7 +137,6 @@ the top, add it and `aeronet` to your app, and start building!
 `aeronet` and its subcrates use a combination of:
 - unit tests, using `cargo`, for individual, self-contained features
 - integration tests, using `cargo`, for testing code in the context of a full Bevy app
-  - currently, only [`aeronet_channel`] has integration tests
 - fuzz tests, using [`cargo-fuzz`], for protocol-level features and parsing
   - used by [`aeronet_transport`]
 

crates/aeronet_io/src/lib.rs

@@ -63,12 +63,19 @@ pub struct SessionEndpoint;
 /// different protocols, such as raw UDP datagrams alongside Steam networking
 /// sockets, so that you can e.g. support crossplay between different platforms.
 ///
+/// # Interaction with IO layer implementation
+///
 /// The [`Session`] component is created by your chosen IO layer implementation,
 /// so you should not create it yourself. See your IO layer's documentation for
 /// how to spawn an entity with [`Session`]. There are also constraints on which
 /// fields of this component you can modify, and how. See each field's
 /// documentation for how you can use it.
 ///
+/// Each entity with a [`Session`] should only ever have a single IO layer
+/// implementation that drives it. **Adding multiple transports onto the same
+/// entity is not supported**, but you can always have multiple entities each
+/// with their own [`Session`] and their own transport.
+///
 /// # Lifecycle
 ///
 /// After creating a session entity using your chosen IO layer, the entity will

crates/aeronet_transport/Cargo.toml

@@ -57,7 +57,6 @@ document-features = [
   # - Compile error!
   #
   # To get around this, when generating docs, we manually enable the `x11` feature.
-  "dep:bevy_winit",
   "bevy_winit/x11",
 ]