Skip to content

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 23 Sep 18:19
· 259 commits to main since this release

Changed

  • Among siblings nobody numbered, folders now come before documents: in the
    sidebar, and on section pages. A landing document still opens its folder, and
    a number in a Drive name still places an item exactly where it was numbered.
    The first full sync after upgrading reorders the sidebar of any folder mixing
    unnumbered subfolders and documents. See
    ADR-019.
  • The Access preflight in project-deploy.yml runs beside the candidate
    verification instead of after it. It reads only the live hostname, and the
    deployment still waits for both.

Added

  • A section page tells folders from documents. Its frontmatter records each
    entry's kind, and for a folder, how many documents sit anywhere below it. The
    site draws a folder glyph and the count ("Empty" when there are none) for a
    folder, and a document glyph, the date its source was last edited and its
    description for a document. Each row's kind also reaches a screen reader as
    text. A page generated before this release keeps its plain list until the
    next full sync rewrites it.
  • project-deploy.yml takes candidate_verified. A caller deploying a commit
    project-sync.yml produced passes it as true with candidate_sha, and the
    candidate verification job, a second pnpm verify of the tree the sync job
    had just verified, is skipped. The input fails the run without a SHA. A
    project opts in by adding candidate_verified: true to the deployment job
    of its sync workflow; without it nothing changes.
  • The workflows cache the images Astro optimizes, in project-sync.yml,
    project-deploy.yml and project-ci.yml, keyed by the lockfile and the
    images under src/assets/. Encoding them was most of every build, and a sync
    that deploys builds the site three times.

Fixed

  • Dependencies are downloaded once per lockfile rather than in every job. The
    workflows cached the pnpm store through actions/setup-node, whose key
    names only the lockfile, and the dependency audit in project-ci.yml, which
    installs nothing, usually saved its near-empty store under that key first;
    every job after it restored that and fetched every package again. Each
    workflow now caches the store and pnpm's cache directory itself, under a key
    of its own, and the audit restores and saves nothing. Keeping the cache
    directory also keeps pnpm's record that the lockfile passed its supply-chain
    check. Entries under the old key are no longer read and expire on their own.