Uh oh!
There was an error while loading. Please reload this page.
chore: release v0.4.4 - #304
Conversation
There was a problem hiding this comment.
AI Automated Review
Analysis engine: MiniMax@https://litellm.jory.dev/v1 (anthropic)
Recommendation: Approve
This is a clean, minimal release commit that bumps the Dispatch package version from 0.4.3 to 0.4.4. The single-line diff is correct, the PR body accurately summarizes the merged work, and there are no schema or config changes to validate.
Change-by-change Findings
package.json
- Version bump:
0.4.3→0.4.4(line 4). This is the only change in the PR and matches the release intent declared in the title and body.
Sources / Verification
Cross-checked every item in the PR body against git log:
| Claim in PR body | Verified commit | Source |
|---|---|---|
POST /api/issues/reconcile scans PR body keywords (Fixes #/Closes #/Resolves #) | b6c7116 | PR #303 (fix/302-merged-pr-body-detection) |
Optional body field added to GithubPR type | 7ccf69e (feat: add optional body field to GithubPR type) | git log |
react 19.2.15 → 19.2.16 | 27b096c | PR #299 (renovate/react-monorepo) |
next 16.2.6 → 16.2.7 | 4f2f47b | PR #298 (renovate/nextjs-monorepo) |
actions/checkout v6.0.2 → v6.0.3 | e211580 | PR #301 |
github/codeql-action 7211b7c → 87557b9 | 6fbac56 | PR #300 |
All changes referenced in the release notes were merged into main before this release commit, so the version bump is consolidating previously-reviewed work rather than introducing new risk.
Standards Compliance
AGENTS.mddoes not specify a release process, but the version bump is consistent with the manifest-style release notes provided.- PR body states no schema migration required and no config changes needed — consistent with the diff (only the
versionfield changes). - No new env vars, no agent-name hardcoding, no secrets committed.
- No code standards violations in this diff (it is a one-line metadata change).
Linked Issue Fit
No linked issues were referenced in the PR body. Nothing to evaluate against acceptance criteria.
Evidence Provider Findings
No evidence providers were configured for this run. No high-priority signals to evaluate.
Tool Harness Findings
Tool harness reported 0 planned requests with a planning warning ("Could not parse planning response as JSON"). This is a harness-side parsing issue, not a PR-side problem, and does not affect the review of the version bump itself.
Unknowns / Needs Verification
- Minor documentation drift (pre-existing, not introduced by this PR):
README.md:13still advertises**Next.js**: 16.2.6 (App Router), whilepackage.jsonandpackage-lock.jsonare on16.2.7. This was already true before v0.4.4 (the bump to 16.2.7 was PR #298) and is out of scope for this release commit, but it would be a nice follow-up to align the README with the actual version shipped in v0.4.4. package-lock.jsonwas not included in the diff for this PR, which is expected — dependency bumps landed in their own PRs (#298, #299). No action needed here; flagging only for completeness.
Conclusion
The diff is minimal, correct, and consistent with the release notes. Approving.
Release v0.4.4
Changes since v0.4.3
Fixes:
POST /api/issues/reconcilenow scans PR body keywords (Fixes #, Closes #, Resolves #) to detect merged PR-to-issue closure links, in addition to branch name patterns (fix: scan PR body keywords for merged PR issue detection (#302) #303 / P1: /api/issues/reconcile merged PR detection misses body-keyword issue references #302)bodyfield toGithubPRtype to support body-text scanning (7ccf69e)Dependencies:
react19.2.15 → 19.2.16next16.2.6 → 16.2.7CI:
actions/checkoutv6.0.2 → v6.0.3github/codeql-action7211b7c → 87557b9Note: No schema migration required. No config changes needed.