Skip to content

chore(release): prepare 0.14.1 - #402

Merged
steipete merged 1 commit into
mainfrom
maintenance/mcporter-release-final
Sep 24, 2026
Merged

chore(release): prepare 0.14.1#402
steipete merged 1 commit into
mainfrom
maintenance/mcporter-release-final

Conversation

@steipete

@steipete steipete commented Sep 24, 2026

Copy link
Copy Markdown
Collaborator

Prepare 0.14.1 with the Windows background-console fix, restored daemon activity-log filtering, and dependency security updates. The URI and brace-parser security fixes apply to development fixtures. Node 24 and the existing compatibility floor remain unchanged.

Validation: frozen install, formatting/lint/typecheck, the full test suite, Node and Bun builds, and audit on Crabbox; macOS release-contract tests under reduced priority; independent review through P2. Native signing, notarization, and publication follow this PR’s exact-head CI and the repository’s serialized release procedure.

@steipete
chore(release): prepare 0.14.1
af49a4a 
Finalize the Windows console fix, daemon log-filter fix, and development-fixture security updates. Preserve Node 24 compatibility and contributor credit. Combined Crabbox release checks, 2071 tests, Node/Bun builds, audit, macOS release-contract mocks, and independent review passed.
@steipete
steipete requested a review from a team as a code owner September 24, 2026 10:54
@clawsweeper

clawsweeper Bot commented Sep 24, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

@clawsweeper clawsweeper Bot added P2 Normal priority bug or improvement with limited blast radius. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels Sep 24, 2026
@clawsweeper

clawsweeper Bot commented Sep 24, 2026

Copy link
Copy Markdown
Contributor

Codex review: needs maintainer review before merge. Reviewed September 24, 2026, 7:01 AM ET / 11:01 UTC.

ClawSweeper review

What this changes

Sets MCPorter's package version to 0.14.1 and dates the release notes, adding highlights and a dependency-refresh entry for fixes already merged.

Merge readiness

✅ Ready for maintainer review

Keep open: current main still identifies itself as 0.14.0, so this PR supplies distinct release preparation for 0.14.1. The metadata follows the documented release checklist, and no defect was found in the introduced changes.

Priority: P2
Reviewed head: af49a4a4ad08008b5e75ed59be432168bb063575

Review scores

Measure Result What it means
Overall readiness 🐚 platinum hermit (4/6) The small release-metadata patch matches the repository's release contract and the fixes already on main, with no introduced correctness or security finding.
Proof confidence 🌊 off-meta tidepool Not applicable: The package version feeds CLI --version and release packaging, while the other edit is release prose. No 0.14.1 artifact run is captured in the supplied evidence, but this collaborator-authored release-preparation PR is exempt from contributor behavior proof; release artifacts have separate exact-tag gates, and no stored-data contract changes.
Patch quality 🐚 platinum hermit (4/6) No actionable review findings were identified.

Verification

Check Result Evidence
Real behavior Not applicable Not applicable: The package version feeds CLI --version and release packaging, while the other edit is release prose. No 0.14.1 artifact run is captured in the supplied evidence, but this collaborator-authored release-preparation PR is exempt from contributor behavior proof; release artifacts have separate exact-tag gates, and no stored-data contract changes.
Evidence reviewed 8 items Introduced release metadata: The pinned PR delta changes only CHANGELOG.md and package.json, adding five lines and removing two.
Release notes: The new 0.14.1 heading and notes describe daemon logging, Windows subprocess handling, and development-fixture dependency updates.
Current-main distinction: At the recorded main revision, package.json remains at 0.14.0 and the 0.14.1 changelog heading remains Unreleased.
Findings None None.
Security None None.

How this fits together

MCPorter's package version feeds CLI version output and release packaging. The changelog describes the changes that the release process will publish to npm and Homebrew.

flowchart LR
 A[Merged fixes] --> B[Release notes]
 C[Package version] --> D[CLI version output]
 B --> E[Signed release tag]
 C --> E
 E --> F[Verified release assets]
 F --> G[npm and Homebrew]
Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Publish 0.14.1 from a signed tag of the reviewed release commit, with the repository's native-asset proof and matching npm and Homebrew artifacts.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this PR prepares release metadata rather than reporting a new bug. The behavior described in its notes is present in current-main source and tests.

Is this the best way to solve the issue?

Yes: the two metadata edits match the documented release-preparation step, while the existing release process handles tagging, artifact verification, and publication.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 54286054dac7.

Labels

Label changes:

  • add P2: This is normal-priority release preparation for already-merged user fixes.
  • add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
  • add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The package version feeds CLI --version and release packaging, while the other edit is release prose. No 0.14.1 artifact run is captured in the supplied evidence, but this collaborator-authored release-preparation PR is exempt from contributor behavior proof; release artifacts have separate exact-tag gates, and no stored-data contract changes.

Label justifications:

  • P2: This is normal-priority release preparation for already-merged user fixes.
  • rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The package version feeds CLI --version and release packaging, while the other edit is release prose. No 0.14.1 artifact run is captured in the supplied evidence, but this collaborator-authored release-preparation PR is exempt from contributor behavior proof; release artifacts have separate exact-tag gates, and no stored-data contract changes.

Evidence

What I checked:

  • Introduced release metadata: The pinned PR delta changes only CHANGELOG.md and package.json, adding five lines and removing two. (package.json:3, af49a4a4ad08)
  • Release notes: The new 0.14.1 heading and notes describe daemon logging, Windows subprocess handling, and development-fixture dependency updates. (CHANGELOG.md:3, af49a4a4ad08)
  • Current-main distinction: At the recorded main revision, package.json remains at 0.14.0 and the 0.14.1 changelog heading remains Unreleased. (package.json:3, 54286054dac7)
  • Release contract: The checklist calls for package.json and CHANGELOG.md preparation, followed by source gates, exact-head CI, a signed tag, native verification, and serialized publication. (docs/RELEASE.md:30, 54286054dac7)
  • Merged behavior behind the notes: Current-main daemon code applies the logging selection to the caller-visible server alias; its test covers selected and excluded aliases sharing a connection, including stdout and file output. (src/daemon/host.ts:121, 54286054dac7)
  • Windows and dependency notes: Current-main source hides the background PowerShell window, and the existing lockfile pins the URI and brace-parser versions named in the release notes. Those dependencies are not changed by this PR. (pnpm-lock.yaml:9, 54286054dac7)

Likely related people:

  • steipete: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

Rating scale

Score Internal tier Crab rank Meaning
6/6 S 🦀 challenger crab Exceptional readiness
5/6 A 🦞 diamond lobster Very strong readiness
4/6 B 🐚 platinum hermit Good normal PR; ordinary maintainer review
3/6 C 🦐 gold shrimp Useful, but confidence is limited
2/6 D 🦪 silver shellfish Proof or implementation needs work
1/6 F 🧂 unranked krab Not merge-ready
N/A NA 🌊 off-meta tidepool Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

@steipete
steipete merged commit 93e0916 into main Sep 24, 2026
9 checks passed
@vincentkoc
vincentkoc deleted the maintenance/mcporter-release-final branch September 25, 2026 11:19
@clawsweeper clawsweeper Bot mentioned this pull request Oct 11, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

P2 Normal priority bug or improvement with limited blast radius. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@steipete