Skip to content

Update server update required handling #6796

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

Merged
merged 1 commit into from
Apr 29, 2025

Conversation

thornbill
Copy link
Member

@thornbill thornbill commented Apr 22, 2025

Changes

  • Updates the handling of the server update required state

Issues
N/A

@thornbill thornbill added the cleanup Cleanup of legacy code or code smells label Apr 22, 2025
@thornbill thornbill added this to the v10.11.0 milestone Apr 22, 2025
@thornbill thornbill requested a review from a team as a code owner April 22, 2025 21:24
@jellyfin-bot
Copy link
Collaborator

jellyfin-bot commented Apr 22, 2025

Cloudflare Pages deployment

Latest commit 3b1ed1a
Status ✅ Deployed!
Preview URL https://f3080ca3.jellyfin-web.pages.dev
Type 🔀 Preview

View build logs

@thornbill thornbill force-pushed the update-server-page branch from c4ab3d8 to 3b1ed1a Compare April 27, 2025 07:13
@thornbill thornbill changed the title Add a dedicated server update required page Update server update required handling Apr 27, 2025
@thornbill
Copy link
Member Author

Ok I updated this to remove the dedicated route. Redirecting to/from the dedicated route when the connection state changed was overly complicated. Instead just rendering the error state in the current route context seems like a better approach.

A future PR will update handling for the Unavailable ConnectionState.

@thornbill thornbill merged commit 83bb102 into jellyfin:master Apr 29, 2025
15 checks passed
@thornbill thornbill deleted the update-server-page branch April 29, 2025 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup Cleanup of legacy code or code smells
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants