Skip to content

release v0.7.3 - #160

Merged
btspoony merged 1 commit into
mainfrom
release/v0.7.3
Nov 17, 2026
Merged

btspoony merged 1 commit into
mainfrom
release/v0.7.3

Conversation

@btspoony

Copy link
Copy Markdown
Member

[0.7.3] - 2026-11-17

Merging this PR tags v0.7.3 and publishes [email protected] via the Release workflow.

@btspoony btspoony added the release Release PRs label Nov 17, 2026
@m-inspector

m-inspector Bot commented Nov 17, 2026

Copy link
Copy Markdown

✅ Verdict: ship it · Score 100% (mergeable)

Findings Count
🔴 must-fix 0
🟠 should-fix 0
🟡 may-fix 0
🔵 nit 0

📋 Review

What this PR does: This PR is the automated Release prep step for dsh-advisor 0.7.3: it sets the package.json version to 0.7.3 and adds the matching ## [0.7.3] - 2026-11-17 CHANGELOG section, whose entries are the two merges landed since 0.7.2 (the runtime-signature noteMaxChars documentation note from #159 and the word-boundary truncation fix from #157). Per the documented release flow, that committed CHANGELOG section is the single source for both the PR body and the GitHub Release body, so the diff is expected to be version metadata plus release notes rather than a runtime change of its own. Merging is the publish trigger: the Release workflow re-runs typecheck/build/test, publishes over OIDC trusted publishing, and tags v0.7.3.

Findings

none

Revalidated findings

none

Linked-issue AC

none — the PR links no issue (the captured issue list is empty and the body only describes the 0.7.3 release), so there are no acceptance criteria to check.

✅ Verified

- Review document records verdict ship it at 100% (band: mergeable) with an empty findings list — must-fix=0, should-fix=0, may-fix=0, nit=0.
- Prior-finding revalidation table is empty, consistent with the zero findings recorded for this head SHA (da3b06f).
- ❓ No check command (pnpm run typecheck / build / test), CI run link, or publish dry-run is recorded in the review document, so validation of the release artifacts is not evidenced here.
- ❓ Consistency between the package.json version and the CHANGELOG heading date/version is not recorded as an executed check in the review document.

🗑️ Considered & rejected

none — the review document records no candidate concerns that were considered and then rejected; its findings list is empty.

🛠️ Plan to fix

Expand fix plan
none — no must-fix, should-fix, may-fix, or nit findings remain. The only remaining action is the normal merge, after which the Release workflow validates, publishes, and tags v0.7.3.

Review 1 · commit da3b06f

@btspoony
btspoony merged commit 7986d7b into main Nov 17, 2026
2 checks passed
@btspoony
btspoony deleted the release/v0.7.3 branch November 17, 2026 06:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release Release PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant