feat(realtime): bump realtime from 2.4.3 to 2.5.1 #1149
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@silentworks Is there anything wrong with the PR? |
|
These are normally handled by dependabot automatically in order to get a good changelog. I closed this PR to see if dependabot would pick it up but I think because you opened the PR before dependabot got to run, it didn't bother creating the automated PR. |
silentworks
changed the title
silentworks
force-pushed
the
chore/bump-realtime
branch
from
0589f5a to
f5a6d0b
Compare
Pull Request Test Coverage Report for Build 15800727246Details
💛 - Coveralls |
silentworks
changed the title
silentworks
approved these changes
Jun 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Bump version of realtime
What is the current behavior?
Currently 2.5.x versions of realtime conflict with other libraries that use websockets library.
What is the new behavior?
No new behaviour
Additional context
Just bumping version, so that it does not conflict