Skip to content

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

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)#197
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 development and build dependencies to the latest patch versions for improved stability and tooling compatibility.
    • Refreshed TypeScript and linting toolchain to maintain alignment with current standards.
    • No changes to user-facing functionality or public APIs.
    • Low-risk maintenance update aimed at keeping the project up to date.

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

coderabbitai bot commented Sep 3, 2025

Walkthrough

Bumps versions of dev dependencies in package.json: got, @types/node, eslint-plugin-prettier, and typescript. No code or API changes.

Changes

Cohort / File(s) Summary
Dependency updates
package.json
Bumped 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 nudge my specs, hop-light and keen,
Patch bumps polished, tidy and clean.
No wires crossed, no routes askew—
Just fresher carrots in the stew. 🥕
Tap-tap, approve—then off I zoom,
A rabbit shipping to full bloom!

✨ 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 (squash) September 3, 2025 15:33
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: 1

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

33-35: Skip Action runtime verification; optionally declare Node engines
There’s no action.yml in this repo—this isn’t a JavaScript GitHub Action and CI uses Nix shells for Node. You can optionally add to package.json to document that you need a modern Node for got v14:

   "type": "module",
+  "engines": {
+    "node": ">=20.0.0"
+  },
📜 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 428f3c6 and 128522e.

⛔ 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). (11)
  • GitHub Check: Test: macos-14-large with determinate
  • GitHub Check: Test: macos-14-large
  • GitHub Check: Test: macos-14-xlarge
  • GitHub Check: Test: namespace-profile-default-arm64 with determinate
  • GitHub Check: Test: namespace-profile-default-arm64
  • GitHub Check: Test: macos-14-xlarge with determinate
  • GitHub Check: Test: ubuntu-latest
  • GitHub Check: Test: macos-13-large
  • GitHub Check: Test: nscloud-ubuntu-22.04-amd64-4x16
  • GitHub Check: Test: macos-13-large with determinate
  • GitHub Check: Check the dist/ folder is up to date
🔇 Additional comments (3)
package.json (3)

39-41: @types/node bump looks fine.

Matches Node 20+ usage typical for Actions; no concerns.


50-51: No action required: @typescript-eslint/eslint-plugin@7.18.0 is compatible with TS 5.9
Peer dependencies for @typescript-eslint/eslint-plugin@7.18.0 list typescript: "*", and the lockfile shows both the plugin and its parser resolving against TypeScript 5.9.2, confirming compatibility.


47-48: Peer compatibility verified — no changes required. eslint@^8.57.1 meets “>=8.0.0,” prettier@^3.6.2 meets “>=3.0.0,” and eslint-config-prettier@10.1.8 falls within “>=10.1.0” peer range.

Comment on lines 32 to 36
"detsys-ts": "github:DeterminateSystems/detsys-ts",
"got": "^14.4.7",
"got": "^14.4.8",
"string-argv": "^0.3.2",
"vitest": "^3.2.4"
},
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Pin detsys-ts commit and move vitest to devDeps for reproducibility and lean installs.

Lockfile likely pins the commit, but encoding the SHA in package.json avoids drift if the lock is regenerated. Vitest shouldn’t be a runtime dep for a bundled Action.

Apply:

   "dependencies": {
     "@actions/core": "^1.11.1",
     "@actions/exec": "^1.1.1",
     "@actions/github": "^6.0.1",
-    "detsys-ts": "github:DeterminateSystems/detsys-ts",
+    "detsys-ts": "github:DeterminateSystems/detsys-ts#c7303495f43d348cac78091ef434443b1ef22485",
     "got": "^14.4.8",
     "string-argv": "^0.3.2",
-    "vitest": "^3.2.4"
+    "vitest": "^3.2.4"
   },
   "devDependencies": {
+    "vitest": "^3.2.4",

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In package.json around lines 32 to 36, pin the detsys-ts dependency to a
specific commit SHA (replace "github:DeterminateSystems/detsys-ts" with
"github:DeterminateSystems/detsys-ts#<commit-sha>") to avoid drift when
lockfiles are regenerated, and move "vitest" from dependencies into
devDependencies (remove it from the "dependencies" block and add it under
"devDependencies") so vitest is not installed at runtime for the bundled Action;
update package.json accordingly and run npm install to refresh the lockfile.

@grahamc grahamc merged commit 18b667a into DeterminateSystems:main Sep 3, 2025
18 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