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

[dependabot]

Bumps @typescript/native-preview from 7.0.0-dev.20260615.1 to 7.0.0-dev.20260620.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 June 27, 2026, 3:07 PM ET / 19:07 UTC.

Summary
This PR bumps the direct devDependency @typescript/native-preview to 7.0.0-dev.20260620.1 and refreshes matching pnpm-lock.yaml entries.

Reproducibility: not applicable. this is a Dependabot dev-dependency update, not a bug report. The relevant source check is that current main still pins 7.0.0-dev.20260615.1 while the PR updates it.

Review metrics: 3 noteworthy metrics.

• Dependency scope: 1 direct devDependency updated. The change affects the TypeScript native tooling path, not the published runtime dependency list.
• Diff surface: 2 files changed, 43 added, 43 deleted. The review surface is limited to the package manifest and pnpm lockfile.
• Validation surface: 6 Node matrix jobs, 1 browser smoke, workflow lint, and CodeQL passed. The native-preview package is platform-sensitive, so cross-OS and Node-version CI success is meaningful pre-merge evidence.

Root-cause cluster
Relationship: canonical
Canonical: #16
Summary: This PR is the active newer native-preview Dependabot update; the immediately prior daily bump was closed as superseded.

Members:

• superseded: chore(deps-dev): bump @typescript/native-preview from 7.0.0-dev.20260615.1 to 7.0.0-dev.20260617.2 #14 - Dependabot commented that the older 7.0.0-dev.20260617.2 update was superseded by this PR, and that older PR is closed unmerged.
• adjacent_distinct: chore(deps-dev): bump @typescript/native-preview from 7.0.0-dev.20260614.1 to 7.0.0-dev.20260615.1 #6 - This earlier merged native-preview bump established the current main version, but it does not cover the newer requested version.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

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; this clean dependency-only PR should proceed through normal maintainer dependency review.

Security
Cleared: The diff only updates an existing direct devDependency and matching pnpm integrity entries, with no workflow, permission, script, secret, or publishing changes.

Review details

Best possible solution:

Review and merge the package/lockfile-only bump if maintainers are comfortable advancing the pinned native-preview dev toolchain.

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

Not applicable: this is a Dependabot dev-dependency update, not a bug report. The relevant source check is that current main still pins 7.0.0-dev.20260615.1 while the PR updates it.

Is this the best way to solve the issue?

Yes: changing package.json plus the generated pnpm lockfile is the narrow maintainable path for this pinned direct devDependency update.

AGENTS.md: found and applied where relevant.

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

Label changes

Label justifications:

• P3: This is routine development dependency maintenance with no source, protocol, or runtime 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: Not applicable: this is a Dependabot bot dependency update, so contributor real-behavior proof is not required.

Evidence reviewed

What I checked:

• Repository policy read: The full target AGENTS.md was read; its focused-change and repository-script guidance informed the dependency-only review while the checkout stayed read-only. (AGENTS.md:1, 8ffb44049333)
• Current main still has older package pin: Current main still sets @typescript/native-preview to 7.0.0-dev.20260615.1, so the requested bump is not already implemented. (package.json:92, 8ffb44049333)
• Current main lockfile still resolves older version: The importer and tsdown peer resolution in pnpm-lock.yaml still reference 7.0.0-dev.20260615.1. (pnpm-lock.yaml:21, 8ffb44049333)
• PR diff is dependency-scoped: The PR changes only package.json and pnpm-lock.yaml, replacing the native-preview package and lockfile resolutions with 7.0.0-dev.20260620.1. (package.json:92, fa50cd18cb6f)
• Validation and merge state: GitHub reports the PR as mergeable/clean, with Node 22/24 checks on Ubuntu, macOS, and Windows, browser smoke, workflow lint, and CodeQL checks passing. (fa50cd18cb6f)
• Related dependency PR search: The native-preview PR search found this PR as the only open native-preview update; the older 7.0.0-dev.20260617.2 PR is closed and marked superseded by this PR, while the prior 7.0.0-dev.20260615.1 bump is already merged. (fa50cd18cb6f)

Likely related people:

• vincentkoc: Recent package metadata, release validation, and Dependabot configuration commits touch this toolchain surface, and GitHub metadata shows this user merged the prior native-preview bump. (role: recent package and release contributor; confidence: high; commits: 8ffb44049333, c1ca6f199108, c0fdb1f0ebc2; files: package.json, pnpm-lock.yaml, .github/dependabot.yml)
• dependabot[bot]: Blame shows the current native-preview version on main came from a prior merged Dependabot bump, and this PR follows the same package and lockfile update path. (role: dependency automation for current pin; confidence: medium; commits: ed9ce515e4a2, fa50cd18cb6f; 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 #21.