Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update rust crate socketioxide to 0.14.0 #10

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 7, 2024

This PR contains the following updates:

Package Type Update Change
socketioxide dependencies minor 0.12.0 -> 0.14.0

Release Notes

totodore/socketioxide (socketioxide)

v0.14.1

Compare Source

What's Changed

New Contributors

Full Changelog: Totodore/socketioxide@v0.14.0...v0.14.1

v0.14.0

Compare Source

socketioxide

  • (Breaking): State reworked to avoid having unsafe global mutable state (issue #​317). Therefore State types must now implement Clone and will be cloned for each handler where the state is used.
  • (Breaking): Extensions reworked to avoid Send + Sync requirements on extensions (issue #​295). They are now extracted by Cloning. Therefore all the type must implement Clone. An Extension extractor is available to get an extension directly without calling socket.extensions.get().
  • feat: New HttpExtension types to extract extensions from the http request.
  • feat: SocketIo can now be used as an extractor. So you can now easily access the entire socket.io context from your handlers.
  • feat: Dynamic namespaces. You can know set dynamic namespaces with the dyn_ns function. You can specify patterns with the {name} syntax thanks to the matchit crate. The dynamic namespace will create a child namespace for any path that matches the given pattern with the given handler.

engineioxide

  • deps: bump tokio-tungstenite from 0.21.0 to 0.23.0.

v0.13.1

Compare Source

engineioxide

  • fix: issue #​320. Remove unnecessary panic when receiving unexpected websocket messages. This might happen with some specific socket.io clients.

v0.13.0

Compare Source

socketioxide

  • fix: issue #​311, the delete_ns fn was deadlocking the entire server when called from inside a disconnect_handler.
  • feat: the delete_ns is now gracefully closing the adapter as well as all its sockets before being removed.
  • feat: the API use Bytes rather than Vec<u8> to represent binary payloads. This allow to avoid unnecessary copies.
  • deps: use futures-util and futures-core rather than the whole futures crate.

engineioxide

  • feat: the API use Bytes/Str rather than Vec<u8> and String to represent payloads. This allow to avoid unnecessary copies.
  • deps: use futures-util and futures-core rather than the whole futures crate.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/socketioxide-0.x branch from 87c1e69 to a7fc7c8 Compare June 26, 2024 17:23
@renovate renovate bot changed the title fix(deps): update rust crate socketioxide to 0.13.0 fix(deps): update rust crate socketioxide to 0.14.0 Jun 26, 2024
@renovate renovate bot force-pushed the renovate/socketioxide-0.x branch from a7fc7c8 to 3f41b30 Compare August 15, 2024 23:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants