v1.1.2

What's Changed

Other

• ci: adopt the Happenv package standard by @webard in #3
• feat: translate the indicator into every language Filament ships by @webard in #4
• fix: share location and status once subscribed, and on request by @webard in #5
• fix: theme the tooltip like Filament's own by @webard in #6
• fix: centre the avatar strip on the page heading by @webard in #7

Full Changelog: v1.1.1...v1.1.2

v1.1.1

What's Changed

• fix: the page subheading returns below the heading instead of sitting next to it by @gorny-dev in #2

New Contributors

• @gorny-dev made their first contribution in #2

Full Changelog: v1.1.0...v1.1.1

v1.1.0

Stop the presence loop once the session has expired (#1)

The enter / heartbeat / leave routes sit behind the auth middleware. Once the session expired they answered 401 (guest) or 419 (stale CSRF token) with an HTML redirect body — over and over, because nothing stopped heartbeatTimer. A tab left open kept hitting the endpoint every heartbeat_interval until it was closed.

post() now checks the response status and ends the session on an authentication verdict: it stops the timer, leaves the channel, dispatches a filament-presence:session-expired event on window and, by default, reloads the tab — so it lands on the login screen instead of sitting on a page whose every request fails anyway.

A rejected fetch (a momentary network blip) deliberately does not end the session — it stays in .catch().

New configuration option

// config/filament-presence.php
'reload_on_session_expiry' => true, // default

Hosts that handle expiry themselves set it to false — the loop still stops and the event is still dispatched.

MINOR, not PATCH: this adds a configuration key, a new window event and a runtime behaviour change (the reload). It is backwards compatible; ^1.0 picks it up without changes.