Overview - Ghost

Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
29328
220221da Fixed sign-in redirect loop during Admin bootstrap ref https://linear.app/ghost/issue/PLA-188/ - unauthenticated Admin routes legitimately receive authorization failures while booting - keep session-expiry suppression without replacing a page that is already returning to sign-in
by Steve Larson
Succeeded
29328
061dae56 🐛 Fixed expired sessions returning forbidden responses ref https://linear.app/ghost/issue/PLA-188/ - Core returns 403 Authorization failed when an authenticated session expires - only that exact forbidden response should trigger the existing signin redirect
by Steve Larson
Succeeded
29328
061dae56 🐛 Fixed expired sessions returning forbidden responses ref https://linear.app/ghost/issue/PLA-188/ - Core returns 403 Authorization failed when an authenticated session expires - only that exact forbidden response should trigger the existing signin redirect
by Steve Larson
Succeeded
29328
948f268b 🐛 Fixed session expiry error classification ref https://linear.app/ghost/issue/PLA-188/ Only redirected Admin API 401s should be hidden; other unauthorized responses still need visible error feedback. Session URL query and fragment boundaries must also remain inside the authentication flow.
by Steve Larson
Succeeded
29328
e23dc21a 🐛 Fixed expired sessions leaving Admin stuck instead of returning to signin ref https://linear.app/ghost/issue/PLA-188/add-401-session-expiry-handling-to-the-admin-x-framework-fetch-layer - the React admin fetch layer had no 401 handling, so an expired session surfaced as a generic error toast and left the page dead - a 401 on an Admin API request (excluding the session endpoint, so failed signins are unaffected) now triggers a single full-page replace to the admin root - the same mechanism Ember's ajax service uses - which reboots Admin unauthenticated and lands on signin; this works for every framework consumer without depending on the Ember bridge - handleResponse was returned un-awaited, so response errors skipped the fetch layer's catch entirely; awaiting it also makes the documented MaintenanceError (503) retry reachable
by Steve Larson