Skip to content

v0.38.2

Latest

Choose a tag to compare

@Helweg Helweg released this 26 Oct 08:58
· 6 commits to main since this release
Immutable release. Only release title and notes can be modified.
48b9f1a

Fixes

  • Repository-history sync: GitHub can return HTTP 422 / structured not_available for a PR's file diff, including PRs reporting zero changed files and zero commits. Manual sync now retains that PR and all fetched discussions, records files: [] with fileReferencesComplete: false, and continues syncing. Structured REST error codes are preserved from gh stdout with or without HTTP headers; raw private error bodies are never forwarded. Unrelated API failures, cancellation, and atomic publication checks remain intact.
  • Contributor watcher diagnostics (#469): Preserve failure-only capture expectations independently of snapshot writes, and report retained, retention-failed, expected-missing and unavailable-status diagnostics without replacing the original failure. This release does not reopen or attribute historical watcher failures.

Verification before publication

  • Synthetic-gh regressions failed before the fix and passed after it; all 88 history tests passed.
  • Built-CLI sync/search/status verified the persisted incomplete-file-reference result and retained discussions.
  • Full local build, typecheck, lint and test gate passed with --maxWorkers=1: 2,936 tests passed, 6 skipped. No tests excluded or timeouts changed. The initial default-worker run had one existing watcher timeout; its current-run log/capture was retained privately, with no watcher edits.
  • Package, lockfile and host plugin metadata are synchronized at 0.38.2. Node.js minimum remains 22.13.0; supported-version families are unchanged.
  • Exact-head PR checks passed before merge. Merged commit 48b9f1a33eb1783a6b0eaa06287b87ef48369372 passed push CI on Node 22/24, including packed-identity and Node 22.13.0 consumer checks, and CodeQL. Dependabot, code-scanning and secret-scanning open alert boards were empty again immediately before tagging.

Publication runs through the repository's trusted dual-package workflow. Registry, provenance and installed-runtime results will be recorded on the release PR after they have actually been exercised. The macOS ARM64 binding can be executed locally; other targets require build evidence, not a claim of local execution. Windows ARM64 remains best-effort under the existing runner policy.

Complete changelog · All changes since v0.38.1 · Release PR #472