Skip to content

release: 0.5.77 - #1620

Open
its-miso[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--dispatch
Open

its-miso[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--dispatch

Conversation

@its-miso

@its-miso its-miso Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.5.77 (2026-11-22)

Features

  • deps: update dependency @testing-library/jest-dom (7.0.1 → 8.0.0) (#1663) (e5bbfa7)
  • deps: update dependency eslint (10.14.0 → 10.15.0) (#1632) (4620f4d)
  • deps: update dependency lucide-react (1.72.0 → 1.73.0) (#1633) (3489ff7)
  • deps: update dependency lucide-react (1.73.0 → 1.74.0) (#1650) (b2c7244)
  • deps: update dependency lucide-react (1.74.0 → 1.75.0) (#1658) (55b292d)
  • deps: update dependency lucide-react (1.75.0 → 1.76.0) (#1664) (a158db8)
  • deps: update dependency lucide-react (1.76.0 → 1.77.0) (#1669) (73321f8)
  • external-work: add contribution interface (#1688) (434723e)
  • external-work: track Courier lifecycle via the read-only status API (#1538) (#1685) (6c1742b)
  • pr-fix: /dispatch-fix PR comment command — per-PR operator handoff of human-authored PRs (#1622) (#1634) (81ff10f)
  • scope automatic PR follow-up for shared automation identities (#1665) (#1683) (b545a60)

Bug Fixes

  • courier-admission: settle response-body read failures as uncertain delivery (#1627) (#1629) (45f6e7c)
  • deps: floor effect at 3.22.1 to clear the npm audit gate; enforce lint --max-warnings=0 (#1672) (7805b1f)
  • deps: scope the effect override to @prisma/config and cap Renovate at 3.x (#1686) (48df22f)
  • deps: update dependency @testing-library/user-event (14.6.10 → 14.6.12) (#1643) (5b893aa)
  • deps: update dependency @testing-library/user-event (14.6.12 → 14.6.13) (#1662) (c26a787)
  • deps: update dependency @testing-library/user-event (14.6.9 → 14.6.10) (#1619) (8b28369)
  • deps: update dependency astro (7.4.11 → 7.4.12) (#1631) (cd3e1af)
  • deps: update dependency astro (7.4.12 → 7.4.13) (#1661) (72d663a)
  • deps: update dependency jsdom (31.0.0 → 31.0.1) (#1626) (ece7e2b)
  • deps: update dependency tailwind-merge (3.7.0 → 3.7.1) (#1666) (1af494d)
  • deps: update vitest monorepo (5.1.0 → 5.1.1) (#1659) (a45b2cb)
  • external-contributions: keep a live final attempt in_flight (#1628) (#1630) (86a56c7)
  • pr-fix-queue: prove deleted PR absence past listing read bound (#1648) (#1649) (6261f1e)
  • pr-fix-queue: queue-wide head-repository eligibility (#1638) (#1640) (38090c1)
  • pr-fix-queue: reap queue rows whose PR was deleted — per-PR existence probe (#1641) (#1642) (0b1c786)
  • pr-fix-queue: run the deleted-PR reap with no tracked repositories (#1651) (#1652) (d4d5c88)
  • pr-fix: keep an older CHANGES_REQUESTED standing when a re-review is dismissed (#1636) (#1647) (2933b61)
  • pr-fix: ship the original claimant inline on followup-pr hand-outs (#1582) (#1679) (a86967a)
  • pr-followup: verify the PR head repo against the base repo before queueing fix work (#1637) (#1639) (fffb64d)
  • site-audit: time-boxed exception for the picomatch advisory GHSA-fc5q-39xc-vjpf (#1654) (308f58f)
  • sync: reconcile cached agent labels against GitHub so stale labels stop poisoning claimants (#1625) (548b540)

Chores

Refactors

  • consolidate duplicated shaping helpers into their owning modules (#1646) (1ad9e30)
  • consolidate excluded-label where composition into applyExcludedLabelExclusion (#1624) (a42889d)
  • share the duplicated JSON helpers from src/lib/json.ts (#1668) (788d01b)

This PR was generated with Release Please. See documentation.

its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch 5 times, most recently from 682e025 to 68d12da Compare November 13, 2026 14:49
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from 68d12da to e922d56 Compare November 13, 2026 22:02
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from e922d56 to f7b15f1 Compare November 13, 2026 22:32
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from f7b15f1 to a0edbdb Compare November 14, 2026 19:31
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from a0edbdb to 499ba3f Compare November 16, 2026 06:26
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch 2 times, most recently from 139f62a to c62465e Compare November 16, 2026 17:09
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch 2 times, most recently from b3a519f to ca960aa Compare November 16, 2026 17:51
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from 35aaac8 to 25ea608 Compare November 18, 2026 12:25
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from 25ea608 to 1f6b453 Compare November 18, 2026 15:33
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from 1f6b453 to 8a6be1b Compare November 18, 2026 22:33
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch 2 times, most recently from 4479d07 to 56b21c3 Compare November 19, 2026 15:17
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from 56b21c3 to 23c8a69 Compare November 19, 2026 15:55
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from 23c8a69 to 39094d0 Compare November 20, 2026 20:46
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from 39094d0 to ebe8d0f Compare November 20, 2026 21:47
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from ebe8d0f to 0545bd0 Compare November 20, 2026 22:16
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from 0545bd0 to 4163b4e Compare November 20, 2026 22:28
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch 3 times, most recently from 73c186f to d51c947 Compare November 21, 2026 02:26
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from d51c947 to b86b42a Compare November 21, 2026 02:42
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from b86b42a to e79159d Compare November 21, 2026 03:04
its-saffron[bot]

This comment was marked as outdated.

@its-miso
its-miso Bot force-pushed the release-please--branches--main--components--dispatch branch from e79159d to 216fa74 Compare November 22, 2026 03:41

@its-saffron its-saffron Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

{"schema":"review-handoff/v1","review_id":"ea8afdb286dc3d43","head_sha":"216fa74b2170b1ee6e93e895e49d6f4985bcae98","verdict":"approve","review_result":"partial","required_checks":"incomplete","items":[{"id":"5c9272070a600954f76e801ef92fc831ae332ecd18328ca7be91e0a392516c14","severity":"info","category":"other","path":"CHANGELOG.md","line":42,"message":"The 0.5.77 notes still advertise the time-boxed picomatch exception GHSA-fc5q-39xc-vjpf, so the previously raised cleanup of the accepted-risk entry stays outstanding pending confirmation that the advisory was withdrawn upstream. (review thread PRRT_kwDOSZt6uM66Q9tK: open)"},{"id":"8f0291824d81e0d2f8f3919784e24c2b87cbc5f4dfaa2dfe16d242eaecfef005","severity":"info","category":"other","path":"CHANGELOG.md","line":42,"message":"The release notes still advertise the time-boxed picomatch exception GHSA-fc5q-39xc-vjpf, and `SECURITY-ACCEPTED-RISKS.md:23-29` still lists it as an active exception expiring 2027-02-17, so the previously raised cleanup of the withdrawn advisory is still outstanding (upstream withdrawal could not be re-verified in this run). (review thread PRRT_kwDOSZt6uM66QvGA: open)"},{"id":"461df4c8d3d1ccf8925c6a565639e7883d381124859304c4903df781e49f3171","severity":"info","category":"other","path":"CHANGELOG.md","line":42,"message":"The changelog still advertises the time-boxed picomatch exception for GHSA-fc5q-39xc-vjpf, but that advisory was withdrawn upstream on 2026-11-18, so the admitted exception in `scripts/site-npm-audit.mjs` and `SECURITY-ACCEPTED-RISKS.md` (expires 2027-02-17) now describes a withdrawn advisory and should be retired. (review thread PRRT_kwDOSZt6uM66M78v: open)"},{"id":"9151152bfd3c5624f3f60349a4a2f8c4c7befd7fa9e6f888fcf2fcf5fcacadae","severity":"info","category":"other","path":"CHANGELOG.md","line":49,"message":"The release notes still advertise the time-boxed picomatch advisory exception, so the stale withdrawn-advisory cleanup raised in the review thread remains outstanding. (review thread PRRT_kwDOSZt6uM66Mnrf: open)"},{"id":"0ba55da5e93c30e95dab98e1d55ed5e368db135e7e2f531c458e3bfa3fc58334","severity":"info","category":"other","path":"CHANGELOG.md","line":42,"message":"The changelog records the picomatch advisory GHSA-fc5q-39xc-vjpf as an open accepted risk, but GitHub withdrew that advisory on 2026-11-18, so `SECURITY-ACCEPTED-RISKS.md` and the admitted-exception entry in `scripts/site-npm-audit.mjs` (expires 2027-02-17) now describe a withdrawn advisory and should be retired. (review thread PRRT_kwDOSZt6uM66MFL2: open)"},{"id":"6b90d9a2c4b3b51bd87b58d1bc1f74f43e35b84d1a85546ab4fddac201c3bcf3","severity":"info","category":"other","path":"CHANGELOG.md","line":49,"message":"The changelog records a time-boxed exception for picomatch advisory GHSA-fc5q-39xc-vjpf, but that advisory is now marked withdrawn upstream, so the exception text may be stale. (review thread PRRT_kwDOSZt6uM65kLQB: open)"}],"items_total":6,"items_truncated":false,"unresolved_requirement_ids":[],"unresolved_requirement_ids_total":0,"unresolved_requirement_ids_truncated":false,"unresolved_requirement_ids_source_total":0,"unresolved_required_checks":["establish upstream provenance for the updated dependency: publis","inspect the exact old→new upstream release delta for the updated","check upstream security advisories for the updated dependency ve"],"unresolved_required_checks_total":3,"unresolved_required_checks_truncated":false,"unresolved_required_checks_source_total":3,"unresolved_review_obligations":[],"unresolved_review_obligations_total":0,"unresolved_review_obligations_truncated":false,"derived_obligation_state":null}

AI Automated Review

🟡 Automated recommendation: INCOMPLETE — no blocking code defect proven; approval withheld (a mandatory requirement remains unresolved)

Full PR review.

Analysis engine: MiniMax-M3.1-Flash (anthropic) — primary route · pr-reviewer-action v3.10.0

Partial coverage: required-check coverage is incomplete — this review did not resolve every required check and must not be read as a complete pass.

Findings (6 info)

Severity Location Finding
Info CHANGELOG.md:42 The 0.5.77 notes still advertise the time-boxed picomatch exception GHSA-fc5q-39xc-vjpf, so the previously raised cleanup of the accepted-risk entry stays outstanding pending confirmation that the advisory was withdrawn upstream. (review thread PRRT_kwDOSZt6uM66Q9tK: open)
Info CHANGELOG.md:42 The release notes still advertise the time-boxed picomatch exception GHSA-fc5q-39xc-vjpf, and `SECURITY-ACCEPTED-RISKS.md:23-29` still lists it as an active exception expiring 2027-02-17, so the previously raised cleanup of the withdrawn advisory is still outstanding (upstream withdrawal could not b
Info CHANGELOG.md:42 The changelog still advertises the time-boxed picomatch exception for GHSA-fc5q-39xc-vjpf, but that advisory was withdrawn upstream on 2026-11-18, so the admitted exception in `scripts/site-npm-audit.mjs` and `SECURITY-ACCEPTED-RISKS.md` (expires 2027-02-17) now describes a withdrawn advisory and sh
Info CHANGELOG.md:49 The release notes still advertise the time-boxed picomatch advisory exception, so the stale withdrawn-advisory cleanup raised in the review thread remains outstanding. (review thread PRRT_kwDOSZt6uM66Mnrf: open)
Info CHANGELOG.md:42 The changelog records the picomatch advisory GHSA-fc5q-39xc-vjpf as an open accepted risk, but GitHub withdrew that advisory on 2026-11-18, so `SECURITY-ACCEPTED-RISKS.md` and the admitted-exception entry in `scripts/site-npm-audit.mjs` (expires 2027-02-17) now describe a withdrawn advisory and shou
Info CHANGELOG.md:49 The changelog records a time-boxed exception for picomatch advisory GHSA-fc5q-39xc-vjpf, but that advisory is now marked withdrawn upstream, so the exception text may be stale. (review thread PRRT_kwDOSZt6uM65kLQB: open)

Recommendation: Incomplete — no blocking code defect proven; approval withheld (a mandatory requirement remains unresolved). (Model suggestion before validation, not authoritative: approve — release-please 0.5.77 version/changelog bump; no blocking or major findings.)

  • Breaking changes: jest-dom 8.0.0's only breaking change (dropped support for vitest <5) is satisfied — the repo resolves vitest 5.1.1 against vitest: ^5.0.0 (call-25); eslint 10.15.0 and the remaining bumps carry no breaking changes (calls 3, 4, 6, 7, 8, 11, 14, 38). tailwind-merge 3.7.1 changes class-merge behavior (a font-size class no longer drops an earlier leading-*) — cosmetic, no API break (call-38).
  • Test suite: head 216fa74 has green Tests, Coverage, Lint, Typecheck, npm audit and npm audit (site/) runs (calls 23, 24).
  • Provenance: canonical publishers/repos confirmed per bumped package — testing-library (jest-dom, user-event), eslint/eslint, lucide-icons/lucide, withastro/astro, jsdom/jsdom, dcastil/tailwind-merge, vitest-dev/vitest, Effect-TS/effect (calls 3, 4, 6, 7, 8, 11, 14, 38).
  • Release delta: upstream release notes read for each new resolved version (calls 3, 4, 6, 7, 8, 11, 14, 38); intermediate lockfile-only bumps are covered by the changelog entries.
  • Advisories: GitHub advisory API queried per new version with no match (calls 12, 13, 37, 39); the effect advisory GHSA-7589-6fvf-x4pw (≤3.22.0) is remediated — the lockfile resolves effect 3.22.5 (call-26).

Claims: Claim 1 held — CHANGELOG.md:15-16 carry the external-work entries. Claims 2–5 unverified: the Courier / pr-fix / shared-identity code is not in this diff and the tool budget was exhausted before those call sites could be read.

Tool Harness Findings: 40 calls executed; upstream release notes and advisory lookups succeeded for jest-dom, eslint, lucide-react, astro, user-event, vitest, jsdom, tailwind-merge and effect; the jsdom and tailwind-merge tag endpoints 404'd and were recovered via list endpoints (calls 14, 38); the budget ended before SECURITY-ACCEPTED-RISKS.md and the Courier/pr-fix implementations could be read.

Unknowns or Needs Verification:

  • Upstream withdrawal of picomatch GHSA-fc5q-39xc-vjpf was not re-verified in this run; the 0.5.77 notes still advertise the time-boxed exception (CHANGELOG.md:42).
  • The resolved minimatch version was not read; GHSA-g3hv-75wg-m249 (CVE-2026-118764) covers minimatch >=7.0.0 <11.0.1 — dev-scoped, and the prod-only audit gate is green.

Unaddressed required checks

The classifier marked these checks as required for this PR's risk profile, but the review does not establish clean coverage for them (unresolved, or dispositioned unmet — performed and failed):

  • establish upstream provenance for the updated dependency: publisher and canonical source repository
  • inspect the exact old→new upstream release delta for the updated dependency
  • check upstream security advisories for the updated dependency version range, or report the advisory check as not performed

Unresolved Required Review Evidence

Required-evidence coverage is incomplete: the review could not gather the required evidence above, so no defect is claimed here (an unresolved required check is a coverage marker, not a finding). The review is partial and trusted approval is withheld until the evidence is gathered.

- obligation-3 (must_check, unresolved, cause: budget-exhausted): establish upstream provenance for the updated dependency: publisher and canonical source repository
- obligation-4 (must_check, unresolved, cause: budget-exhausted): inspect the exact old→new upstream release delta for the updated dependency
- obligation-5 (must_check, unresolved, cause: budget-exhausted): check upstream security advisories for the updated dependency version range, or report the advisory check as not performed

required review evidence unresolved: obligation-3, obligation-4, obligation-5 (review-owned required check not discharged; review partial, trusted approval withheld; PR 1381).

Unresolved Review Threads

  • PRRT_kwDOSZt6uM66Q9tK: open
  • PRRT_kwDOSZt6uM66QvGA: open
  • PRRT_kwDOSZt6uM66M78v: open
  • PRRT_kwDOSZt6uM66Mnrf: open
  • PRRT_kwDOSZt6uM66MFL2: open
  • PRRT_kwDOSZt6uM65kLQB: open

Dependency Upgrade Coverage Accounting (reviewer-reported)

  • Coverage rollup: partial (4/5 aspects checked)
  • source_mapping: checked_no_match — Both Chart.yaml rows (version and appVersion 0.5.77) are this repo's own chart; values.yaml (call-22) maps the app image to ghcr.io/misospace/dispatch with tag falling back to appVersion — no external artifact, no mismatch.
  • release_notes: checked_no_match — The chart release notes are the CHANGELOG.md 0.5.77 section added by this PR, and upstream npm release notes for each bumped dependency were fetched (calls 3, 4, 6, 7, 8, 11, 14, 38).
  • advisories: checked_no_match — GitHub advisory API checked per bumped package with no match (calls 12, 13, 37, 39); effect advisory GHSA-7589-6fvf-x4pw is remediated by the resolved 3.22.5 (call-26); the picomatch exception GHSA-fc5q-39xc-vjpf was not re-verified upstream in this run.
  • signature_verification: not_checked — No cosign/attestation receipt for the chart or the ghcr.io/misospace/dispatch image was produced or checked in this run.
  • relevance: checked_no_match — The chart bump only advances version/appVersion; values.yaml (call-22) has no chart-level dependency pinned to the bumped versions, and the shipped image tag follows appVersion.

Statuses are the reviewer's answer, not harness receipts. Advisory coverage accounting: gaps are informational, not findings. not_checked means never investigated — not "no known vulnerabilities".

Approval withheld — review incomplete: a mandatory requirement remains unresolved No blocking code defect was proven; this run needs review and no native approval is certified.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants