Repository navigation
build(deps-dev): bump tsdown from 0.23.2 to 0.23.3 in the development group - #120
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the development group with 1 update: [tsdown](https://github.com/rolldown/tsdown). Updates `tsdown` from 0.23.2 to 0.23.3 - [Release notes](https://github.com/rolldown/tsdown/releases) - [Commits](rolldown/tsdown@v0.23.2...v0.23.3) --- updated-dependencies: - dependency-name: tsdown dependency-version: 0.23.3 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: development ... Signed-off-by: dependabot[bot] <support@github.com>
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
|
Codex review: needs maintainer review before merge. What this changesUpdates the locked tsdown version from 0.23.2 to 0.23.3 and its declaration plugin from 0.29.0-beta.2 to 0.28.8. Example: A developer installs the repository with pnpm install --frozen-lockfile.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness✅ Ready for maintainer review Keep this PR open: the focused dependency update is absent from reviewed main, matches the upstream patch release, and has passing checks with no actionable defect found. Priority: P3 Before mergeNone. FindingsNone. Agent review detailsHow this fits togetherThe development build runs tsdown over TypeScript entry points to produce the JavaScript and declaration files consumed through the package exports. flowchart LR
A[pnpm lockfile] --> B[Build tool versions]
B --> C[tsdown]
D[TypeScript entry points] --> C
C --> E[JavaScript bundles]
C --> F[Type declarations]
E --> G[Package consumers]
F --> G
Technical reviewBest possible solution: Land the focused lockfile update through the normal dependency review workflow. Do we have a high-confidence way to reproduce the issue? This is dependency maintenance; the upstream TypeScript 7.0 failure does not establish a target-repository bug because its declaration build uses TypeScript 6. Is this the best way to solve the issue? The generated lockfile update is the smallest appropriate change within the existing dependency range and follows the upstream patch correction. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against ee424e450dd6. Provenance checked
TestingProof path: shipped entry point. SecurityNone. EvidenceWhat I checked:
LabelsLabel changes:
Label justifications:
Rating scale6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior. WorkflowClawSweeper edits this one comment on every review. Comment Reviewed October 30, 2026, 1:27 PM ET / 17:27 UTC. |
Bumps the development group with 1 update: tsdown.
Updates
tsdownfrom 0.23.2 to 0.23.3Release notes
Sourced from tsdown's releases.
Commits
53638e8chore: release v0.23.30344c4ffix: downgrade rolldown-plugin-dts to 0.28 to restore TypeScript 7.0 support ...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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions