Skip to content
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

chore(deps): update dependency @tsconfig/node-lts to ^20.1.3 #2028

Merged
merged 1 commit into from
Sep 15, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 20, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@tsconfig/node-lts (source) ^20.1.0 -> ^20.1.3 age adoption passing confidence

Warning

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


Release Notes

tsconfig/bases (@​tsconfig/node-lts)

v20.1.3

Compare Source

v20.1.2

Compare Source

v20.1.1

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.

Copy link
Contributor Author

renovate bot commented Aug 20, 2024

Branch automerge failure

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

Copy link

coderabbitai bot commented Aug 20, 2024

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

Walkthrough

A minor update has been made to the package.json file, specifically upgrading the version of the @tsconfig/node-lts package from ^20.1.0 to ^20.1.3. The rest of the dependencies and structure of the package.json remain unchanged.

Changes

File Change Summary
package.json Updated @tsconfig/node-lts from ^20.1.0 to ^20.1.3 in devDependencies.

Poem

In the garden of code, a change so spry,
A hop in the version, oh my, oh my!
With fixes and tweaks, it’s time to rejoice,
For TypeScript’s growth, we dance and we voice.
🌸🐇 Let’s celebrate well, with a leap and a sigh!


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.

Copy link

codecov bot commented Aug 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 29.03%. Comparing base (ae49e3c) to head (c442c51).
Report is 2 commits behind head on dev.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev    #2028   +/-   ##
=======================================
  Coverage   29.03%   29.03%           
=======================================
  Files         223      223           
  Lines       12545    12545           
  Branches      552      524   -28     
=======================================
  Hits         3642     3642           
  Misses       8903     8903           
Flag Coverage Δ
cli 7.14% <ø> (ø)
connection 22.42% <ø> (ø)
database 30.76% <ø> (ø)
gateway 23.46% <ø> (ø)
lobby 7.18% <ø> (ø)
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.

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

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

The code changes seem to focus on updating a devDependency '@tsconfig/node-lts' from version '20.1.0' to '20.1.3'. This change affects both package-lock.json and package.json files. In addition, a 'license' field ('MIT') has been added exclusively to the package-lock.json file. Although the changes seem appropriate and harmless, it is good practice to ensure that the changes do not affect any existing functionality or introduce potential bugs. It would be helpful to explain why the 'license' field was added to one file and not the other.

@@ -23,7 +23,7 @@
},
"devDependencies": {
"@sentry/cli": "^2.23.1",
"@tsconfig/node-lts": "^20.1.0",
"@tsconfig/node-lts": "^20.1.3",
Copy link

Choose a reason for hiding this comment

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

The '@tsconfig/node-lts' version has been updated from '^20.1.0' to '^20.1.3'. It's good practice to verify that this update doesn't break any existing functionality or introduce any bugs into the codebase.

"version": "20.1.0",
"resolved": "https://registry.npmjs.org/@tsconfig/node-lts/-/node-lts-20.1.0.tgz",
"integrity": "sha512-3w2D9MfGdqBL51pHB5nGFmGtXBn1gbO+n9xzwcGSvZPArtCn4tElk+6EeelLXispAeqv13GAgbzkgLNHtoxOCQ==",
"dev": true
Copy link

Choose a reason for hiding this comment

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

The '@tsconfig/node-lts' version has also been updated here. This change should be consistent with the update made in the package.json file.

"version": "20.1.3",
"resolved": "https://registry.npmjs.org/@tsconfig/node-lts/-/node-lts-20.1.3.tgz",
"integrity": "sha512-m3b7EP2U+h5tNSpaBMfcTuHmHn04wrgRPQQrfKt75YIPq6kPs2153/KfPHdqkEWGx5pEBvS6rnvToT+yTtC1iw==",
"dev": true,
Copy link

Choose a reason for hiding this comment

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

A 'license' field with the 'MIT' license has been added here. It would be helpful to include a reason for this addition in the pull request or commit message.

@@ -41,7 +41,7 @@
},
"devDependencies": {
"@sentry/cli": "^2.23.1",
"@tsconfig/node-lts": "^20.1.0",
"@tsconfig/node-lts": "^20.1.3",
Copy link

Choose a reason for hiding this comment

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

The '@tsconfig/node-lts' devDependency has been updated here as well. It's important to test the codebase after this update to ensure everything is still working correctly.

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

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

The code diff primarily shows updates to the version number for the '@tsconfig/node-lts' package in both 'package.json' and 'package-lock.json'. The version is updated from '20.1.0' to '20.1.3'. In general, such an update is good for keeping the software up-to-date with improvements, fixes, or new features. In addition to the version update, we see an additional field 'license' was added to 'node_modules/@tsconfig/node-lts' in 'package-lock.json'. However without context, it's hard to say if these changes actually improve anything.

@@ -23,7 +23,7 @@
},
"devDependencies": {
"@sentry/cli": "^2.23.1",
"@tsconfig/node-lts": "^20.1.0",
"@tsconfig/node-lts": "^20.1.3",
Copy link

Choose a reason for hiding this comment

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

The version number for the '@tsconfig/node-lts' package in the 'devDependencies' section of 'package.json' has been updated here. This is generally a good practice as it means the project is keeping up to date with the latest versions of its dependencies. It might be worth checking for any breaking changes or significant updates in the package's changelog between versions '20.1.0' and '20.1.3'.

"version": "20.1.0",
"resolved": "https://registry.npmjs.org/@tsconfig/node-lts/-/node-lts-20.1.0.tgz",
"integrity": "sha512-3w2D9MfGdqBL51pHB5nGFmGtXBn1gbO+n9xzwcGSvZPArtCn4tElk+6EeelLXispAeqv13GAgbzkgLNHtoxOCQ==",
"dev": true
Copy link

Choose a reason for hiding this comment

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

The version number for '@tsconfig/node-lts' has been updated in 'package-lock.json'. This change is expected, as both 'package-lock.json' and 'package.json' should hold the same version after an update. Maintaining consistency in versions across these two files is important for managing packages and ensuring everyone working on the project uses the same versions.

"version": "20.1.3",
"resolved": "https://registry.npmjs.org/@tsconfig/node-lts/-/node-lts-20.1.3.tgz",
"integrity": "sha512-m3b7EP2U+h5tNSpaBMfcTuHmHn04wrgRPQQrfKt75YIPq6kPs2153/KfPHdqkEWGx5pEBvS6rnvToT+yTtC1iw==",
"dev": true,
Copy link

Choose a reason for hiding this comment

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

A 'license' field has been added to '@tsconfig/node-lts' information in 'package-lock.json'. This is informative and doesn't influence the functionality in any way.

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

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

The given diff mainly involves an update to the '@tsconfig/node-lts' package version from '^20.1.0' to '^20.1.3' in both package.json and package-lock.json. This version change seems appropriate but please make sure to test and verify the update to ensure it doesn't break any existing functionality because of underlying code changes. Also, addition of license information for the package in package-lock.json is a good practice and doesn't add any extra risk or impact.

@@ -23,7 +23,7 @@
},
"devDependencies": {
"@sentry/cli": "^2.23.1",
"@tsconfig/node-lts": "^20.1.0",
"@tsconfig/node-lts": "^20.1.3",
Copy link

Choose a reason for hiding this comment

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

Updated the version of '@tsconfig/node-lts' in the 'devDependencies'. Ensure the new version is tested with the current system and check for any deprecated features or breaking changes.

"version": "20.1.0",
"resolved": "https://registry.npmjs.org/@tsconfig/node-lts/-/node-lts-20.1.0.tgz",
"integrity": "sha512-3w2D9MfGdqBL51pHB5nGFmGtXBn1gbO+n9xzwcGSvZPArtCn4tElk+6EeelLXispAeqv13GAgbzkgLNHtoxOCQ==",
"dev": true
Copy link

Choose a reason for hiding this comment

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

The version, resolved url and integrity hash are updated and seem to be in sync with the changes in the package.json

"version": "20.1.3",
"resolved": "https://registry.npmjs.org/@tsconfig/node-lts/-/node-lts-20.1.3.tgz",
"integrity": "sha512-m3b7EP2U+h5tNSpaBMfcTuHmHn04wrgRPQQrfKt75YIPq6kPs2153/KfPHdqkEWGx5pEBvS6rnvToT+yTtC1iw==",
"dev": true,
Copy link

Choose a reason for hiding this comment

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

Adding the 'license' key for the package 'node-lts'. This is good as it gives information about the license of this particular dependency.

@@ -41,7 +41,7 @@
},
"devDependencies": {
"@sentry/cli": "^2.23.1",
"@tsconfig/node-lts": "^20.1.0",
"@tsconfig/node-lts": "^20.1.3",
Copy link

@codecov codecov bot Aug 20, 2024

Choose a reason for hiding this comment

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

You've updated the version of @tsconfig/node-lts here. As long as this doesn't introduce breaking changes in the way the project uses TypeScript, this update should be fine. However, do ensure compatibility of this package's version with the rest of the project.

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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

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

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

coderabbitai[bot]
coderabbitai bot previously approved these changes Aug 20, 2024
Copy link
Contributor Author

renovate bot commented Aug 26, 2024

⚠️ 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-15T14_45_12_895Z-debug-0.log

Copy link

deepsource-io bot commented Aug 26, 2024

Here's the code health analysis summary for commits ae49e3c..c442c51. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource JavaScript LogoJavaScript✅ SuccessView Check ↗

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

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

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

CodecovAI submitted a new review for fbbb504

pnpm-lock.yaml Outdated
@@ -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)
Copy link

Choose a reason for hiding this comment

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

Don't see a reason to delete 'pg' from the versions mention alongside other dependencies since these are just version details not the actual dependency declaration.

pnpm-lock.yaml Outdated
@@ -79,7 +79,7 @@
version: link:packages/transactions
sequelize:
specifier: ^6.35.2
version: 6.37.3(pg@8.12.0)
Copy link

Choose a reason for hiding this comment

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

If the referenced 'pg' dependency is not used anywhere in the project, it's alright to remove it. However, if it is used, this deletion could potentially break the functionality.

@@ -100,7 +100,7 @@
specifier: ^2.23.1
version: 2.33.1
'@tsconfig/node-lts':
Copy link

Choose a reason for hiding this comment

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

Good to update the '@tsconfig/node-lts' version here as well to keep the application compatible with long-term support versions of Node.js.

pnpm-lock.yaml Outdated
@@ -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)
Copy link

Choose a reason for hiding this comment

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

Removing the 'pg' dependency from here as well will lead to inconsistency in the project if 'pg' is still being used elsewhere. Please make sure that it is removed from all the relevant places or not removed at all if still in use.

pnpm-lock.yaml Outdated
@@ -11376,7 +11376,7 @@

Copy link

Choose a reason for hiding this comment

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

Again, the removal of the 'pg' dependency should be carefully considered and checked with the rest of the application.

pnpm-lock.yaml Outdated
@@ -11394,8 +11394,6 @@
Copy link

Choose a reason for hiding this comment

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

If 'pg' is not required in the project, this ranges from harmless to beneficial since you can also shed any vulnerabilities 'pg' might expose to your application.

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

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

CodecovAI submitted a new review for fbbb504

pnpm-lock.yaml Outdated
@@ -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)
Copy link

Choose a reason for hiding this comment

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

You have changed the package versioning for '@adminjs/sequelize'. 'pg@8.12.0' is removed from 'version'. Ensure that the removal does not affect the overall functionality of the application. Testing should be done around this.

pnpm-lock.yaml Outdated
@@ -79,7 +79,7 @@ importers:
version: link:packages/transactions
sequelize:
specifier: ^6.35.2
version: 6.37.3(pg@8.12.0)
Copy link

Choose a reason for hiding this comment

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

Similar to the '@adminjs/sequelize' package, you have removed 'pg@8.12.0' from the sequelize 'version' field. Please make sure that large scale testing is done to ensure everything still works as expected.

@@ -100,7 +100,7 @@ importers:
specifier: ^2.23.1
version: 2.33.1
'@tsconfig/node-lts':
Copy link

Choose a reason for hiding this comment

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

'@tsconfig/node-lts' version is again updated here in the file 'pnpm-lock.yaml'. The previously noted points about testing apply here as well.

pnpm-lock.yaml Outdated
@@ -6034,11 +6034,11 @@ snapshots:
- react-is
- supports-color
Copy link

Choose a reason for hiding this comment

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

Here 'pg@8.12.0' is removed again, from the '@adminjs/sequelize' version in the snapshot. Similar concerns apply as detailed in the previous comments. Thorough testing should be an adequate counter-measure.

pnpm-lock.yaml Outdated
@@ -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)
Copy link

Choose a reason for hiding this comment

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

'pg@8.12.0' is also removed from the 'sequelize' version in the snapshots. Testing should help in identifying any issues due to this change.

pnpm-lock.yaml Outdated
@@ -11376,7 +11376,7 @@ snapshots:

Copy link

Choose a reason for hiding this comment

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

Once more 'pg@8.12.0' is removed, this time from 'sequelize' in the snapshot. Please provide further context around these changes to the removal of 'pg' package points and initiate comprehensive testing.

pnpm-lock.yaml Outdated
@@ -11394,8 +11394,6 @@ snapshots:
Copy link

Choose a reason for hiding this comment

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

'pg' as an optional dependency is removed here in the snapshots. As this package is crucial for working with PostgreSQL databases, its removal could lead to breakage if any part of the application makes PostgreSQL calls. Satisfy yourself that this change does not impact database functionalities.

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

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

CodecovAI submitted a new review for fbbb504

pnpm-lock.yaml Outdated
@@ -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)
Copy link

Choose a reason for hiding this comment

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

You've removed the PostgreSQL (pg) dependency from @adminjs/sequelize. If pg was a necessary dependency, its removal could introduce errors. Please ensure proper testing to check for any runtime issues.

pnpm-lock.yaml Outdated
@@ -79,7 +79,7 @@ importers:
version: link:packages/transactions
sequelize:
specifier: ^6.35.2
version: 6.37.3(pg@8.12.0)
Copy link

Choose a reason for hiding this comment

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

You've also removed PostgreSQL (pg) from the sequelize package. As Sequelize is an SQL-focused ORM, removing a SQL dependency seems risky. Thorough testing is required to ensure all features still work as expected without the pg package.

pnpm-lock.yaml Outdated
@@ -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)
Copy link

Choose a reason for hiding this comment

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

Again, PostgreSQL (pg) is removed from the dependencies. Be sure that either pg was not used, or the functionality it provided is covered by a different package.

pnpm-lock.yaml Outdated
@@ -11394,8 +11394,6 @@ snapshots:
Copy link

Choose a reason for hiding this comment

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

Removing pg from the optionalDependencies section of sequelize is also risky and could lead to potentially unanticipated runtime issues. Make sure that the functionalities pg provided are not crucial and that their removal does not introduce any issues.

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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b27a91a and fbbb504.

Files selected for processing (1)
  • package.json (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • package.json

coderabbitai[bot]
coderabbitai bot previously approved these changes Aug 26, 2024
@renovate renovate bot force-pushed the renovate/tsconfig-node-lts-20.x branch from fbbb504 to 2e80563 Compare August 27, 2024 12:10
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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between fbbb504 and 2e80563.

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 as they are similar to previous changes (1)
  • package.json

@renovate renovate bot force-pushed the renovate/tsconfig-node-lts-20.x branch 2 times, most recently from 30b2dda to da37d4e Compare August 27, 2024 13:32
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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2e80563 and da37d4e.

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 as they are similar to previous changes (1)
  • package.json

@renovate renovate bot force-pushed the renovate/tsconfig-node-lts-20.x branch 6 times, most recently from c702897 to 59bdbe9 Compare August 27, 2024 17:03
@renovate renovate bot force-pushed the renovate/tsconfig-node-lts-20.x branch from 59bdbe9 to 861f979 Compare September 5, 2024 16:40
@renovate renovate bot force-pushed the renovate/tsconfig-node-lts-20.x branch 4 times, most recently from e5486f0 to fbc6de9 Compare September 15, 2024 13:29
@renovate renovate bot added this pull request to the merge queue Sep 15, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to a conflict with the base branch Sep 15, 2024
@renovate renovate bot force-pushed the renovate/tsconfig-node-lts-20.x branch from fbc6de9 to 466f8c5 Compare September 15, 2024 13:36
@renovate renovate bot enabled auto-merge September 15, 2024 13:36
@renovate renovate bot force-pushed the renovate/tsconfig-node-lts-20.x branch 3 times, most recently from 7816013 to e899c5b Compare September 15, 2024 14:44
@renovate renovate bot force-pushed the renovate/tsconfig-node-lts-20.x branch from e899c5b to c442c51 Compare September 15, 2024 14:45
Copy link

sonarcloud bot commented Sep 15, 2024

@renovate renovate bot added this pull request to the merge queue Sep 15, 2024
Merged via the queue into dev with commit abfcc37 Sep 15, 2024
14 of 15 checks passed
@renovate renovate bot deleted the renovate/tsconfig-node-lts-20.x branch September 15, 2024 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants