Repository navigation
release: 0.5.77 - #1620
release: 0.5.77#1620its-miso[bot] wants to merge 1 commit into
Conversation
682e025 to
68d12da
Compare
68d12da to
e922d56
Compare
e922d56 to
f7b15f1
Compare
f7b15f1 to
a0edbdb
Compare
a0edbdb to
499ba3f
Compare
139f62a to
c62465e
Compare
b3a519f to
ca960aa
Compare
35aaac8 to
25ea608
Compare
25ea608 to
1f6b453
Compare
1f6b453 to
8a6be1b
Compare
4479d07 to
56b21c3
Compare
56b21c3 to
23c8a69
Compare
23c8a69 to
39094d0
Compare
39094d0 to
ebe8d0f
Compare
ebe8d0f to
0545bd0
Compare
0545bd0 to
4163b4e
Compare
73c186f to
d51c947
Compare
d51c947 to
b86b42a
Compare
b86b42a to
e79159d
Compare
e79159d to
216fa74
Compare
There was a problem hiding this comment.
{"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 earlierleading-*) — cosmetic, no API break (call-38). - Test suite: head 216fa74 has green
Tests,Coverage,Lint,Typecheck,npm auditandnpm 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: openPRRT_kwDOSZt6uM66QvGA: openPRRT_kwDOSZt6uM66M78v: openPRRT_kwDOSZt6uM66Mnrf: openPRRT_kwDOSZt6uM66MFL2: openPRRT_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.
🤖 I have created a release beep boop
0.5.77 (2026-11-22)
Features
Bug Fixes
Chores
Refactors
This PR was generated with Release Please. See documentation.