chore(release): archied v1.34.0
This commit is contained in:
4 files changed
+51
No files matched your search
@@ -1,5 +1,26 @@
|
||||
# archied changelog
|
||||
|
||||
## [1.34.0] - 2026-09-22
|
||||
|
||||
### Dashboard: an actionable authentication failure state
|
||||
|
||||
- An unauthenticated **document** request now receives a self-contained HTML page with a
|
||||
paste-the-token form, instead of plain text. Previously the whole dashboard -- `index.html`, the
|
||||
bundle and every asset -- sat behind the token check, so a bookmarked bare URL returned a
|
||||
`text/plain` "unauthorised: open the dashboard URL archied logged at startup", the SPA never ran,
|
||||
and none of the dashboard's existing failure surfaces were reachable at all.
|
||||
- The response is still **401**, with `Cache-Control: no-store` and a CSP. It is deliberately not a
|
||||
200: a login page served as success would be cacheable, would read as healthy to anything that
|
||||
checks status alone, and a shared cache could hand it to the wrong person.
|
||||
- API and stream callers are unaffected. `application/json`, `*/*` and `text/event-stream` requests
|
||||
keep the plain-text 401, with a test pinning that split so an XHR or an `EventSource` reconnect can
|
||||
never start receiving a page.
|
||||
- The auth banner gains a **Retry** action that re-runs the dashboard's bootstrap reads, so a
|
||||
recovered session is actionable without a browser-level reload. It deliberately does not re-drive
|
||||
the SSE stream, which already reports its own reconnect state.
|
||||
- The page's guidance stays generic: it points at the dashboard URL the daemon logs rather than
|
||||
naming where the token is stored, so the HTTP layer is not coupled to the token file's location.
|
||||
|
||||
## [1.33.0] - 2026-09-22
|
||||
|
||||
### EDA: playbook action arguments are compiled at load (J2)
|
||||
|
||||
@@ -0,0 +1,22 @@
|
||||
# archied 1.34.0
|
||||
|
||||
Released 2026-09-22. [All news](../index.md)
|
||||
|
||||
### Dashboard: an actionable authentication failure state
|
||||
|
||||
- An unauthenticated **document** request now receives a self-contained HTML page with a
|
||||
paste-the-token form, instead of plain text. Previously the whole dashboard -- `index.html`, the
|
||||
bundle and every asset -- sat behind the token check, so a bookmarked bare URL returned a
|
||||
`text/plain` "unauthorised: open the dashboard URL archied logged at startup", the SPA never ran,
|
||||
and none of the dashboard's existing failure surfaces were reachable at all.
|
||||
- The response is still **401**, with `Cache-Control: no-store` and a CSP. It is deliberately not a
|
||||
200: a login page served as success would be cacheable, would read as healthy to anything that
|
||||
checks status alone, and a shared cache could hand it to the wrong person.
|
||||
- API and stream callers are unaffected. `application/json`, `*/*` and `text/event-stream` requests
|
||||
keep the plain-text 401, with a test pinning that split so an XHR or an `EventSource` reconnect can
|
||||
never start receiving a page.
|
||||
- The auth banner gains a **Retry** action that re-runs the dashboard's bootstrap reads, so a
|
||||
recovered session is actionable without a browser-level reload. It deliberately does not re-drive
|
||||
the SSE stream, which already reports its own reconnect state.
|
||||
- The page's guidance stays generic: it points at the dashboard URL the daemon logs rather than
|
||||
naming where the token is stored, so the HTTP layer is not coupled to the token file's location.
|
||||
@@ -4,6 +4,7 @@ Release notes for archied and archie-agent, newest first.
|
||||
|
||||
## 2026-09-22
|
||||
|
||||
- [archied 1.34.0](archied/1.34.0.md)
|
||||
- [archied 1.33.0](archied/1.33.0.md)
|
||||
- [archied 1.32.1](archied/1.32.1.md)
|
||||
- [archied 1.32.0](archied/1.32.0.md)
|
||||
|
||||
@@ -1,4 +1,11 @@
|
||||
[
|
||||
{
|
||||
"component": "archied",
|
||||
"name": "archied",
|
||||
"version": "1.34.0",
|
||||
"date": "2026-09-22",
|
||||
"body": "### Dashboard: an actionable authentication failure state\n\n- An unauthenticated **document** request now receives a self-contained HTML page with a\n paste-the-token form, instead of plain text. Previously the whole dashboard -- `index.html`, the\n bundle and every asset -- sat behind the token check, so a bookmarked bare URL returned a\n `text/plain` \"unauthorised: open the dashboard URL archied logged at startup\", the SPA never ran,\n and none of the dashboard's existing failure surfaces were reachable at all.\n- The response is still **401**, with `Cache-Control: no-store` and a CSP. It is deliberately not a\n 200: a login page served as success would be cacheable, would read as healthy to anything that\n checks status alone, and a shared cache could hand it to the wrong person.\n- API and stream callers are unaffected. `application/json`, `*/*` and `text/event-stream` requests\n keep the plain-text 401, with a test pinning that split so an XHR or an `EventSource` reconnect can\n never start receiving a page.\n- The auth banner gains a **Retry** action that re-runs the dashboard's bootstrap reads, so a\n recovered session is actionable without a browser-level reload. It deliberately does not re-drive\n the SSE stream, which already reports its own reconnect state.\n- The page's guidance stays generic: it points at the dashboard URL the daemon logs rather than\n naming where the token is stored, so the HTTP layer is not coupled to the token file's location."
|
||||
},
|
||||
{
|
||||
"component": "archied",
|
||||
"name": "archied",
|
||||
|
||||
Reference in new issue
Block a user