Update detsys-ts: Merge pull request #109 from DeterminateSystems/tsup-to-tsdown

[detsys-pr-bot]

Bump detsys-ts to the latest HEAD and regenerate application bundle.

• Source ref: 285768c0d657f9709cb689893f12895c36923093
• Source pull request: DeterminateSystems/detsys-ts#109
• Source diff: c7303495f43d348cac78091ef434443b1ef22485..285768c0d657f9709cb689893f12895c36923093
• Diff file: 109.diff

Summary by CodeRabbit

• Chores
  • Updated development tooling dependencies to the latest patch release to improve type definitions and maintain compatibility with the current Node.js environment.
  • This maintenance update keeps build tooling and editor integrations current.
  • No user-facing changes or behavioral differences are expected.
  • Performance, features, and public APIs remain unchanged.
  • No action required for end-users.

[coderabbitai]

Walkthrough

Updated the devDependency "@types/node" in package.json from ^20.19.12 to ^20.19.13. No other files or fields changed.

Changes

Cohort / File(s)	Summary of Changes
Dev dependency bump package.json	Incremented devDependencies["@types/node"] from ^20.19.12 to ^20.19.13.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update detsys-ts: Capture the version of Nix in addition to the nix store version (#108) #197 — Also updates @types/node in package.json, closely related version bump.

Suggested reviewers

• grahamc

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title clearly identifies the main action — updating detsys-ts — which matches the PR objectives to bump detsys-ts to the latest HEAD and regenerate the bundle; therefore it is on-topic and not misleading. It is however verbose and includes redundant merge metadata ("Merge pull request #109 from DeterminateSystems/tsup-to-tsdown") that reduces readability and adds noise. Because the title conveys the primary change and is not vague, it meets the pass criteria.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Poem

A nibble of numbers, a tiny hop higher,
Types drift a notch—no need to perspire.
Package.json hums, dependencies align,
Carrot-shaped semvers looking fine.
I twitch my whiskers, stamp and cheer—
One small bump; the meadow’s clear! 🥕✨

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 786fff0 and d3ddf02.

⛔ Files ignored due to path filters (2)

• dist/index.js is excluded by !**/dist/**
• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (10)

• GitHub Check: Test: namespace-profile-default-arm64 with determinate
• GitHub Check: Test: macos-14-large with determinate
• GitHub Check: Test: macos-14-xlarge
• GitHub Check: Test: macos-14-xlarge with determinate
• GitHub Check: Test: ubuntu-latest
• GitHub Check: Test: macos-13-large
• GitHub Check: Test: macos-13-large with determinate
• GitHub Check: Test: nscloud-ubuntu-22.04-amd64-4x16
• GitHub Check: Test: macos-14-large
• GitHub Check: Test: namespace-profile-default-arm64

🔇 Additional comments (1)

package.json (1)

39-39: Confirm Node runtime, lockfile compatibility, and dist rebuild

• pnpm-lock.yaml pins detsys-ts to commit 285768c0d657f9709cb689893f12895c36923093 (see pnpm-lock.yaml).
• Verification failed at install: pnpm logged "Ignoring not compatible lockfile" then errored "Cannot install with 'frozen-lockfile' because pnpm-lock.yaml is absent" — fix lockfile / pnpm-version mismatch or re-generate a compatible lockfile so CI can install/build.
• Build/test/package did not run; dist/ regeneration was not confirmed. Ensure dist/ (bundle) was rebuilt and committed or that CI runs the bundle generation.
• Confirm GitHub Actions Node runtime is 20.x to match @types/node@^20.19.13.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}