chore(deps): update dependency @tsconfig/node20 to ^20.1.4 #2029

renovate · 2024-08-20T10:26:16Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@tsconfig/node20 (source)	`^20.1.2` -> `^20.1.4`

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

tsconfig/bases (@tsconfig/node20)

`v20.1.4`

Compare Source

`v20.1.3`

Compare Source

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate · 2024-08-20T10:26:17Z

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

coderabbitai · 2024-08-20T10:26:23Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The recent update involves a minor version change in the devDependencies of the package.json file, specifically for the @tsconfig/node20 package. The version has been updated from ^20.1.2 to ^20.1.4, reflecting improvements and bug fixes while maintaining compatibility. This update enhances the overall stability and performance of the project without altering its core functionality.

Changes

File	Change Summary
`package.json`	Updated `@tsconfig/node20` version from `^20.1.2` to `^20.1.4`

Poem

In the garden where code does bloom,
A version change dispels the gloom.
With fixes bright and features new,
Our project hops with joy, it’s true!
So here’s to code, smooth and bright,
Let’s celebrate this wondrous sight! 🐇✨

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>.
- 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 generate interesting stats about this repository and render them as a table.
- @coderabbitai show all the console.log statements in this repository.
- @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 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.

codecov · 2024-08-20T10:26:47Z

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 29.58%. Comparing base (feaa400) to head (78c6335).
Report is 7 commits behind head on dev.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev    #2029   +/-   ##
=======================================
  Coverage   29.58%   29.58%           
=======================================
  Files         222      222           
  Lines       12545    12545           
  Branches      454      522   +68     
=======================================
  Hits         3712     3712           
  Misses       8833     8833

Flag	Coverage Δ
cli	`7.14% <ø> (ø)`
connection	`22.42% <ø> (ø)`
database	`30.76% <ø> (ø)`
gateway	`23.46% <ø> (ø)`
lobby	`14.37% <ø> (ø)`
login	`7.14% <ø> (ø)`
mcots	`10.62% <ø> (ø)`
nps	`15.88% <ø> (ø)`
patch	`65.04% <ø> (ø)`
persona	`19.45% <ø> (ø)`
sessions	`91.98% <ø> (ø)`
shard	`47.71% <ø> (ø)`
shared	`23.71% <ø> (ø)`
shared-packets	`2.64% <ø> (ø)`
transactions	`60.54% <ø> (ø)`

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

codecov

The changes made involve updating the version of the @tsconfig/node20 from 20.1.2 to 20.1.4. This changes are shown in package-lock.json and package.json files. The specifics of the changes are in the resolved and integrity properties for node20 in the package-lock.json file. The change seems necessary and safe because it doesn't alter functionality or compatibility significantly. Overall the changes are well implemented.

codecov · 2024-08-20T10:27:01Z

package-lock.json

@@ -24,7 +24,7 @@
            "devDependencies": {
                "@sentry/cli": "^2.23.1",
                "@tsconfig/node-lts": "^20.1.0",
-                "@tsconfig/node20": "^20.1.2",
+                "@tsconfig/node20": "^20.1.4",


This is a good practice to keep your dependencies up to date. However, when updating a version it's highly recommended to also perform a test to ensure that the new version doesn't introduce unwanted changes or bugs.

codecov · 2024-08-20T10:27:02Z

package-lock.json

@@ -3876,7 +3876,9 @@
            "license": "MIT"
        },
        "node_modules/@tsconfig/node20": {
-            "version": "20.1.2",


The version number has been updated here as well which is consistent with the update made in package.json. It's important to keep dependency version numbers in sync across all files where they are mentioned otherwise it could lead to confusion and potential issues.

codecov · 2024-08-20T10:27:02Z

package-lock.json

@@ -3876,7 +3876,9 @@
            "license": "MIT"
        },
        "node_modules/@tsconfig/node20": {
-            "version": "20.1.2",
+            "version": "20.1.4",


The resolved URL now points to the new version of the dependency. You did a good job updating this as it's essential for others who will work on this project or for deployment purposes. They will be able to fetch the exact same version of the dependency as you have.

codecov · 2024-08-20T10:27:02Z

package-lock.json

@@ -3876,7 +3876,9 @@
            "license": "MIT"
        },
        "node_modules/@tsconfig/node20": {
-            "version": "20.1.2",
+            "version": "20.1.4",
+            "resolved": "https://registry.npmjs.org/@tsconfig/node20/-/node20-20.1.4.tgz",


It's good to see that you have updated the integrity hash. This will ensure that the correct and secure package version is being pulled from the registry.

codecov · 2024-08-20T10:27:02Z

package.json

@@ -42,7 +42,7 @@
    "devDependencies": {
        "@sentry/cli": "^2.23.1",
        "@tsconfig/node-lts": "^20.1.0",
-        "@tsconfig/node20": "^20.1.2",
+        "@tsconfig/node20": "^20.1.4",


This is a good practice to keep the dependencies in package.json up-to-date. Again, make sure to test the updated package version to ensure compatibility with your project.

codecov

The code review does not reveal any significant issues with the changes. The changes are primarily aimed at updating the version of @tsconfig/node20, which is a good practice to keep the packages updated. The updates are effectively reflected in package.json and package-lock.json

codecov · 2024-08-20T10:27:03Z

package-lock.json

@@ -24,7 +24,7 @@
            "devDependencies": {
                "@sentry/cli": "^2.23.1",
                "@tsconfig/node-lts": "^20.1.0",
-                "@tsconfig/node20": "^20.1.2",
+                "@tsconfig/node20": "^20.1.4",


It's good to see the version of @tsconfig/node20 has been updated from 20.1.2 to 20.1.4. There should normally be no issues with this, unless this new version introduces a breaking change which is not compatible with the rest of the project. Make sure to run all the tests after upgrade.

codecov · 2024-08-20T10:27:03Z

package-lock.json

@@ -3876,7 +3876,9 @@
            "license": "MIT"
        },
        "node_modules/@tsconfig/node20": {


The version of @tsconfig/node20 in the package-lock.json has also been updated to reflect the changes in package.json, which guarantees a consistent environment.

codecov · 2024-08-20T10:27:03Z

package-lock.json

@@ -3876,7 +3876,9 @@
            "license": "MIT"
        },
        "node_modules/@tsconfig/node20": {
-            "version": "20.1.2",
+            "version": "20.1.4",


The resolved URL for @tsconfig/node20 is documented well with the exact version file node20-20.1.4.tgz, pointing towards a good practice.

codecov · 2024-08-20T10:27:03Z

package-lock.json

@@ -3876,7 +3876,9 @@
            "license": "MIT"
        },
        "node_modules/@tsconfig/node20": {
-            "version": "20.1.2",
+            "version": "20.1.4",
+            "resolved": "https://registry.npmjs.org/@tsconfig/node20/-/node20-20.1.4.tgz",


It's great to see that you've included the integrity attribute, it provides subresource integrity which prevents tampering of the package and makes sure that package would not be installed if the integrity hash doesn't match with the expected.

codecov · 2024-08-20T10:27:03Z

package.json

@@ -42,7 +42,7 @@
    "devDependencies": {
        "@sentry/cli": "^2.23.1",
        "@tsconfig/node-lts": "^20.1.0",
-        "@tsconfig/node20": "^20.1.2",
+        "@tsconfig/node20": "^20.1.4",


Updating the @tsconfig/node20 version should not cause major issues as generally minor version changes are backward compatible. Just double check the version change notes/issue log to be absolutely sure.

coderabbitai

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 646aa88 and 4659669.

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)

Files skipped from review due to trivial changes (1)

package.json

renovate · 2024-08-26T18:47:07Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code EUNSUPPORTEDPROTOCOL
npm error Unsupported URL Type "link:": link:packages/lobby
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-15T13_29_39_016Z-debug-0.log

deepsource-io · 2024-08-26T18:47:39Z

Here's the code health analysis summary for commits feaa400..78c6335. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

codecov

CodecovAI submitted a new review for aef3354

codecov · 2024-08-26T18:48:03Z

pnpm-lock.yaml

@@ -10,7 +10,7 @@ importers:
    dependencies:
      '@adminjs/sequelize':
        specifier: ^4.1.1
-        version: 4.1.1(adminjs@7.8.11(@types/react@18.3.4))(sequelize@6.37.3(pg@8.12.0))
+        version: 4.1.1(adminjs@7.8.11(@types/react@18.3.4))(sequelize@6.37.3)


It seems like you've removed PostgreSQL as a dependency for sequelize. If you've switched databases, this is fine. But if you're still using PostgreSQL, this will cause errors. Please confirm this is the intended change.

codecov · 2024-08-26T18:48:03Z

pnpm-lock.yaml

@@ -79,7 +79,7 @@ importers:
        version: link:packages/transactions
      sequelize:
        specifier: ^6.35.2
-        version: 6.37.3(pg@8.12.0)


The pg package has also been removed from here. Again, if PostgreSQL is out of use, this is fine. If not, this is an issue.

codecov · 2024-08-26T18:48:03Z

pnpm-lock.yaml

@@ -6034,11 +6034,11 @@ snapshots:
      - react-is
      - supports-color

-  '@adminjs/sequelize@4.1.1(adminjs@7.8.11(@types/react@18.3.4))(sequelize@6.37.3(pg@8.12.0))':
+  '@adminjs/sequelize@4.1.1(adminjs@7.8.11(@types/react@18.3.4))(sequelize@6.37.3)':
    dependencies:
      adminjs: 7.8.11(@types/react@18.3.4)


PostgreSQL has been removed as a dependency from sequelize here too. This seems like a sweeping change, make sure it's been made consciously and after thorough testing.

codecov · 2024-08-26T18:48:04Z

pnpm-lock.yaml

@@ -11376,7 +11376,7 @@ snapshots:



Here also the PostgreSQL dependency is removed from sequelize. As highlighted before, it's vital to ensure if this is intentional and appropriate.

codecov · 2024-08-26T18:48:04Z

pnpm-lock.yaml

pg was listed here as an optional dependency. It's removal suggests a larger decision to move away from PostgreSQL. Validate if this change aligns with your project's database infrastructure strategy.

codecov

CodecovAI submitted a new review for aef3354

codecov · 2024-08-26T18:48:12Z

pnpm-lock.yaml

@@ -10,7 +10,7 @@ importers:
    dependencies:
      '@adminjs/sequelize':
        specifier: ^4.1.1
-        version: 4.1.1(adminjs@7.8.11(@types/react@18.3.4))(sequelize@6.37.3(pg@8.12.0))
+        version: 4.1.1(adminjs@7.8.11(@types/react@18.3.4))(sequelize@6.37.3)


('@adminjs/sequelize@4.1.1(adminjs@7.8.11(@types/react@18.3.4))(sequelize@6.37.3)'): It seems that the pg@8.12.0 has been removed as an parameter of sequelize. If you were relying on pg package indirectly via sequelize, this might affect your code. It would be wise to examine how this removal impacts your application.

codecov · 2024-08-26T18:48:12Z

pnpm-lock.yaml

@@ -79,7 +79,7 @@
        version: link:packages/transactions
      sequelize:
        specifier: ^6.35.2
-        version: 6.37.3(pg@8.12.0)


('sequelize@6.37.3'): pg@8.12.0 has been removed as an argument from sequelize. If pg was being imported within sequelize, and in turn, used by your code, this change could potentially affect your application behavior. Confirm this doesn't introduce breaking changes.

codecov · 2024-08-26T18:48:12Z

pnpm-lock.yaml

@@ -103,7 +103,7 @@
        specifier: ^20.1.0
        version: 20.1.3
      '@tsconfig/node20':


Again, the @tsconfig/node20 package version has been increased in pnpm-lock.yaml from ^20.1.2 to ^20.1.4. This should still align with the rest of code usage without breaking it, as explained before.

codecov · 2024-08-26T18:48:12Z

pnpm-lock.yaml

@@ -6034,11 +6034,11 @@
      - react-is
      - supports-color

-  '@adminjs/sequelize@4.1.1(adminjs@7.8.11(@types/react@18.3.4))(sequelize@6.37.3(pg@8.12.0))':
+  '@adminjs/sequelize@4.1.1(adminjs@7.8.11(@types/react@18.3.4))(sequelize@6.37.3)':
    dependencies:
      adminjs: 7.8.11(@types/react@18.3.4)


('sequelize@6.37.3'): pg@8.12.0 has been removed as an argument from sequelize in the snapshots section. Take care to examine this can't cause any inconsistency between your application's current use of this feature and future uses.

codecov · 2024-08-26T18:48:12Z

pnpm-lock.yaml

@@ -11376,7 +11376,7 @@



('sequelize@6.37.3'): pg@8.12.0 has been removed as an argument from sequelize in the snapshots section as well. Confirm these changes align with your application's requirements and don't introduce any breaking change.

codecov · 2024-08-26T18:48:13Z

pnpm-lock.yaml

optionalDependencies: The pg package has been removed from the optionalDependencies of sequelize. Should your code be using this package indirectly via sequelize, appropriate measures need to be taken to prevent any disruptions to your codebase.

codecov

CodecovAI submitted a new review for aef3354

codecov · 2024-08-26T18:48:19Z

pnpm-lock.yaml

@@ -10,7 +10,7 @@ importers:
    dependencies:
      '@adminjs/sequelize':
        specifier: ^4.1.1
-        version: 4.1.1(adminjs@7.8.11(@types/react@18.3.4))(sequelize@6.37.3(pg@8.12.0))


It appears 'pg' package was removed from ‘@adminjs/sequelize’ version dependencies. Make sure to test thoroughly to ensure the removal won't break any dependent functionality.

codecov · 2024-08-26T18:48:19Z

pnpm-lock.yaml

@@ -79,7 +79,7 @@
        version: link:packages/transactions
      sequelize:
        specifier: ^6.35.2


The 'pg' package is removed from sequelize. Ensure sequelize does not have any direct or indirect dependency on 'pg' that could potentially break the code.

codecov · 2024-08-26T18:48:20Z

pnpm-lock.yaml

@@ -103,7 +103,7 @@
        specifier: ^20.1.0
        version: 20.1.3
      '@tsconfig/node20':


Updating the '@tsconfig/node20' specifier should not cause major issues as generally minor version changes are backward compatible. Just double check to be absolutely sure.

codecov · 2024-08-26T18:48:20Z

pnpm-lock.yaml

@@ -6034,11 +6034,11 @@
      - react-is


The 'pg' package is removed from '@adminjs/sequelize'. This could potentially break the code if '@adminjs/sequelize' was using 'pg' directly or indirectly.

codecov · 2024-08-26T18:48:20Z

pnpm-lock.yaml

@@ -6034,11 +6034,11 @@
      - react-is
      - supports-color

-  '@adminjs/sequelize@4.1.1(adminjs@7.8.11(@types/react@18.3.4))(sequelize@6.37.3(pg@8.12.0))':
+  '@adminjs/sequelize@4.1.1(adminjs@7.8.11(@types/react@18.3.4))(sequelize@6.37.3)':
    dependencies:


The 'pg' package is removed from sequelize. This could have unwanted side effects if there were any dependencies on 'pg' in sequelize.

codecov · 2024-08-26T18:48:20Z

pnpm-lock.yaml

'pg' package is removed from sequelize dependencies. Consider reviewing if sequelize is dependent on 'pg' in any way to avoid potential breaks.

codecov · 2024-08-26T18:48:20Z

pnpm-lock.yaml

@@ -11376,7 +11376,7 @@

  sequelize-pool@7.1.0: {}

-  sequelize@6.37.3(pg@8.12.0):
+  sequelize@6.37.3:
    dependencies:
      '@types/debug': 4.1.12
      '@types/validator': 13.12.0


Removing the 'pg' package from optionalDependencies of sequelize could potentially introduce issues if 'pg' was being used conditionally.

coderabbitai

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4659669 and aef3354.

Files selected for processing (1)

package.json (1 hunks)

Files skipped from review due to trivial changes (1)

package.json

coderabbitai

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between aef3354 and 766ba34.

Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (1)

package.json (1 hunks)

Files skipped from review due to trivial changes (1)

package.json

coderabbitai

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 766ba34 and 9272e17.

Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (1)

package.json (1 hunks)

Files skipped from review due to trivial changes (1)

package.json

sonarcloud · 2024-09-15T13:30:56Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

renovate bot enabled auto-merge August 20, 2024 10:26

pull-request-size bot added the size/XS label Aug 20, 2024

codecov bot reviewed Aug 20, 2024

View reviewed changes

coderabbitai bot reviewed Aug 20, 2024

View reviewed changes

coderabbitai bot previously approved these changes Aug 20, 2024

View reviewed changes

renovate bot dismissed coderabbitai[bot]’s stale review via aef3354 August 26, 2024 18:47

renovate bot force-pushed the renovate/tsconfig-node20-20.x branch from 4659669 to aef3354 Compare August 26, 2024 18:47

pull-request-size bot added size/S and removed size/XS labels Aug 26, 2024

codecov bot reviewed Aug 26, 2024

View reviewed changes

coderabbitai bot reviewed Aug 26, 2024

View reviewed changes

coderabbitai bot approved these changes Aug 26, 2024

View reviewed changes

renovate bot force-pushed the renovate/tsconfig-node20-20.x branch from aef3354 to 766ba34 Compare August 27, 2024 12:11

coderabbitai bot reviewed Aug 27, 2024

View reviewed changes

renovate bot force-pushed the renovate/tsconfig-node20-20.x branch 2 times, most recently from 2d82a52 to 9272e17 Compare August 27, 2024 13:33

pull-request-size bot added size/XS and removed size/S labels Aug 27, 2024

coderabbitai bot reviewed Aug 27, 2024

View reviewed changes

renovate bot force-pushed the renovate/tsconfig-node20-20.x branch 3 times, most recently from d7aaa94 to 9577e47 Compare August 27, 2024 13:52

renovate bot force-pushed the renovate/tsconfig-node20-20.x branch 4 times, most recently from 44eec85 to 5e48b74 Compare August 27, 2024 17:04

renovate bot force-pushed the renovate/tsconfig-node20-20.x branch from 5e48b74 to 4d6ab91 Compare September 5, 2024 16:40

renovate bot force-pushed the renovate/tsconfig-node20-20.x branch from 4d6ab91 to 979a50a Compare September 15, 2024 13:11

pull-request-size bot added size/M and removed size/XS labels Sep 15, 2024

renovate bot force-pushed the renovate/tsconfig-node20-20.x branch from 979a50a to d8f94c4 Compare September 15, 2024 13:19

pull-request-size bot added size/XS and removed size/M labels Sep 15, 2024

renovate bot force-pushed the renovate/tsconfig-node20-20.x branch from d8f94c4 to 1993a14 Compare September 15, 2024 13:22

chore(deps): update dependency @tsconfig/node20 to ^20.1.4

78c6335

renovate bot force-pushed the renovate/tsconfig-node20-20.x branch from 1993a14 to 78c6335 Compare September 15, 2024 13:29

renovate bot added this pull request to the merge queue Sep 15, 2024

Merged via the queue into dev with commit 4c999f0 Sep 15, 2024
13 of 15 checks passed

renovate bot deleted the renovate/tsconfig-node20-20.x branch September 15, 2024 13:35

chore(deps): update dependency @tsconfig/node20 to ^20.1.4 #2029

chore(deps): update dependency @tsconfig/node20 to ^20.1.4 #2029

Conversation

renovate bot commented Aug 20, 2024 • edited Loading

Release Notes

v20.1.4

v20.1.3

Configuration

renovate bot commented Aug 20, 2024

Branch automerge failure

coderabbitai bot commented Aug 20, 2024 • edited Loading

Review skipped

Walkthrough

Changes

Poem

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

codecov bot commented Aug 20, 2024 • edited Loading

Codecov Report

codecov bot left a comment

Choose a reason for hiding this comment

codecov bot Aug 20, 2024

Choose a reason for hiding this comment

codecov bot Aug 20, 2024

Choose a reason for hiding this comment

codecov bot Aug 20, 2024

Choose a reason for hiding this comment

codecov bot Aug 20, 2024

Choose a reason for hiding this comment

codecov bot Aug 20, 2024

Choose a reason for hiding this comment

codecov bot left a comment

Choose a reason for hiding this comment

codecov bot Aug 20, 2024

Choose a reason for hiding this comment

codecov bot Aug 20, 2024

Choose a reason for hiding this comment

codecov bot Aug 20, 2024

Choose a reason for hiding this comment

codecov bot Aug 20, 2024

Choose a reason for hiding this comment

codecov bot Aug 20, 2024 • edited Loading

Choose a reason for hiding this comment

coderabbitai bot left a comment

Choose a reason for hiding this comment

renovate bot commented Aug 26, 2024 • edited Loading

⚠️ Artifact update problem

File name: package-lock.json

deepsource-io bot commented Aug 26, 2024 • edited Loading

Analysis Summary

codecov bot left a comment

Choose a reason for hiding this comment

codecov bot Aug 26, 2024

Choose a reason for hiding this comment

codecov bot Aug 26, 2024

Choose a reason for hiding this comment

codecov bot Aug 26, 2024

Choose a reason for hiding this comment

codecov bot Aug 26, 2024

Choose a reason for hiding this comment

codecov bot Aug 26, 2024

Choose a reason for hiding this comment

codecov bot left a comment

Choose a reason for hiding this comment

codecov bot Aug 26, 2024

Choose a reason for hiding this comment

codecov bot Aug 26, 2024

Choose a reason for hiding this comment

codecov bot Aug 26, 2024

Choose a reason for hiding this comment

codecov bot Aug 26, 2024

Choose a reason for hiding this comment

codecov bot Aug 26, 2024

Choose a reason for hiding this comment

codecov bot Aug 26, 2024

Choose a reason for hiding this comment

codecov bot left a comment

renovate bot commented Aug 20, 2024 •

edited

Loading

`v20.1.4`

`v20.1.3`

coderabbitai bot commented Aug 20, 2024 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)

codecov bot commented Aug 20, 2024 •

edited

Loading

codecov bot Aug 20, 2024 •

edited

Loading

renovate bot commented Aug 26, 2024 •

edited

Loading

deepsource-io bot commented Aug 26, 2024 •

edited

Loading