Skip to content

fix: upgrade simple-git to support Node 24+#2005

Open
divyarathodgit wants to merge 2 commits intoasyncapi:masterfrom
divyarathodgit:fix/node-24-support
Open

fix: upgrade simple-git to support Node 24+#2005
divyarathodgit wants to merge 2 commits intoasyncapi:masterfrom
divyarathodgit:fix/node-24-support

Conversation

@divyarathodgit
Copy link

@divyarathodgit divyarathodgit commented Feb 16, 2026

This PR upgrades simple-git to the latest version to resolve compatibility issues with Node.js v24 (and other recent versions).

The Problem:
Older versions of simple-git trigger an ENOENT: no such file or directory, open 'node:buffer' error when running tests on modern Node environments due to changes in how internal modules are resolved.

The Fix:

Upgraded simple-git dependency in root and apps/generator.

Regenerated package-lock.json to reflect the version bump (minimal diff).

Verification:

npm run test:unit passes successfully on Node v24.13.0.

Summary by CodeRabbit

  • Chores
    • Updated project dependencies for improved stability and security.

Upgrades simple-git to resolve 'ENOENT: node:buffer' errors caused by internal API changes in newer Node.js versions. Verified with tests passing on Node 24.
@changeset-bot
Copy link

changeset-bot bot commented Feb 16, 2026

⚠️ No Changeset found

Latest commit: 3480ca9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@asyncapi-bot
Copy link
Contributor

What reviewer looks at during PR review

The following are ideal points maintainers look for during review. Reviewing these points yourself beforehand can help streamline the review process and reduce time to merge.

  1. PR Title: Use a concise title that follows our Conventional Commits guidelines and clearly summarizes the change using imperative mood (it means spoken or written as if giving a command or instruction, like "add new helper for listing operations")

    Note - In Generator, prepend feat: or fix: in PR title only when PATCH/MINOR release must be triggered.

  2. PR Description: Clearly explain the issue being solved, summarize the changes made, and mention the related issue.

    Note - In Generator, we use Maintainers Work board to track progress. Ensure the PR Description includes Resolves #<issue-number> or Fixes #<issue-number> this will automatically close the linked issue when the PR is merged and helps automate the maintainers workflow.

  3. Documentation: Update the relevant Generator documentation to accurately reflect the changes introduced in the PR, ensuring users and contributors have up-to-date guidance.

  4. Comments and JSDoc: Write clear and consistent JSDoc comments for functions, including parameter types, return values, and error conditions, so others can easily understand and use the code.

  5. DRY Code: Ensure the code follows the Don't Repeat Yourself principle. Look out for duplicate logic that can be reused.

  6. Test Coverage: Ensure the new code is well-tested with meaningful test cases that pass consistently and cover all relevant edge cases.

  7. Commit History: Contributors should avoid force-pushing as much as possible. It makes it harder to track incremental changes and review the latest updates.

  8. Template Design Principles Alignment: While reviewing template-related changes in the packages/ directory, ensure they align with the Assumptions and Principles. If any principle feels outdated or no longer applicable, start a discussion these principles are meant to evolve with the project.

  9. Reduce Scope When Needed: If an issue or PR feels too large or complex, consider splitting it and creating follow-up issues. Smaller, focused PRs are easier to review and merge.

  10. Bot Comments: As reviewers, check that contributors have appropriately addressed comments or suggestions made by automated bots. If there are bot comments the reviewer disagrees with, react to them or mark them as resolved, so the review history remains clear and accurate.

@coderabbitai
Copy link

coderabbitai bot commented Feb 16, 2026

📝 Walkthrough

Walkthrough

The simple-git dependency has been updated from version ^3.3.0 to ^3.30.0 in apps/generator/package.json, and the same dependency version has been added to the root package.json dependencies section.

Changes

Cohort / File(s) Summary
Dependency Updates
apps/generator/package.json, package.json
Updated and added simple-git dependency to version ^3.30.0. Root package.json now includes a dependencies section with this entry.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Merge Conflict Detection ⚠️ Warning ❌ Merge conflicts detected (6 files):

⚔️ .github/workflows/scripts/mailchimp/package-lock.json (content)
⚔️ apps/generator/package.json (content)
⚔️ package-lock.json (content)
⚔️ package.json (content)
⚔️ packages/helpers/src/ModelsPresets.js (content)
⚔️ packages/templates/clients/websocket/test/__fixtures__/asyncapi-websocket-components.yml (content)

These conflicts must be resolved before merging into master.
Resolve conflicts locally and push changes to this branch.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title follows Conventional Commits format with 'fix:' prefix, uses imperative mood, and accurately describes the main change: upgrading simple-git dependency to support Node 24+.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
⚔️ Resolve merge conflicts (beta)
  • Auto-commit resolved conflicts to branch fix/node-24-support
  • Post resolved changes as copyable diffs 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

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

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

🤖 Fix all issues with AI agents
In `@package.json`:
- Around line 49-51: Remove the redundant "simple-git" dependency from the root
package.json by deleting the "simple-git": "^3.30.0" entry from the
"dependencies" object (ensure the JSON remains valid—remove the trailing comma
if needed or delete the whole empty "dependencies" block if nothing else
remains); keep runtime dependency management in apps/generator/package.json
which already declares simple-git.

Comment on lines +49 to +51
"dependencies": {
"simple-git": "^3.30.0"
}
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

# First, check if apps/generator/package.json declares simple-git
cat apps/generator/package.json | grep -A 10 -B 2 "simple-git"

Repository: asyncapi/generator

Length of output: 411


🏁 Script executed:

# Run the verification script to check if simple-git is used directly at root level (outside workspace packages)
rg -n "simple-git" --glob '!node_modules' --glob '!package-lock.json' --glob '!apps/**' --glob '!packages/**'

Repository: asyncapi/generator

Length of output: 105


🏁 Script executed:

# Check the root package.json to understand workspace configuration and current state
cat package.json | head -60

Repository: asyncapi/generator

Length of output: 2381


🏁 Script executed:

# Look for any root-level scripts or configurations that might use simple-git
rg -n "require.*simple-git|import.*simple-git" --glob '!node_modules' --glob '!apps/**' --glob '!packages/**'

Repository: asyncapi/generator

Length of output: 44


Remove unnecessary simple-git dependency from root package.json.

apps/generator/package.json already declares simple-git as its own dependency, and there is no usage of simple-git at the root level. Adding it to the root's dependencies is redundant in a workspace monorepo. Workspace packages should manage their own runtime dependencies independently. Remove this entry to keep the root manifest clean.

Suggested diff
-  ],
-  "dependencies": {
-    "simple-git": "^3.30.0"
-  }
-}
+  ]
+}
🤖 Prompt for AI Agents
In `@package.json` around lines 49 - 51, Remove the redundant "simple-git"
dependency from the root package.json by deleting the "simple-git": "^3.30.0"
entry from the "dependencies" object (ensure the JSON remains valid—remove the
trailing comma if needed or delete the whole empty "dependencies" block if
nothing else remains); keep runtime dependency management in
apps/generator/package.json which already declares simple-git.

@sonarqubecloud
Copy link

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.

3 participants