Skip to content

dependency updates #2806

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 18, 2025
Merged

dependency updates #2806

merged 1 commit into from
Apr 18, 2025

Conversation

imolorhe
Copy link
Collaborator

@imolorhe imolorhe commented Apr 18, 2025

Fixes

Checks

  • Ran yarn test-build
  • Updated relevant documentations
  • Updated matching config options in altair-static

Changes proposed in this pull request:

Summary by Sourcery

Chores:

  • Upgrade package versions to their latest minor and patch releases

Summary by CodeRabbit

  • Chores
    • Updated several dependencies across multiple packages to newer versions, including @nestjs/common, ng-mocks, Koa and its type definitions, @tanstack/react-query, and axios. No changes to features or user-facing functionality.

Copy link

sourcery-ai bot commented Apr 18, 2025

Reviewer's Guide by Sourcery

This pull request updates several dependencies in the project, including NestJS core modules, UI libraries, and other utility packages. The changes primarily involve version bumps in the pnpm-lock.yaml file and corresponding package.json files.

Updated class diagram for NestJS Common

classDiagram
  class NestJSCommon {
    <<interface>>
    +version: string
    +classTransformer: string
    +classValidator: string
    +reflectMetadata: string
    +rxjs: string
  }

  note for NestJSCommon "Updated version from 10.3.10 to 10.4.17"
Loading

Updated class diagram for Koa

classDiagram
  class Koa {
    <<interface>>
    +version: string
    +accepts: string
    +cacheContentType: string
    +contentDisposition: string
    +contentType: string
    +cookies: string
    +debug: string
    +delegates: string
    +depd: string
    +destroy: string
    +encodeUrl: string
    +escapeHtml: string
    +fresh: string
    +httpErrors: string
    +isType: string
    +keygrip: string
    +only: string
    +onFinished: string
    +statuses: string
    +stream: string
    +typeIs: string
    +vary: string
  }

  note for Koa "Updated version from 2.13.4 to 2.16.1"
Loading

Updated class diagram for React Query

classDiagram
  class ReactQuery {
    <<interface>>
    +version: string
    +queryCore: string
    +react: string
  }

  note for ReactQuery "Updated version from 5.51.5 to 5.74.4"
Loading

File-Level Changes

Change Details Files
Updated multiple dependencies in the project.
  • Updated '@nestjs/common' from version 10.3.10 to 10.4.17.
  • Updated '@nestjs/core' from version 10.3.10 to 10.3.10.
  • Updated '@nestjs/config' from version 3.2.3 to 3.2.3.
  • Updated '@nestjs/event-emitter' from version 2.0.4 to 2.0.4.
  • Updated '@nestjs/jwt' from version 10.2.0 to 10.2.0.
  • Updated '@nestjs/passport' from version 10.0.3 to 10.0.3.
  • Updated '@nestjs/platform-express' from version 10.3.10 to 10.3.10.
  • Updated '@nestjs/schedule' from version 4.1.0 to 4.1.0.
  • Updated '@nestjs/swagger' from version 7.4.0 to 7.4.0.
  • Updated '@nestjs/testing' from version 10.3.10 to 10.3.10.
  • Updated 'ng-mocks' from version 14.12.1 to 14.13.4.
  • Updated '@tanstack/react-query' from version 5.51.5 to 5.74.4.
  • Updated '@types/koa' from version 2.13.5 to 2.15.0.
  • Updated '@types/koa__router' from version 8.0.11 to 12.0.4.
  • Updated 'koa' from version 2.13.4 to 2.16.1.
  • Updated 'tslib' from version 2.6.3 to 2.8.1.
  • Updated 'axios' from version 0.18.1 to 0.30.0.
pnpm-lock.yaml
packages/altair-koa-middleware/package.json
packages/altair-api/package.json
packages/altair-app/package.json
plugins/ai/package.json
test-server/package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

coderabbitai bot commented Apr 18, 2025

Walkthrough

