Skip to content

chore: release 0.13.13 - #371

Merged
steipete merged 1 commit into
mainfrom
release/0.13.13
Sep 14, 2026
Merged

chore: release 0.13.13#371
steipete merged 1 commit into
mainfrom
release/0.13.13

Conversation

@steipete

@steipete steipete commented Sep 14, 2026

Copy link
Copy Markdown
Collaborator

Prepare mcporter 0.13.13 with the package version and finalized release notes. Preserve all seven changelog entries and lead with literal/prototype-named key handling and selected configuration-path diagnostics.

Validation: full release gates passed (format, lint, typecheck, 1,978 tests, Node and Bun builds, release-contract checks, and dependency audit), docs site and generated schema checks passed, and independent P0–P2 review was clean. Publication will follow green exact-commit CI, signed-tag native verification, and the existing npm/Homebrew workflows.

@steipete
steipete requested a review from a team as a code owner September 14, 2026 15:03
@clawsweeper

clawsweeper Bot commented Sep 14, 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 P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. 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 14, 2026
@clawsweeper

clawsweeper Bot commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

Codex review: needs maintainer review before merge. Reviewed September 14, 2026, 11:05 AM ET / 15:05 UTC.

ClawSweeper review

What this changes

Updates MCPorter’s package version to 0.13.13 and finalizes its dated release notes, preserving all seven entries.

Merge readiness

✅ Ready for maintainer review

Keep open: this is a focused, correct release-preparation patch that is still needed on main. The collaborator-authored PR has no actionable findings.

Priority: P3
Reviewed head: 2abc478d1db6e230c80bbc8e6b93fb952ba084ef

Review scores

Measure Result What it means
Overall readiness 🐚 platinum hermit (4/6) A focused release update consistent with prior releases and the documented process, with no actionable defect found.
Proof confidence 🌊 off-meta tidepool Not applicable: This collaborator-authored metadata PR is exempt from contributor runtime proof; signed-artifact verification remains a later publication gate in the existing release checklist.
Patch quality 🐚 platinum hermit (4/6) No actionable review findings were identified.

Verification

Check Result Evidence
Real behavior Not applicable Not applicable: This collaborator-authored metadata PR is exempt from contributor runtime proof; signed-artifact verification remains a later publication gate in the existing release checklist.
Evidence reviewed 6 items Complete introduced diff: The pinned base-to-head diff changes only package.json and CHANGELOG.md: the version advances to 0.13.13, the release receives a date and highlights, and all seven existing entries remain. The whitespace check passed.
Current-main necessity: GitHub confirmed main remains at the pinned base; its package version is 0.13.12, so this release metadata change is not already implemented.
Published release: The latest GitHub release is v0.13.12, published on 2026-09-11; publication of 0.13.13 is not established.
Findings None None.
Security None None.

How this fits together

MCPorter exposes MCP servers through a TypeScript runtime and CLI. Package metadata supplies its version, while the release pipeline uses that version and the changelog to prepare and verify published artifacts.

flowchart LR
  A[Package version] --> B[CLI and library builds]
  A --> C[Release tag checks]
  D[Dated release notes] --> E[GitHub release]
  B --> F[Signed artifact verification]
  C --> F
  F --> E
  E --> G[npm and Homebrew publication]
Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

Metric Value Why it matters
Release-note preservation 7 entries retained across 2 changed files The release preparation preserves the complete existing change list.

Technical review

Best possible solution:

Keep package and changelog versions aligned, then publish through the existing serialized signed-tag and verified-artifact release process.

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

Not applicable: this PR prepares release metadata and does not report a runtime defect.

Is this the best way to solve the issue?

Yes: updating the existing version source and finalizing the matching changelog follows the repository’s release checklist without adding another release mechanism.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 02fb2204e48a.

Labels

Label changes:

  • add P3: This is a bounded release-metadata update without runtime or publishing-workflow changes.
  • 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: This collaborator-authored metadata PR is exempt from contributor runtime proof; signed-artifact verification remains a later publication gate in the existing release checklist.

Label justifications:

  • P3: This is a bounded release-metadata update without runtime or publishing-workflow changes.
  • 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: This collaborator-authored metadata PR is exempt from contributor runtime proof; signed-artifact verification remains a later publication gate in the existing release checklist.

Evidence

What I checked:

  • Complete introduced diff: The pinned base-to-head diff changes only package.json and CHANGELOG.md: the version advances to 0.13.13, the release receives a date and highlights, and all seven existing entries remain. The whitespace check passed. (CHANGELOG.md:3, 2abc478d1db6)
  • Current-main necessity: GitHub confirmed main remains at the pinned base; its package version is 0.13.12, so this release metadata change is not already implemented. (package.json:3, 02fb2204e48a)
  • Published release: The latest GitHub release is v0.13.12, published on 2026-09-11; publication of 0.13.13 is not established.
  • Release contract and version consumers: The release checklist explicitly starts with package.json and CHANGELOG.md updates and places signed-tag native verification after source preparation. src/version.ts reads package metadata, and the Bun builder also reads the package version. This patch does not change publishing permissions, dependencies, scripts, or verification gates. (docs/RELEASE.md:29, 2abc478d1db6)
  • Previous release ownership: GitHub identifies steipete as the author of the prior 0.13.12 release commit, whose patch updates these same two files. Current-main package history also shows repeated release and dependency work by Peter Steinberger. (package.json:3, dee84c59969f)
  • Validation and inspection scope: The supplied PR body reports 1,978 passing tests and release gates; these were not rerun in this read-only review. Root AGENTS.md was read fully, and no maintainer-notes directory exists. Some historical blob reads and the related-PR search failed with HTTP 403; the complete introduced diff, current-main metadata, and previous release patch were successfully inspected. (AGENTS.md:1, 2abc478d1db6)

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 e4cb002 into main Sep 14, 2026
12 checks passed
@steipete
steipete deleted the release/0.13.13 branch September 14, 2026 15:35
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

P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. 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