Update bevy_replicon requirement from 0.33 to 0.34

[dependabot]

Updates the requirements on bevy_replicon to permit the latest version.

Release notes

Sourced from bevy_replicon's releases.

Bevy Replicon 0.34.0

Added

• Authorization system. By default we just verify compatibility between client and server, but it's customizable via RepliconSharedPlugin::auth_method.
• Configurable SendRate for deterministic replication. Use SendRate::Once to send only the initial value, or SendRate::Periodic to only sync the state periodically.
• AppRuleExt::replicate_with_priority to configure replication rule priority.
• DisconnectRequest event to queue a disconnection for a specific client on the server.
• ServerTriggerAppExt::make_trigger_independent.

Changed

• AppRuleExt::replicate_with now accepts IntoReplicationRule trait that allows to define rules with multiple components.
• Rename GroupReplication into BundleReplication.
• Rename ReplicatedClient into AuthorizedClient.
• Rename AppRuleExt::replicate_group into AppRuleExt::replicate_bundle.
• Rename replication_registry::despawn_recursive into replication_registry::despawn.
• Rename shared::event::trigger module into shared::event::remote_targets.
• Rename ServerEventAppExt::make_independent into ServerEventAppExt::make_event_independent. It never worked for triggers.
• ReplicationRule now stores Vec<ComponentRule> instead of Vec<(ComponentId, FnsId)>
• RuleFns now available from prelude.
• Initialize channels in App::finish instead of Startup. It's called automatically on App::run, but in tests you need to call App::finish manually.
• Rules created with the same priority now evaluated in their creation order.
• Component removals and insertions for an entity are now buffered and applied as bundles to avoid triggering observers without all components being inserted or removed. This also significantly improves performance by avoiding extra archetype moves and lookups.
• The Replicated component is no longer automatically inserted into non-replicated entities spawned from replicated components.
• Replace ServerEntityMap::get_by_* and ServerEntityMap::remove_by_* with an entry-based API. Use ServerEntityMap::server_entry or ServerEntityMap::client_entry instead.
• Split ReplicationChannel into ServerChannel and ClientChannel for clarity.
• Don't register an additional unreliable client channel for replication. While the server requires two channels, the client only needs one.
• Print error instead of panic on mapping overwrite in ServerEntityMap.
• Making trace logging level less verbose and more informative.

Removed

• WriteCtx::commands. You can now insert and remove components directly through DeferredEntity.
• RepliconClient::receive and RepliconServer::receive are now private since they should only be called internally by Replicon.
• ServerPlugin::replicate_after_connect. Use RepliconSharedPlugin::auth_method with AuthMethod::Custom instead.
• Deprecated methods.

Changelog

Sourced from bevy_replicon's changelog.

[0.34.0] - 2025-06-15

Added

• Authorization system. By default we just verify compatibility between client and server, but it's customizable via RepliconSharedPlugin::auth_method.
• Configurable SendRate for deterministic replication. Use SendRate::Once to send only the initial value, or SendRate::Periodic to only sync the state periodically.
• AppRuleExt::replicate_with_priority to configure replication rule priority.
• DisconnectRequest event to queue a disconnection for a specific client on the server.
• ServerTriggerAppExt::make_trigger_independent.

Changed

• AppRuleExt::replicate_with now accepts IntoReplicationRule trait that allows to define rules with multiple components.
• Rename GroupReplication into BundleReplication.
• Rename ReplicatedClient into AuthorizedClient.
• Rename AppRuleExt::replicate_group into AppRuleExt::replicate_bundle.
• Rename replication_registry::despawn_recursive into replication_registry::despawn.
• Rename shared::event::trigger module into shared::event::remote_targets.
• Rename ServerEventAppExt::make_independent into ServerEventAppExt::make_event_independent. It never worked for triggers.
• ReplicationRule now stores Vec<ComponentRule> instead of Vec<(ComponentId, FnsId)>
• RuleFns now available from prelude.
• Initialize channels in App::finish instead of Startup. It's called automatically on App::run, but in tests you need to call App::finish manually.
• Rules created with the same priority now evaluated in their creation order.
• Component removals and insertions for an entity are now buffered and applied as bundles to avoid triggering observers without all components being inserted or removed. This also significantly improves performance by avoiding extra archetype moves and lookups.
• The Replicated component is no longer automatically inserted into non-replicated entities spawned from replicated components.
• Replace ServerEntityMap::get_by_* and ServerEntityMap::remove_by_* with an entry-based API. Use ServerEntityMap::server_entry or ServerEntityMap::client_entry instead.
• Split ReplicationChannel into ServerChannel and ClientChannel for clarity.
• Don't register an additional unreliable client channel for replication. While the server requires two channels, the client only needs one.
• Print error instead of panic on mapping overwrite in ServerEntityMap.
• Making trace logging level less verbose and more informative.

Removed

• WriteCtx::commands. You can now insert and remove components directly through DeferredEntity.
• RepliconClient::receive and RepliconServer::receive are now private since they should only be called internally by Replicon.
• ServerPlugin::replicate_after_connect. Use RepliconSharedPlugin::auth_method with AuthMethod::Custom instead.
• Deprecated methods.

[0.33.0] - 2025-04-27

Changed

• Don't unwrap systems.

Added

• Support for no_std.
• Relationships networking. Use SyncRelatedAppExt::sync_related_entities<C> to ensure that entities related by C are replicated in sync.
• Seamless support for immutable components. For these components, replication is always applied via insertion.
• server_just_started run condition.

... (truncated)

Commits

• a899c5b Bump version to 0.34
• 14a587d Fix typo [skip ci]
• 0ccdbc5 Remove comment from write_entity
• 6bb3f66 Fix comment for apply_mutations
• 2f83bff Improve trace-level logging (#504)
• 531225d Log protocol hash
• 5e5e522 Use crate::prelude::*
• c6d2125 Fix link
• bbf82b6 Bump version to 0.14.0-rc.1
• f789ccc Bump crate-ci/typos from 1.32.0 to 1.33.1
• Additional commits viewable 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.