Skip to content

v0.69.0

Choose a tag to compare

@hhff hhff released this 20 Nov 00:58
d666da9

What

  • The dashboard refuses owner actions that carry no browser header. A request to an owner-action route with neither Origin nor Sec-Fetch-Site gets 403. Before, a bare curl or fetch from any local program could act as the owner. Pages in a real browser work as before. A program that forges both headers still gets through, and the spec says so (kit-324 #433).
  • The gateway sends the instance's own Origin when it publishes and unpublishes (kit-324 #433).
  • A repo doc linked from an owner question is one working link. It opens on GitHub in a new tab, at the branch's sha when known. A ticket id inside a path, branch name or filename no longer splits it into a second link (kit-327 #434).
  • An artifact's manifest can say its kind: mock, diagram or docs. artifact new --kind sets it. The Library's Kind filter reads it, and older cache rows heal themselves (kit-319 #431).
  • New findings:
    • fleet-idle, when nothing has run for half an hour (#355);
    • findings for stalled PRs and overdue releases on maintained repo links (#405);
    • a validate warning when the unmerged ticket graph is mostly one serial chain (#353).
  • operator.md: an idle fleet is a check-in finding, with the moves to clear it (#356).
  • Two flaky tests are fixed (canvas cursors and thread replies; kit-326 #432), along with a Library poll test (kit-325 #430).

Why

  • Safety: an owner action now needs a browser, not just any local program.
  • Owner-reported bugs: the broken doc link.
  • Approved goals: a cleaner dashboard (artifact kinds), and self-improvement (the idle-fleet, PR-stall and serial-graph signals).
  • Upkeep: CI that stops failing on timing races.

Migration

This is a minor, and the box redeploys. The gateway must be at v0.69.0 before, or together with, the instances.

If an instance is on v0.69.0 behind an older gateway:

  • Publishing fails with 403 and nothing is published.
  • Unpublishing still takes the page down, but the instance doesn't record it. Use the Library's Forget to tidy up.

A script that posts to dashboard owner routes has to send the dashboard's own Origin. The kit itself has no such caller apart from the gateway, which this release fixes.

After adopting, validate may warn that the graph is mostly serial. That is a warning, not an error. Repos on upstream_sync "ask" get their usual process question, because operator.md changed.