Skip to content

chore(deps): upgrade dependencies#241

Merged
rhamzeh merged 1 commit into
mainfrom
chore/bump-deps
Aug 8, 2025
Merged

chore(deps): upgrade dependencies#241
rhamzeh merged 1 commit into
mainfrom
chore/bump-deps

Conversation

@rhamzeh

@rhamzeh rhamzeh commented Aug 8, 2025 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Member

Description

What problem is being solved?

How is it being solved?

What changes are made to solve it?

References

Review Checklist

  • I have clicked on "allow edits by maintainers".
  • I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
  • The correct base branch is being used, if not main
  • I have added tests to validate that the change in functionality is working as expected

Summary by CodeRabbit

  • Chores
    • Updated several dependencies to their latest versions for improved stability and compatibility.

@rhamzeh
rhamzeh requested a review from a team as a code owner August 8, 2025 04:22
@coderabbitai

coderabbitai Bot commented Aug 8, 2025 •
edited
Loading

Copy link
Copy Markdown

Walkthrough

The package.json file was updated to bump the versions of several dependencies and devDependencies, including axios, @types/node, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, nock, ts-jest, and typescript. No other changes or modifications to code, scripts, or configuration were made.

Changes

Cohort / File(s) Change Summary
Dependency Version Updates
package.json		 Upgraded versions for:
- axios (1.8.3 → 1.11.0)
- @types/node (22.13.10 → 24.2.0)
- @typescript-eslint/eslint-plugin and @typescript-eslint/parser (8.26.1 → 8.39.0)
- nock (14.0.1 → 14.0.9)
- ts-jest (29.2.6 → 29.4.1)
- typescript (5.8.2 → 5.9.2)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Note

🔌 MCP (Model Context Protocol) integration is now available in Early Access!

Pro users can now connect to remote MCP servers under the Integrations page to get reviews and chat conversations that understand additional development context.

📜 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 3f65221 and c9a73ca.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json (1 hunks)
🔇 Additional comments (3)
package.json (3)

26-26: Run the full test-matrix before publishing – axios went through three minor releases

Even within the same major, axios occasionally tightens typings or tweaks default behaviour (e.g., deprecating responseType: 'blob' on Node). 1.11.0 jumps over 1.9/1.10, so please ensure:

• Unit/integration tests still pass
• No new warnings are emitted by the TypeScript compiler

If CI isn’t covering browser builds, consider adding one before releasing.

38-40: ts-jest & TypeScript 5.9 combo – verify Jest config compatibility

[email protected] added initial TS 5.9 support but requires the preset: 'ts-jest' config to be regenerated (they removed some defaults). If tests/jest.config.js still relies on implicit transform, expect a runtime error:

● Validation Error:  Module <rootDir>/tests is not permitted …

Confirm the config or update as per the 29.4 migration notes.

32-32: No mismatch detected with @types/node@24
After confirming your engines.node is set to >=16.15.0 and scanning the codebase for Node 24–only globals (structuredClone, fs.promises.cp), no usages were found. Upgrading to @types/node@24 therefore poses no runtime or typing risk.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/bump-deps

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.
    • Explain this complex logic.
    • 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. Examples:
    • @coderabbitai explain this code block.
  • 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 src/utils.ts and explain its main purpose.
    • @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 comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai 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

Documentation and Community

  • 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.

@socket-security

socket-security Bot commented Aug 8, 2025

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updated@​typescript-eslint/​parser@​8.31.0 ⏵ 8.39.01001006997100
Updated@​typescript-eslint/​eslint-plugin@​8.31.0 ⏵ 8.39.099 +110078 +197100
Updated@​types/​node@​22.15.2 ⏵ 24.2.0100 +110080 +196100
Updatedtypescript@​5.8.3 ⏵ 5.9.2100 +110089 +1100100
Updatedts-jest@​29.3.2 ⏵ 29.4.1971009392 +5100
Updatedaxios@​1.9.0 ⏵ 1.11.099 +110010096100
Updatednock@​14.0.4 ⏵ 14.0.99910010098 +3100

View full report

@socket-security

socket-security Bot commented Aug 8, 2025

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
[email protected] has a License Policy Violation.

License: CC-BY-4.0 (npm metadata)

License: CC-BY-4.0 (package/LICENSE)

License: CC-BY-4.0 (package/package.json)

From: package-lock.json → npm/[email protected] → npm/[email protected] → npm/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
[email protected] has a License Policy Violation.

License: MIT-Khronos-old (package/ThirdPartyNoticeText.txt)

License: CC-BY-4.0 (package/ThirdPartyNoticeText.txt)

From: package-lock.json → npm/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@codecov-commenter

codecov-commenter commented Aug 8, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.16%. Comparing base (3f65221) to head (c9a73ca).

Additional details and impacted files 
@@           Coverage Diff           @@
##             main     #241   +/-   ##
=======================================
  Coverage   88.16%   88.16%           
=======================================
  Files          23       23           
  Lines        1217     1217           
  Branches      216      216           
=======================================
  Hits         1073     1073           
  Misses         86       86           
  Partials       58       58

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@rhamzeh
rhamzeh enabled auto-merge August 8, 2025 12:13
@rhamzeh
rhamzeh added this pull request to the merge queue Aug 8, 2025
Merged via the queue into main with commit a7c27dd Aug 8, 2025
21 checks passed
@rhamzeh
rhamzeh deleted the chore/bump-deps branch August 8, 2025 12:29
@coderabbitai coderabbitai Bot mentioned this pull request Aug 12, 2025
Merged
4 tasks
@coderabbitai coderabbitai Bot mentioned this pull request Feb 24, 2026
Merged
4 tasks
@coderabbitai coderabbitai Bot mentioned this pull request May 6, 2026
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sergiught sergiught sergiught approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@rhamzeh @codecov-commenter @sergiught