Skip to content

Update detsys-ts: Capture the version of Nix in addition to the nix store version (#108)#147

Merged
grahamc merged 1 commit intoDeterminateSystems:mainfrom
detsys-pr-bot:detsys-ts-update-c7303495f43d348cac78091ef434443b1ef22485
Sep 3, 2025
Merged

Update detsys-ts: Capture the version of Nix in addition to the nix store version (#108)#147
grahamc merged 1 commit intoDeterminateSystems:mainfrom
detsys-pr-bot:detsys-ts-update-c7303495f43d348cac78091ef434443b1ef22485

Conversation

@detsys-pr-bot
Copy link
Contributor

@detsys-pr-bot detsys-pr-bot commented Sep 3, 2025

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

Summary by CodeRabbit

  • Chores
    • Updated third-party dependencies to the latest patch/minor versions to improve stability, security, and compatibility.
    • No user-facing features or behavioral changes are expected as part of this update.

…e nix store version (DeterminateSystems#108)` (`c7303495f43d348cac78091ef434443b1ef22485`)
@coderabbitai
Copy link

coderabbitai bot commented Sep 3, 2025

Walkthrough

Dependency version bumps in package.json for got, @types/node, eslint-plugin-prettier, and typescript. No source code or control-flow changes.

Changes

Cohort / File(s) Summary of Changes
Dependency version bumps
package.json
Updated versions: got ^14.4.7→^14.4.8; @types/node ^20.19.9→^20.19.12; eslint-plugin-prettier ^5.5.3→^5.5.4; typescript ^5.8.3→^5.9.2

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibbled through the fields of semver green,
Bumped each leaf to a fresher sheen.
No code to chase, no flows to plot—
Just tidy carrots in the lot. 🥕
Version winds hum soft and light—
Patch by patch, we hop it right.

✨ 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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@grahamc grahamc enabled auto-merge September 3, 2025 15:35
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
package.json (1)

32-34: No action required: detsys-ts is already pinned to commit c7303495f43d3… in your lockfile and bundled output. Optional: if you want package.json to reflect that exact commit (so fresh installs without an existing lockfile still resolve to c7303495f43d3…), you can change the spec to

- "detsys-ts": "github:DeterminateSystems/detsys-ts",
+ "detsys-ts": "github:DeterminateSystems/detsys-ts#c7303495f43d348cac78091ef434443b1ef22485",
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 7f4e021 and f252c67.

⛔ 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 (2 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). (1)
  • GitHub Check: Build
🔇 Additional comments (2)
package.json (2)

38-38: @types/node ^20.19.12 bump looks fine.

No action needed if the action targets Node 20. Keep tsconfig lib/target aligned.


47-47: eslint-plugin-prettier ^5.5.4 bump is OK.

Peer deps with Prettier 3 and ESLint 8 appear satisfied.

"@actions/glob": "^0.5.0",
"detsys-ts": "github:DeterminateSystems/detsys-ts",
"got": "^14.4.7",
"got": "^14.4.8",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

got ^14.4.8: confirm Node engine and ESM-only usage.

  • got v14 is ESM-only; repo is "type":"module" so imports should be fine.
  • Ensure runner Node version (GitHub-hosted) satisfies got’s engine.

Checks:


🏁 Script executed:

#!/bin/bash
# No CommonJS requires of got
rg -nP "require\\(['\"]got['\"]\\)" -g 'src/**/*.ts' -C2 || true

# Installed got version and engines
pnpm list got --depth=0 || true
jq -r '.engines // {}' node_modules/got/package.json 2>/dev/null || true

Length of output: 155


🏁 Script executed:

#!/bin/bash
# Confirm no CommonJS requires of got
rg -nP "require\(['\"]got['\"]\)" -g 'src/**/*.ts' -C2 || true

# Confirm ESM imports usage of got
rg -nP "import\s+got" -g 'src/**/*.ts' -C2 || true

# Project Node engine requirement
jq -r '.engines.node // "none"' package.json

# Got package engines requirement
curl -s 'https://registry.npmjs.org/got/14.4.8' | jq -r '.engines.node // "none"'

Length of output: 572


got v14.4.8: ESM import confirmed; enforce Node.js ≥20

  • No CommonJS require("got") detected; ESM import got… is in use.
  • In package.json, add
    "engines": { "node": ">=20" }
    and update your GitHub Actions workflow to run on Node.js 20.x.
🤖 Prompt for AI Agents
In package.json around line 33, the project depends on got v14.4.8 which is
ESM-only and requires Node.js ≥20; add an "engines": {"node": ">=20"} entry to
package.json and update any CI workflow files (e.g., GitHub Actions matrix) to
include/use Node.js 20.x so runners use a compatible Node version; ensure
package.json formatting stays valid and bump any docs or README that state
supported Node versions.

"prettier": "^3.6.2",
"tsup": "^8.5.0",
"typescript": "^5.8.3"
"typescript": "^5.9.2"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

TypeScript ^5.9.2: verify lint/parser compatibility and typebreaks.

Ensure @typescript-eslint stack is compatible; bump if needed.

Quick sweep:


🏁 Script executed:

#!/bin/bash
# Show versions
node -v || true
pnpm list typescript @typescript-eslint/eslint-plugin @typescript-eslint/parser --depth=0 || true

# Typecheck without emitting
pnpm exec tsc --noEmit

# Lint to catch parser mismatch
pnpm run lint

Length of output: 439


🏁 Script executed:

#!/bin/bash
# Install dependencies to enable eslint and tsc commands
pnpm install --frozen-lockfile || pnpm install

# Show Node and package versions
node -v
pnpm list typescript @typescript-eslint/eslint-plugin @typescript-eslint/parser --depth=0

# Verify type checking
pnpm exec tsc --noEmit

# Run lint to catch any parser mismatches
pnpm run lint

Length of output: 3709


TypeScript ^5.9.2: fix typecheck & ESLint parser setup
• tsc is erroring on tsup.config.ts outside rootDir='src'—add it to tsconfig.json’s exclude (or expand rootDir).
@typescript-eslint/parser isn’t installed but is required by the ESLint plugin—add it to devDependencies to match your 7.18.0 plugin.
Re-run pnpm exec tsc --noEmit and pnpm run lint to confirm.

🤖 Prompt for AI Agents
In package.json around line 50, TypeScript ^5.9.2 is causing tsc to error on
files outside rootDir (e.g., tsup.config.ts) and ESLint requires
@typescript-eslint/parser but it’s not installed; update tsconfig.json to
exclude tsup.config.ts (or adjust rootDir to include it) so tsc stops
typechecking that file, add @typescript-eslint/parser@7.18.0 to devDependencies
to match the plugin version, then re-run pnpm exec tsc --noEmit and pnpm run
lint to verify fixes.

@grahamc grahamc added this pull request to the merge queue Sep 3, 2025
Merged via the queue into DeterminateSystems:main with commit 1177eb6 Sep 3, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants