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 all non-major dependencies #68

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 16, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@changesets/cli (source) ^2.27.1 -> ^2.27.8 age adoption passing confidence devDependencies patch
@commitlint/cli (source) ^19.0.0 -> ^19.5.0 age adoption passing confidence devDependencies minor
@mheob/commitlint-config (source) ^1.1.1 -> ^1.1.2 age adoption passing confidence devDependencies patch
@mheob/prettier-config (source) ^3.2.0 -> ^3.3.1 age adoption passing confidence devDependencies minor
@mheob/tsconfig (source) ^2.0.0 -> ^2.2.1 age adoption passing confidence devDependencies minor
@types/node (source) ^20.11.16 -> ^20.16.5 age adoption passing confidence devDependencies minor
@vitest/coverage-istanbul (source) ^1.2.2 -> ^1.6.0 age adoption passing confidence devDependencies minor
cz-git (source) ^1.8.0 -> ^1.9.4 age adoption passing confidence devDependencies patch
dotenv ^16.4.1 -> ^16.4.5 age adoption passing confidence dependencies patch
eslint (source) ^8.56.0 -> ^8.57.1 age adoption passing confidence devDependencies patch
lint-staged ^15.2.2 -> ^15.2.10 age adoption passing confidence devDependencies patch
node (source) 20 -> 20.17.0 age adoption passing confidence minor
tsup (source) ^8.0.1 -> ^8.3.0 age adoption passing confidence devDependencies minor
typescript (source) ^5.3.3 -> ^5.6.2 age adoption passing confidence devDependencies minor
vitest (source) ^1.2.2 -> ^1.6.0 age adoption passing confidence devDependencies minor

Release Notes

changesets/changesets (@​changesets/cli)

v2.27.8

Compare Source

v2.27.7

Compare Source

Patch Changes

v2.27.6

Compare Source

Patch Changes

v2.27.5

Compare Source

Patch Changes

v2.27.4

Compare Source

Patch Changes

v2.27.3

Compare Source

Patch Changes
  • #​1357 18c966a Thanks @​Andarist! - Fixed an issue with changeset status executed without since argument. It should now correctly use the configured base branch as the default value.

v2.27.2

Compare Source

Patch Changes
conventional-changelog/commitlint (@​commitlint/cli)

v19.5.0

Compare Source

Features

19.4.1 (2024-08-28)

Note: Version bump only for package @​commitlint/cli

v19.4.1

Compare Source

Note: Version bump only for package @​commitlint/cli

v19.4.0

Compare Source

Features

v19.3.0

Compare Source

Note: Version bump only for package @​commitlint/cli

19.2.2 (2024-04-14)

Note: Version bump only for package @​commitlint/cli

19.2.1 (2024-03-19)

Note: Version bump only for package @​commitlint/cli

v19.2.2

Compare Source

Note: Version bump only for package @​commitlint/cli

mheob/config (@​mheob/commitlint-config)

v1.1.2

Compare Source

Patch Changes
vitest-dev/vitest (@​vitest/coverage-istanbul)

v1.6.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v1.5.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.5.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
Zhengqbbb/cz-git (cz-git)

v1.9.4

Compare Source

Bug Fixes

v1.9.3

Compare Source

Bug Fixes

v1.9.2

Compare Source

