Trails v0.2.4

Release 0.2.4

Published the publishable @ontrails/* package set at 0.2.4 on the latest dist-tag.

Highlights

• Report a directory that disappears between listing and reading as vanished-directory instead of unreadable-directory in collectSourceTree. Permission and other read failures still report unreadable-directory. Static project identity discovery now rescans, up to three attempts, when a directory vanishes mid-walk. A removed directory, such as a parallel test's temp dir, drops out of the next listing, and a renamed one, including one holding a trails.config.* marker, is found under its new path. Churn that outlasts the retries still fails closed. Regrade also fails closed on both reasons, because a vanished directory may have been renamed and its sources would otherwise escape a prepared run or apply.
• Accept GitHub stacked-PR merge evidence for publish:auto. A merged changeset source PR now earns trusted source evidence when its REST resource carries a GitHub stack object and required CI passed on its head SHA or merge SHA, recorded as GitHub stack #N and required CI passed on <sha>. Graphite merge-queue evidence and the stack:boundary label work as before. Standalone PRs and any unreadable or unrecognized response still fail closed to publish:manual.
• Retry transient GitHub API failures in release policy reads. githubJson now retries 5xx responses and network errors up to four attempts with exponential backoff (1s, 2s, 4s) before failing, so an intermittent 500 from /commits/{sha}/pulls no longer fails the Release workflow's label-release-pr step. 4xx responses still fail immediately.

Changes

• b155fde: Report a directory that disappears between listing and reading as vanished-directory instead of unreadable-directory in collectSourceTree. Permission and other read failures still report unreadable-directory. Static project identity discovery now rescans, up to three attempts, when a directory vanishes mid-walk. A removed directory, such as a parallel test's temp dir, drops out of the next listing, and a renamed one, including one holding a trails.config.* marker, is found under its new path. Churn that outlasts the retries still fails closed. Regrade also fails closed on both reasons, because a vanished directory may have been renamed and its sources would otherwise escape a prepared run or apply. Packages: @ontrails/config, @ontrails/regrade, @ontrails/source
• cfeb154: Accept GitHub stacked-PR merge evidence for publish:auto. A merged changeset source PR now earns trusted source evidence when its REST resource carries a GitHub stack object and required CI passed on its head SHA or merge SHA, recorded as GitHub stack #N and required CI passed on <sha>. Graphite merge-queue evidence and the stack:boundary label work as before. Standalone PRs and any unreadable or unrecognized response still fail closed to publish:manual. Packages: @ontrails/trails
• 53ed05f: Retry transient GitHub API failures in release policy reads. githubJson now retries 5xx responses and network errors up to four attempts with exponential backoff (1s, 2s, 4s) before failing, so an intermittent 500 from /commits/{sha}/pulls no longer fails the Release workflow's label-release-pr step. 4xx responses still fail immediately. Packages: @ontrails/trails

Package Versions

• @ontrails/adapter-kit@0.2.4
• @ontrails/cli@0.2.4
• @ontrails/cloudflare@0.2.4
• @ontrails/commander@0.2.4
• @ontrails/config@0.2.4
• @ontrails/core@0.2.4
• @ontrails/drizzle@0.2.4
• @ontrails/hono@0.2.4
• @ontrails/http@0.2.4
• @ontrails/library@0.2.4
• @ontrails/logtape@0.2.4
• @ontrails/mcp@0.2.4
• @ontrails/observability@0.2.4
• @ontrails/permits@0.2.4
• @ontrails/pino@0.2.4
• @ontrails/regrade@0.2.4
• @ontrails/source@0.2.4
• @ontrails/store@0.2.4
• @ontrails/testing@0.2.4
• @ontrails/topography@0.2.4
• @ontrails/trails@0.2.4
• @ontrails/vite@0.2.4
• @ontrails/warden@0.2.4