chore(deps-dev): bump @typescript/native-preview from 7.0.0-dev.20260628.1 to 7.0.0-dev.20260629.1

[dependabot]

Bumps @typescript/native-preview from 7.0.0-dev.20260628.1 to 7.0.0-dev.20260629.1.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed July 1, 2026, 3:02 PM ET / 19:02 UTC.

Summary
Dependabot updates the development dependency @typescript/native-preview from 7.0.0-dev.20260628.1 to 7.0.0-dev.20260629.1 in package.json and pnpm-lock.yaml.

Reproducibility: not applicable. this is a dependency maintenance PR rather than a reported runtime bug.

Review metrics: 2 noteworthy metrics.

• Dependency files changed: 2 files, 39 additions, 39 deletions. The diff is limited to the manifest and lockfile, so review can focus on package resolution and CI results.
• Package check matrix: 6 Node platform checks passed. The changed compiler toolchain was exercised on Node 22 and Node 24 across ubuntu, macOS, and Windows in GitHub checks.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🌊 off-meta tidepool
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

• none.

Next step before merge

• No ClawSweeper repair lane is needed because the PR has no actionable review finding and should proceed through normal dependency-update review.

Security
Cleared: The diff updates an existing direct devDependency and lockfile integrity entries without adding new scripts, permissions, runtime dependencies, or package sources.

Review details

Best possible solution:

Merge the dependency-only update once maintainers are comfortable relying on the green package check matrix for the preview TypeScript toolchain.

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

Not applicable; this is a dependency maintenance PR rather than a reported runtime bug.

Is this the best way to solve the issue?

Yes; a manifest plus lockfile update is the narrow maintainable path for this devDependency bump, and the package check matrix is the right validation surface.

AGENTS.md: found and applied where relevant.

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

Label changes

Label changes:

• add P3: This is a low-risk development-dependency maintenance PR with no runtime router behavior change.
• 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 is a Dependabot-authored PR, so the external contributor real-behavior proof gate does not apply.

Label justifications:

• P3: This is a low-risk development-dependency maintenance PR with no runtime router behavior change.
• 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 is a Dependabot-authored PR, so the external contributor real-behavior proof gate does not apply.

Evidence reviewed

What I checked:

• Current main still uses old version: package.json on current main pins @typescript/native-preview to 7.0.0-dev.20260628.1, so the proposed dependency bump is not already implemented. (package.json:53, ec1dfe4ce00d)
• Lockfile still resolves old version: pnpm-lock.yaml on current main resolves @typescript/native-preview and the tsdown peer context against 7.0.0-dev.20260628.1. (pnpm-lock.yaml:14, ec1dfe4ce00d)
• PR metadata and checks: GitHub reports the PR as mergeable, changing only package.json and pnpm-lock.yaml; CI and CodeQL checks are successful, including Node 22 and Node 24 checks across ubuntu, macOS, and Windows. (9e980ac732c0)
• Dependency history: The current main version came from the prior Dependabot bump, which also changed only package.json and pnpm-lock.yaml. (package.json:53, ec1dfe4ce00d)
• No superseding item found: No same-repository PR for @typescript/native-preview 20260629 was returned, so there is no canonical replacement for this PR.
• Clean checkout after review: The read-only review left the target checkout clean.

Likely related people:

• Vincent Koc: The initial package metadata and lockfile were added in the package bootstrap/release commit. (role: initial package setup author; confidence: medium; commits: 61fb4ea24131; files: package.json, pnpm-lock.yaml)
• dependabot[bot]: The current @typescript/native-preview line on main was last changed by the previous Dependabot bump. (role: recent dependency updater; confidence: medium; commits: ec1dfe4ce00d; files: package.json, pnpm-lock.yaml)

What the crustacean ranks mean

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

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.

How this review workflow works

• 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.

[dependabot]

Superseded by #5.