This update consists of dependency version bumps across several package.json files in different parts of the project. The changes include upgrading both runtime and development dependencies for packages related to NestJS, Koa, React Query, ng-mocks, and Axios. No changes were made to code, scripts, configurations, or public API declarations. The updates are strictly limited to dependency version numbers.

Changes

File(s) Change Summary
packages/altair-api/package.json Updated @nestjs/common dependency from ^10.3.10 to ^10.4.16.
packages/altair-app/package.json Updated ng-mocks devDependency from ^14.12.1 to ^14.13.4.
packages/altair-koa-middleware/package.json Updated koa from 2.13.1 to 2.16.1, @types/koa from 2.13.4 to 2.15.0, and @types/koa__router from 8.0.8 to 12.0.4.
plugins/ai/package.json Updated @tanstack/react-query dependency from ^5.51.5 to ^5.66.9.
test-server/package.json Updated axios dependency from ^0.18.1 to ^0.30.0.

Poem

Hopping through the code so bright,
Dependencies updated, all feels right!
Koa and NestJS, React Query too,
Fresh new versions, nothing else to do.
With every leap, the garden grows,
A bunny’s work, as everyone knows!
🐇✨

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • 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 generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

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

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Hello @imolorhe, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request updates various dependencies across multiple packages in the Altair GraphQL project. The packages affected include altair-api, altair-app, altair-koa-middleware, and the ai plugin. These updates involve both direct dependencies and development dependencies, aiming to incorporate the latest versions and associated fixes and features. The pnpm-lock.yaml file is also updated to reflect these changes, ensuring consistency across the project.

Highlights

  • Dependency Updates: The primary focus of this PR is to update dependencies in several packages, including @nestjs/common in altair-api, ng-mocks in altair-app, @types/koa and koa in altair-koa-middleware, and @tanstack/react-query in the ai plugin.
  • Lockfile Update: The pnpm-lock.yaml file has been updated to reflect the new dependency versions, ensuring that all environments use the same versions.
  • Test and Documentation Checks: The PR description indicates that yarn test-build has been run and relevant documentations and configs have been updated.

Changelog

Click here to see the changelog
  • packages/altair-api/package.json
    • Updated @nestjs/common from ^10.3.10 to ^10.4.16.
  • packages/altair-app/package.json
    • Updated ng-mocks from ^14.12.1 to ^14.13.4.
  • packages/altair-koa-middleware/package.json
    • Updated @types/koa from ^2.13.4 to ^2.15.0.
    • Updated @types/koa__router from ^8.0.8 to ^12.0.4.
    • Updated koa from ^2.13.1 to ^2.16.1.
  • plugins/ai/package.json
    • Updated @tanstack/react-query from ^5.51.5 to ^5.66.9.
  • pnpm-lock.yaml
    • The lockfile has been updated to reflect the new versions of all dependencies across the project.
  • test-server/package.json
    • Updated axios from ^0.18.1 to ^0.30.0.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


A version's gentle rise,
Dependencies dance in the code,
Stability blooms.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

The pull request updates dependencies across several packages. The changes seem straightforward, involving version bumps in package.json files and corresponding updates in pnpm-lock.yaml. No specific style guide was provided, so I'm defaulting to general best practices.

Merge Readiness

The pull request updates dependencies. Given the nature of the changes, it's crucial to ensure that all tests pass and that the updated dependencies don't introduce any regressions or breaking changes. I am unable to approve the pull request, and I recommend that the pull request not be merged until the test suite has been run and verified to pass. Also, given the number of dependency updates, it would be useful to have another reviewer take a look at the changes.

Comment on lines 18 to +19
"@graphql-yoga/plugin-graphql-sse": "^3.10.8",
"axios": "^0.18.1",
"axios": "^0.30.0",

Choose a reason for hiding this comment

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

medium

Updating axios from 0.18.1 to 0.30.0 is a significant jump. Ensure that all usages of axios in the test server are compatible with the new version. Review the axios changelog for any breaking changes that might affect the test server's functionality.

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @imolorhe - I've reviewed your changes - here's some feedback:

Overall Comments:

  • Consider running pnpm update to ensure all dependencies are updated to their latest compatible versions.
Here's what I looked at during the review
  • 🟢 General issues: all looks good
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Complexity: all looks good
  • 🟢 Documentation: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

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

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1ab7400 and 33dcb75.

⛔ Files ignored due to path filters (2)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
  • test-server/yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (5)
  • packages/altair-api/package.json (1 hunks)
  • packages/altair-app/package.json (1 hunks)
  • packages/altair-koa-middleware/package.json (1 hunks)
  • plugins/ai/package.json (1 hunks)
  • test-server/package.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (11)
  • GitHub Check: electron / electron (ubuntu-latest)
  • GitHub Check: electron / electron (macos-latest)
  • GitHub Check: docker / docker
  • GitHub Check: electron / electron (windows-latest)
  • GitHub Check: tests / e2e-test (ubuntu-latest)
  • GitHub Check: tests / e2e-test (macos-latest)
  • GitHub Check: tests / test (macos-latest)
  • GitHub Check: tests / test (ubuntu-latest)
  • GitHub Check: sites / Deploy sites
  • GitHub Check: tests / api-e2e-test
  • GitHub Check: build_and_preview
🔇 Additional comments (4)
test-server/package.json (1)

19-19: Approve axios version bump
Bumping axios to ^0.30.0 aligns with the rest of the project and pulls in important fixes.

Please run yarn build and exercise the GraphQL endpoints in this test server to validate that Axios usage behaves correctly under the new version.

plugins/ai/package.json (1)

13-13: Approve React Query version bump
Updating @tanstack/react-query to ^5.66.9 is consistent with the overall dependency strategy and includes performance improvements and bug fixes.

Ensure the plugin’s demo and test suite (yarn build && yarn test) still run without errors after this upgrade.

packages/altair-app/package.json (1)

164-164: Verify ng‑mocks minor update
Upgrading ng-mocks from ^14.12.1 to ^14.13.4 brings the latest fixes, but please confirm compatibility with your Angular v18 setup.

Run the full Angular build and test suite (pnpm test-build or yarn test) to catch any breaking changes in your components.

packages/altair-koa-middleware/package.json (1)

13-19: Validate Koa and its type definitions upgrade
Bumping "koa" to ^2.16.1 along with @types/koa (^2.15.0) and @types/koa__router (^12.0.4) brings in the latest API changes.

Please run:

pnpm install && pnpm declarations
pnpm run example

to ensure the middleware compiles and your example still works as expected.

@@ -11,7 +11,7 @@
"@langchain/community": "^0.3.12",
"@langchain/core": "^0.3.22",
"@langchain/openai": "^0.3.12",
"@nestjs/common": "^10.3.10",
"@nestjs/common": "^10.4.16",
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

⚠️ Potential issue

Align NestJS package versions
You’ve bumped @nestjs/common to ^10.4.16, but @nestjs/core and @nestjs/platform-express remain at ^10.3.10, which can cause peer‑dependency warnings or subtle mismatches.

Please synchronize all NestJS packages to the same version. For example:

-    "@nestjs/core": "^10.3.10",
+    "@nestjs/core": "^10.4.16",
@@
-    "@nestjs/platform-express": "^10.3.10",
+    "@nestjs/platform-express": "^10.4.16",

You may also want to bump @nestjs/testing in devDependencies to ^10.4.16 for full alignment.

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

Copy link

Visit the preview URL for this PR (updated for commit 33dcb75):

https://altair-gql--pr2806-imolorhe-dep-upd-lamsu99g.web.app

(expires Fri, 25 Apr 2025 06:41:10 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 02d6323d75a99e532a38922862e269d63351a6cf

@imolorhe imolorhe added this pull request to the merge queue Apr 18, 2025
Merged via the queue into master with commit 7247a88 Apr 18, 2025
17 checks passed
@imolorhe imolorhe deleted the imolorhe/dep-upd branch April 18, 2025 07:06
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.

1 participant