Skip to content

v0.5.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 05 Oct 01:50
· 71 commits to main since this release
v0.5.1
362e6b3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Desk v0.5.1

Two fixes and no new capability. Desk stays on Runtime v0.26.0, Runner v0.5.0 and Gateway v0.9.0.

What changes for you

  • Research: an expectation no pack can produce is shown as the expectation's defect, not as something to repair in the draft. The runtime's sentence that names the rule is shown with it, and no repair round starts on it.
  • Nothing else visible. The other change is in how a release archive is built.

An unreachable expectation is the expectation's defect, not the candidate's (#207, closes #137)

The pinned runtime answers JPS-EXPECTATION-UNREACHABLE for an expectation no conforming pack can reach: an unresolved result retaining not-applicable, no-match beside any other reason, or an outcome id outside the identifier grammar. Desk read that row as an admitted §8.3 defect, worded it that way, and every caller presented it as something to repair in the candidate.

  • JPS-EXPECTATION-UNREACHABLE is its own case, apart from a §8.3 defect and a limit. The person reads: "This expectation names a disposition no pack can produce, so the expectation must change, not the draft:" followed by the runtime's message, which names the rule.
  • The issue list, the proposal check, the approval check and the reopened-draft recheck all present it as an expectation to change, and start no repair round on it. They already stopped before a repair round on any invalid finding; the change is the wording, and tests now hold each of them.
  • The fixture holds the runtime's live answers for the three unreachable shapes, byte for byte, from Runtime v0.26.0.

The Tests workspace still shows the runtime's bare message for an invalid expectation (#208).

Release archives retry a component download (#206, closes #203)

The release-archives job, and check-release.py at release time, fetch the published components with gh release download. The download failed intermittently, twice in about four runs, and the log held only Python's CalledProcessError without what gh had printed.

  • The download is retried, at most three attempts, with waits of 2 and 4 seconds. Before a retry the download directory is emptied, because gh refuses to overwrite a partial file.
  • The checksum check and gh attestation verify are never retried; they fail at once, as before.
  • Every command's standard error is kept. A failure names the command and repeats what gh said; a command that printed nothing says so.

Nothing in the app changes. The archives this release carries were fetched through the new code.

Component updates

None. Runtime v0.27.0 refuses a signing key kept in a directory anyone else could write or that another user owns; Desk does not pin it yet. Desk's own key custody (ADR-0010, in progress) places keys where that rule accepts them, and the pin moves with that work.

Existing job releases keep their frozen Runtime. State epoch remains 1.

Verification

CI ran frontend behaviour, all twelve locale catalogues, the Go chassis tests, the Jobs companion against the pinned Runner and Runtime, the local Gateway checks and the native archive builds.

  • Mutation checks: #207's six branches were each broken by hand and caught by a named test; their rows for scripts/mutation-check.sh follow in a change of their own. #206's eleven variants are in its pull request; the harness runs no Python rows.
  • Review: #206, which is not frontend, had one cross-vendor round, recorded on its pull request: no HIGH or MEDIUM, one LOW accepted without change. #207 is frontend and had the in-house checks.

Not exercised: the retry recovering from a real transient failure in CI, which only the stand-in gh showed.

See installation and updates and release verification.

Component Pin
Runtime v0.26.0
Runner and source worker v0.5.0
Gateway and required Desk adapters v0.9.0

Platforms

This release contains complete Linux/amd64, macOS Apple Silicon (arm64), and
macOS Intel (amd64) archives. All three archives were built and smoke-tested on
native GitHub-hosted runners before publication; neither macOS archive is merely
cross-compiled. Component versions come from the same release lock.

macOS executables are not Developer ID signed or notarized. Gatekeeper may block
downloaded executables; verify the release and checksums, then use Apple's
Privacy & Security → Open Anyway procedure
for the blocked executable. Native CI does not exercise these dialogs. The Codex
subscription subprocess bridge remains Linux-only.

No Windows archive is published. Windows execution is untested, and the managed
installer supports only Linux and macOS.

Assets 10
Loading