Bug Fixes
  • cz-git: incorrect maxSubjectLength on custom scope (#​173) (baa58ae)
eslint/eslint (eslint)

v8.57.1

Compare Source

lint-staged/lint-staged (lint-staged)

v15.2.10

Compare Source

Patch Changes

v15.2.9

Compare Source

Patch Changes
  • #​1463 b69ce2d Thanks @​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning MaxListenersExceededWarning: Possible EventEmitter memory leak detected.

v15.2.8

Compare Source

Patch Changes
  • f0480f0 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version switched the --show-toplevel flag with --show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js child_process. The new flag returns a path relative to the working directory, avoiding the issue.

    The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.

v15.2.7

Compare Source

Patch Changes
  • #​1440 a51be80 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.

v15.2.6

Compare Source

Patch Changes
  • #​1433 119adb2 Thanks @​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.

v15.2.5

Compare Source

Patch Changes
  • #​1424 31a1f95 Thanks @​iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.

  • #​1423 91abea0 Thanks @​iiroj! - Improve error logging when failing to read or parse a configuration file

  • #​1424 ee43f15 Thanks @​iiroj! - Upgrade micromatch@4.0.7

v15.2.4

Compare Source

Patch Changes
  • 4f4537a Thanks @​iiroj! - Fix release issue with previous version; update dependencies
nodejs/node (node)

v20.17.0

Compare Source

v20.16.0

Compare Source

v20.15.1

Compare Source

v20.15.0: 2024-06-20, Version 20.15.0 'Iron' (LTS), @​marco-ippolito

Compare Source

test_runner: support test plans

It is now possible to count the number of assertions and subtests that are expected to run within a test. If the number of assertions and subtests that run does not match the expected count, the test will fail.

test('top level test', (t) => {
  t.plan(2);
  t.assert.ok('some relevant assertion here');
  t.subtest('subtest', () => {});
});

Contributed by Colin Ihrig in #​52860

inspector: introduce the --inspect-wait flag

This release introduces the --inspect-wait flag, which allows debugger to wait for attachement. This flag is useful when you want to debug the code from the beginning. Unlike --inspect-brk, which breaks on the first line, this flag waits for debugger to be connected and then runs the code as soon as a session is established.

Contributed by Kohei Ueno in #​52734

zlib: expose zlib.crc32()

This release exposes the crc32() function from zlib to user-land.

It computes a 32-bit Cyclic Redundancy Check checksum of data. If
value is specified, it is used as the starting value of the checksum,
otherwise, 0 is used as the starting value.

The CRC algorithm is designed to compute checksums and to detect error
in data transmission. It's not suitable for cryptographic authentication.

const zlib = require('node:zlib');
const { Buffer } = require('node:buffer');

let crc = zlib.crc32('hello');  // 907060870
crc = zlib.crc32('world', crc);  // 4192936109

crc = zlib.crc32(Buffer.from('hello', 'utf16le'));  // 1427272415
crc = zlib.crc32(Buffer.from('world', 'utf16le'), crc);  // 4150509955

Contributed by Joyee Cheung in #​52692

cli: allow running wasm in limited vmem with --disable-wasm-trap-handler

By default, Node.js enables trap-handler-based WebAssembly bound
checks. As a result, V8 does not need to insert inline bound checks
int the code compiled from WebAssembly which may speedup WebAssembly
execution significantly, but this optimization requires allocating
a big virtual memory cage (currently 10GB). If the Node.js process
does not have access to a large enough virtual memory address space
due to system configurations or hardware limitations, users won't
be able to run any WebAssembly that involves allocation in this
virtual memory cage and will see an out-of-memory error.

$ ulimit -v 5000000
$ node -p "new WebAssembly.Memory({ initial: 10, maximum: 100 });"
[eval]:1
new WebAssembly.Memory({ initial: 10, maximum: 100 });
^

RangeError: WebAssembly.Memory(): could not allocate memory
    at [eval]:1:1
    at runScriptInThisContext (node:internal/vm:209:10)
    at node:internal/process/execution:118:14
    at [eval]-wrapper:6:24
    at runScript (node:internal/process/execution:101:62)
    at evalScript (node:internal/process/execution:136:3)
    at node:internal/main/eval_string:49:3

--disable-wasm-trap-handler disables this optimization so that
users can at least run WebAssembly (with a less optimial performance)
when the virtual memory address space available to their Node.js
process is lower than what the V8 WebAssembly memory cage needs.

Contributed by Joyee Cheung in #​52766

Other Notable Changes
Commits

Configuration

📅 Schedule: Branch creation - "before 4am on Wednesday" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate renovate bot requested a review from mheob as a code owner April 16, 2024 22:01
Copy link

changeset-bot bot commented Apr 16, 2024

⚠️ No Changeset found

Latest commit: a0af90b

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

Copy link

coderabbitai bot commented Apr 16, 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

The recent updates refine the project's Node.js environment and dependency management. The .nvmrc file now specifies an exact Node.js version, enhancing compatibility clarity. Additionally, the package.json file has seen multiple dependency upgrades, ensuring the project utilizes the latest improvements in functionality and security. This maintenance aligns the project with current standards.

Changes

File Change Summary
.nvmrc Updated Node.js version from 20 to 20.17.0.
package.json Multiple dependency updates, including:
- dotenv from ^16.4.1 to ^16.4.5
- @changesets/cli from ^2.27.1 to ^2.27.7
- @commitlint/cli from ^19.0.0 to ^19.4.1
- @mheob/commitlint-config from ^1.1.1 to ^1.1.2
- @mheob/prettier-config from ^3.2.0 to ^3.3.1
- @mheob/tsconfig from ^2.0.0 to ^2.2.1
- @types/node from ^20.11.16 to ^20.16.2
- @vitest/coverage-istanbul from ^1.2.2 to ^1.6.0
- cz-git from ^1.8.0 to ^1.9.4
- eslint from ^8.56.0 to ^8.57.0
- lint-staged from ^15.2.2 to ^15.2.9
- tsup from ^8.0.1 to ^8.2.4
- typescript from ^5.3.3 to ^5.5.4
- vite from ^5.0.12 to ^5.4.2
- vitest from ^1.2.2 to ^1.6.0.

Poem

🐇 In the garden of code, we leap and we bound,
Upgrading our tools, new features abound!
With Node.js spruced, and packages bright,
We’ll code through the day, and dance through the night!
Hooray for the changes, let’s all give a cheer,
For a smoother, sweet journey, the future is near! 🌷


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

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 895a91f to bf4a3ac Compare May 1, 2024 15:17
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from c5267b4 to c1b0d23 Compare May 20, 2024 23:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c1b0d23 to 7d869f9 Compare May 23, 2024 08:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7d869f9 to 529a64d Compare June 13, 2024 08:54
Copy link

sonarcloud bot commented Jun 13, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 5cc4e31 to 81a5ad9 Compare August 6, 2024 09:36
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 22137c8 and 81a5ad9.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Additional comments not posted (16)
.nvmrc (1)

1-1: Ensure compatibility with Node.js version 20.16.0.

The Node.js version has been updated from 20 to 20.16.0. Ensure that all dependencies and the project itself are compatible with this specific version.

package.json (15)

63-63: Update @vitest/coverage-istanbul to version 1.6.0.

The @vitest/coverage-istanbul package has been updated from ^1.2.2 to ^1.6.0. Ensure that the updated version is compatible with the project.


60-60: Update @mheob/prettier-config to version 3.3.1.

The @mheob/prettier-config package has been updated from ^3.2.0 to ^3.3.1. Ensure that the updated version is compatible with the project.


55-55: Update @changesets/cli to version 2.27.7.

The @changesets/cli package has been updated from ^2.27.1 to ^2.27.7. Ensure that the updated version is compatible with the project.


70-70: Update tsup to version 8.2.4.

The tsup package has been updated from ^8.0.1 to ^8.2.4. Ensure that the updated version is compatible with the project.


73-73: Update vitest to version 1.6.0.

The vitest package has been updated from ^1.2.2 to ^1.6.0. Ensure that the updated version is compatible with the project.


66-66: Update eslint to version 8.57.0.

The eslint package has been updated from ^8.56.0 to ^8.57.0. Ensure that the updated version is compatible with the project.


62-62: Update @types/node to version 20.14.14.

The @types/node package has been updated from ^20.11.16 to ^20.14.14. Ensure that the updated version is compatible with the project.


61-61: Update @mheob/tsconfig to version 2.1.0.

The @mheob/tsconfig package has been updated from ^2.0.0 to ^2.1.0. Ensure that the updated version is compatible with the project.


58-58: Update @mheob/commitlint-config to version 1.1.2.

The @mheob/commitlint-config package has been updated from ^1.1.1 to ^1.1.2. Ensure that the updated version is compatible with the project.

Verification successful

Update @mheob/commitlint-config to version 1.1.2.

The @mheob/commitlint-config package has been updated from ^1.1.1 to ^1.1.2. The package.json and pnpm-lock.yaml files confirm the update. The peer dependencies listed are compatible with the project.

  • package.json confirms version ^1.1.2.
  • pnpm-lock.yaml confirms resolved version 1.1.2.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify compatibility of @mheob/commitlint-config version 1.1.2 with the project.

# Test: Check if @mheob/commitlint-config 1.1.2 is compatible with the project.
# Expect: No compatibility issues.
npm ls @mheob/commitlint-config

Length of output: 104


Script:

#!/bin/bash
# Step 1: Confirm the version of @mheob/commitlint-config in package.json
echo "Checking package.json for @mheob/commitlint-config version..."
grep -A 2 '"@mheob/commitlint-config"' package.json

# Step 2: Confirm the resolved version of @mheob/commitlint-config in package-lock.json
echo "Checking package-lock.json for resolved @mheob/commitlint-config version..."
grep -A 2 '"@mheob/commitlint-config"' package-lock.json

# Step 3: Search the codebase for any references to @mheob/commitlint-config
echo "Searching the codebase for references to @mheob/commitlint-config..."
rg '@mheob/commitlint-config' -A 3

Length of output: 1511


52-52: Update dotenv to version 16.4.5.

The dotenv package has been updated from ^16.4.1 to ^16.4.5. Ensure that the updated version is compatible with the project.


72-72: Update vite to version 5.3.5.

The vite package has been updated from ^5.0.12 to ^5.3.5. Ensure that the updated version is compatible with the project.


57-57: Update @commitlint/cli to version 19.3.0.

The @commitlint/cli package has been updated from ^19.0.0 to ^19.3.0. Ensure that the updated version is compatible with the project.

Verification successful

Update @commitlint/cli to version 19.3.0.

The @commitlint/cli package has been verified to be updated to version 19.3.0 and is compatible with the project based on the information in the pnpm-lock.yaml file.

  • package.json confirms the version is set to ^19.3.0.
  • pnpm-lock.yaml shows no conflicts with other dependencies.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify compatibility of @commitlint/cli version 19.3.0 with the project.

# Test: Check if @commitlint/cli 19.3.0 is compatible with the project.
# Expect: No compatibility issues.
npm ls @commitlint/cli

Length of output: 95


Script:

#!/bin/bash
# Check the version of @commitlint/cli in package.json
rg '@commitlint/cli' package.json

# Check for @commitlint/cli dependencies in package-lock.json (if it exists)
if [ -f "package-lock.json" ]; then
  rg '@commitlint/cli' package-lock.json
fi

Length of output: 96


Script:

#!/bin/bash
# Search for any other references to @commitlint/cli in the codebase
rg '@commitlint/cli'

Length of output: 525


65-65: Update cz-git to version 1.9.4.

The cz-git package has been updated from ^1.8.0 to ^1.9.4. Ensure that the updated version is compatible with the project.


68-68: Update lint-staged to version 15.2.8.

The lint-staged package has been updated from ^15.2.2 to ^15.2.8. Ensure that the updated version is compatible with the project.

Verification successful

Update lint-staged to version 15.2.8.

The lint-staged package has been updated from ^15.2.2 to ^15.2.8. The configuration in package.json is compatible with the updated version.

  • package.json:
    "lint-staged": {
      "!(pnpm-)*.{cjs,js,mjs,ts,json,md,mdx,yaml,yml}": "pnpm exec prettier --write",
      "*.{cjs,js,mjs,ts}": "eslint --fix",
      "package.json": "pnpm dlx sort-package-json"
    }
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify compatibility of lint-staged version 15.2.8 with the project.

# Test: Check if lint-staged 15.2.8 is compatible with the project.
# Expect: No compatibility issues.
npm ls lint-staged

Length of output: 91


Script:

#!/bin/bash
# Search for lint-staged configuration in the project files to review for compatibility with version 15.2.8.
# This configuration is usually found in package.json or a separate .lintstagedrc file.

# Check for lint-staged configuration in package.json
rg '"lint-staged": {[^}]*}' package.json

# Check for a .lintstagedrc file
fd .lintstagedrc --exec cat {}

Length of output: 198


Script:

#!/bin/bash
# Corrected search for lint-staged configuration in the project files to review for compatibility with version 15.2.8.

# Check for lint-staged configuration in package.json
rg '"lint-staged": \{[^}]*\}' package.json

# Check for a .lintstagedrc file
fd .lintstagedrc --exec cat {}

Length of output: 79


Script:

#!/bin/bash
# Search for lint-staged configuration across all project files to review for compatibility with version 15.2.8.

# Search for lint-staged configuration in all project files
rg 'lint-staged' .

Length of output: 213


Script:

#!/bin/bash
# Extract the lint-staged configuration block from package.json for review.

# Extract lint-staged configuration from package.json
rg -A 10 '"lint-staged": \{' package.json

Length of output: 376


71-71: Update typescript to version 5.5.4.

The typescript package has been updated from ^5.3.3 to ^5.5.4. Ensure that the updated version is compatible with the project.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 81a5ad9 to a993f39 Compare August 10, 2024 10:43
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 81a5ad9 and a993f39.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .nvmrc

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a993f39 to 532f485 Compare August 10, 2024 15:31
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 a993f39 and 532f485.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .nvmrc

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 532f485 to 3cbc829 Compare August 12, 2024 18:28
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 532f485 and 3cbc829.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .nvmrc

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3cbc829 to e156de7 Compare August 16, 2024 06:11
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 3cbc829 and e156de7.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .nvmrc

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e156de7 to 33e16e5 Compare August 18, 2024 16:28
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 e156de7 and 33e16e5.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .nvmrc

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 33e16e5 to b59856a Compare August 19, 2024 19:57
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 33e16e5 and b59856a.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .nvmrc

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b59856a to 2054880 Compare August 21, 2024 09:48
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 b59856a and 2054880.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .nvmrc

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2054880 to 8fdaa4c Compare August 21, 2024 20:52
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 2054880 and 8fdaa4c.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .nvmrc

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8fdaa4c to bd6ebc6 Compare August 22, 2024 04:24
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 8fdaa4c and bd6ebc6.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .nvmrc

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from bd6ebc6 to 6e595a5 Compare August 23, 2024 16:28
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 bd6ebc6 and 6e595a5.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .nvmrc

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6e595a5 to b847ada Compare August 28, 2024 19:14
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 6e595a5 and b847ada.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .nvmrc

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b847ada to ec240e2 Compare August 31, 2024 01:50
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 b847ada and ec240e2.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .nvmrc

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ec240e2 to cec2576 Compare August 31, 2024 08:08
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 ec240e2 and cec2576.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (2)
  • .nvmrc (1 hunks)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json
Files skipped from review as they are similar to previous changes (1)
  • .nvmrc

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from e80a75e to 9eb7613 Compare September 8, 2024 01:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 77d2762 to 87c9fe8 Compare September 16, 2024 11:08
Copy link

sonarcloud bot commented Sep 20, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant