test handle presence extension private presence with read permissions will be able to receive presence changes but won't be able to track (Realtime.Integration.RtChannelTest)

test handle refresh token messages on new access_token and channel is private policies are reevaluated (Realtime.Integration.RtChannelTest)

test sensitive information updates on other param changes the socket won't close and no message is sent (Realtime.Integration.RtChannelTest)

test sensitive information updates on jwt_secret the socket closes and sends a system message (Realtime.Integration.RtChannelTest)

test handle broadcast changes broadcast delete event changes on delete in table with trigger (Realtime.Integration.RtChannelTest)

test handle broadcast extension private broadcast with valid channel with permissions sends message (Realtime.Integration.RtChannelTest)

test handle presence extension public presence (Realtime.Integration.RtChannelTest)

test only private channels user with only private channels enabled will be able to join private channels (Realtime.Integration.RtChannelTest)

test handle refresh token messages on new access_token and channel is public policies are not reevaluated (Realtime.Integration.RtChannelTest)

test handle broadcast changes broadcast update event changes on update in table with trigger (Realtime.Integration.RtChannelTest)

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it

min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it

Nested modules could be aliased at the top of the invoking module.

Nested modules could be aliased at the top of the invoking module.

Nested modules could be aliased at the top of the invoking module.

Nested modules could be aliased at the top of the invoking module.

Nested modules could be aliased at the top of the invoking module.

Nested modules could be aliased at the top of the invoking module.

Nested modules could be aliased at the top of the invoking module.

Nested modules could be aliased at the top of the invoking module.

Nested modules could be aliased at the top of the invoking module.