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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update all non-major dependencies #731

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

chore(deps): update all non-major dependencies #731

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 5, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@babel/core (source) 7.25.2 -> 7.26.8 age adoption passing confidence
@babel/preset-env (source) 7.25.4 -> 7.26.8 age adoption passing confidence
@changesets/cli (source) 2.27.7 -> 2.27.12 age adoption passing confidence
@vue/devtools-api (source) ^6.6.3 -> ^6.6.4 age adoption passing confidence
axios (source) 0.28.0 -> 0.29.0 age adoption passing confidence
core-js (source) ^3.38.1 -> ^3.40.0 age adoption passing confidence
core-js (source) 3.38.1 -> 3.40.0 age adoption passing confidence
cypress (source) ^13.14.1 -> ^13.17.0 age adoption passing confidence
drupal-jsonapi-params ^2.3.1 -> ^2.3.2 age adoption passing confidence
drupal-jsonapi-params 2.3.1 -> 2.3.2 age adoption passing confidence
drupal/tome (source) ^1.12.0 -> ^1.13.0 age adoption passing confidence
esbuild 0.23.1 -> 0.25.0 age adoption passing confidence
express-rate-limit ^7.4.0 -> ^7.5.0 age adoption passing confidence
launch-editor ^2.8.1 -> ^2.9.1 age adoption passing confidence
start-server-and-test ^2.0.5 -> ^2.0.10 age adoption passing confidence
yarn (source) 3.8.5 -> 3.8.7 age adoption passing confidence

Release Notes

babel/babel (@​babel/core)

v7.26.8

Compare Source

v7.26.8 (2025-02-08)

🏠 Internal
  • babel-preset-env
    • #​17097 Update dependency babel-plugin-polyfill-corejs3 to ^0.11.0

v7.26.7

Compare Source

🐛 Bug Fix

v7.26.0

Compare Source

v7.25.9

Compare Source

🐛 Bug Fix
🏠 Internal
🏃‍♀️ Performance

v7.25.8

Compare Source

🐛 Bug Fix
🏠 Internal
  • babel-parser, babel-plugin-proposal-async-do-expressions, babel-plugin-proposal-destructuring-private, babel-plugin-proposal-do-expressions, babel-plugin-proposal-explicit-resource-management, babel-plugin-proposal-export-default-from, babel-plugin-proposal-function-bind, babel-plugin-proposal-function-sent, babel-plugin-proposal-import-defer, babel-plugin-proposal-partial-application, babel-plugin-proposal-throw-expressions, babel-plugin-transform-async-generator-functions, babel-plugin-transform-class-static-block, babel-plugin-transform-dynamic-import, babel-plugin-transform-export-namespace-from, babel-plugin-transform-json-strings, babel-plugin-transform-logical-assignment-operators, babel-plugin-transform-nullish-coalescing-operator, babel-plugin-transform-numeric-separator, babel-plugin-transform-object-rest-spread, babel-plugin-transform-optional-catch-binding, babel-plugin-transform-optional-chaining, babel-plugin-transform-private-property-in-object, babel-preset-env

v7.25.7

Compare Source

🐛 Bug Fix
💅 Polish
🏠 Internal
  • babel-core
  • babel-helper-compilation-targets, babel-helper-plugin-utils, babel-preset-env
  • babel-plugin-proposal-destructuring-private, babel-plugin-syntax-decimal, babel-plugin-syntax-import-reflection, babel-standalone
  • babel-generator
🏃‍♀️ Performance
changesets/changesets (@​changesets/cli)

v2.27.12

Compare Source

Patch Changes

v2.27.11

Compare Source

Patch Changes

v2.27.10

Compare Source

v2.27.9

Compare Source

Patch Changes

v2.27.8

Compare Source

vuejs/devtools (@​vue/devtools-api)

v6.6.4

Compare Source

axios/axios (axios)

v0.29.0

Compare Source

Release notes:

Bug Fixes
Contributors to this release

v0.28.1

Compare Source

zloirock/core-js (core-js)

v3.40.0

Compare Source

v3.39.0

Compare Source

cypress-io/cypress (cypress)

v13.17.0

Compare Source

Changelog: https://docs.cypress.io/app/references/changelog#13-17-0

v13.16.1

Compare Source

Changelog: https://docs.cypress.io/app/references/changelog#13-16-1

v13.16.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-16-0

v13.15.2

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-15-2

v13.15.1

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-15-1

v13.15.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-15-0

v13.14.2

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-14-2

d34dman/drupal-jsonapi-params (drupal-jsonapi-params)

v2.3.2

Compare Source

Patch Changes
  • Fixed return for custom params method #​44.
evanw/esbuild (esbuild)

v0.25.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.24.0 or ~0.24.0. See npm's documentation about semver for more information.

  • Restrict access to esbuild's development server (GHSA-67mh-4wv8-2f99)

    This change addresses esbuild's first security vulnerability report. Previously esbuild set the Access-Control-Allow-Origin header to * to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in the report.

    Starting with this release, CORS will now be disabled, and requests will now be denied if the host does not match the one provided to --serve=. The default host is 0.0.0.0, which refers to all of the IP addresses that represent the local machine (e.g. both 127.0.0.1 and 192.168.0.1). If you want to customize anything about esbuild's development server, you can put a proxy in front of esbuild and modify the incoming and/or outgoing requests.

    In addition, the serve() API call has been changed to return an array of hosts instead of a single host string. This makes it possible to determine all of the hosts that esbuild's development server will accept.

    Thanks to @​sapphi-red for reporting this issue.

  • Delete output files when a build fails in watch mode (#​3643)

    It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.

  • Fix correctness issues with the CSS nesting transform (#​3620, #​3877, #​3933, #​3997, #​4005, #​4037, #​4038)

    This release fixes the following problems:

    • Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using :is() to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.

      /* Original code */
.parent {
  > .a,
  > .b1 > .b2 {
    color: red;
  }
}

/* Old output (with --supported:nesting=false) */
.parent > :is(.a, .b1 > .b2) {
  color: red;
}

/* New output (with --supported:nesting=false) */
.parent > .a,
.parent > .b1 > .b2 {
  color: red;
}

      Thanks to @​tim-we for working on a fix.

    • The & CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered && to have the same specificity as &. With this release, this should now work correctly:

      /* Original code (color should be red) */
div {
  && { color: red }
  & { color: blue }
}

/* Old output (with --supported:nesting=false) */
div {
  color: red;
}
div {
  color: blue;
}

/* New output (with --supported:nesting=false) */
div:is(div) {
  color: red;
}
div {
  color: blue;
}

      Thanks to @​CPunisher for working on a fix.

    • Previously transforming nested CSS incorrectly removed leading combinators from within pseudoclass selectors such as :where(). This edge case has been fixed and how has test coverage.

      /* Original code */
a b:has(> span) {
  a & {
    color: green;
  }
}

/* Old output (with --supported:nesting=false) */
a :is(a b:has(span)) {
  color: green;
}

/* New output (with --supported:nesting=false) */
a :is(a b:has(> span)) {
  color: green;
}

      This fix was contributed by @​NoremacNergfol.

    • The CSS minifier contains logic to remove the & selector when it can be implied, which happens when there is only one and it's the leading token. However, this logic was incorrectly also applied to selector lists inside of pseudo-class selectors such as :where(). With this release, the minifier will now avoid applying this logic in this edge case:

      /* Original code */
.a {
  & .b { color: red }
  :where(& .b) { color: blue }
}

/* Old output (with --minify) */
.a{.b{color:red}:where(.b){color:#​00f}}

/* New output (with --minify) */
.a{.b{color:red}:where(& .b){color:#​00f}}

  • Fix some correctness issues with source maps (#​1745, #​3183, #​3613, #​3982)

    Previously esbuild incorrectly treated source map path references as file paths instead of as URLs. With this release, esbuild will now treat source map path references as URLs. This fixes the following problems with source maps:

    • File names in sourceMappingURL that contained a space previously did not encode the space as %20, which resulted in JavaScript tools (including esbuild) failing to read that path back in when consuming the generated output file. This should now be fixed.

    • Absolute URLs in sourceMappingURL that use the file:// scheme previously attempted to read from a folder called file:. These URLs should now be recognized and parsed correctly.

    • Entries in the sources array in the source map are now treated as URLs instead of file paths. The correct behavior for this is much more clear now that source maps has a formal specification. Many thanks to those who worked on the specification.

  • Fix incorrect package for @esbuild/netbsd-arm64 (#​4018)

    Due to a copy+paste typo, the binary published to @esbuild/netbsd-arm64 was not actually for arm64, and didn't run in that environment. This release should fix running esbuild in that environment (NetBSD on 64-bit ARM). Sorry about the mistake.

  • Fix a minification bug with bitwise operators and bigints (#​4065)

    This change removes an incorrect assumption in esbuild that all bitwise operators result in a numeric integer. That assumption was correct up until the introduction of bigints in ES2020, but is no longer correct because almost all bitwise operators now operate on both numbers and bigints. Here's an example of the incorrect minification:

    // Original code
if ((a & b) !== 0) found = true

// Old output (with --minify)
a&b&&(found=!0);

// New output (with --minify)
(a&b)!==0&&(found=!0);

  • Fix esbuild incorrectly rejecting valid TypeScript edge case (#​4027)

    The following TypeScript code is valid:

    export function open(async?: boolean): void {
  console.log(async as boolean)
}

    Before this version, esbuild would fail to parse this with a syntax error as it expected the token sequence async as ... to be the start of an async arrow function expression async as => .... This edge case should be parsed correctly by esbuild starting with this release.

  • Transform BigInt values into constructor calls when unsupported (#​4049)

    Previously esbuild would refuse to compile the BigInt literals (such as 123n) if they are unsupported in the configured target environment (such as with --target=es6). The rationale was that they cannot be polyfilled effectively because they change the behavior of JavaScript's arithmetic operators and JavaScript doesn't have operator overloading.

    However, this prevents using esbuild with certain libraries that would otherwise work if BigInt literals were ignored, such as with old versions of the buffer library before the library fixed support for running in environments without BigInt support. So with this release, esbuild will now turn BigInt literals into BigInt constructor calls (so 123n becomes BigInt(123)) and generate a warning in this case. You can turn off the warning with --log-override:bigint=silent or restore the warning to an error with --log-override:bigint=error if needed.

  • Change how console API dropping works (#​4020)

    Previously the --drop:console feature replaced all method calls off of the console global with undefined regardless of how long the property access chain was (so it applied to console.log() and console.log.call(console) and console.log.not.a.method()). However, it was pointed out that this breaks uses of console.log.bind(console). That's also incompatible with Terser's implementation of the feature, which is where this feature originally came from (it does support bind). So with this release, using this feature with esbuild will now only replace one level of method call (unless extended by call or apply) and will replace the method being called with an empty function in complex cases:

    // Original code
const x = console.log('x')
const y = console.log.call(console, 'y')
const z = console.log.bind(console)('z')

// Old output (with --drop-console)
const x = void 0;
const y = void 0;
const z = (void 0)("z");

// New output (with --drop-console)
const x = void 0;
const y = void 0;
const z = (() => {
}).bind(console)("z");

    This should more closely match Terser's existing behavior.

  • Allow BigInt literals as define values

    With this release, you can now use BigInt literals as define values, such as with --define:FOO=123n. Previously trying to do this resulted in a syntax error.

  • Fix a bug with resolve extensions in node_modules (#​4053)

    The --resolve-extensions= option lets you specify the order in which to try resolving implicit file extensions. For complicated reasons, esbuild reorders TypeScript file extensions after JavaScript ones inside of node_modules so that JavaScript source code is always preferred to TypeScript source code inside of dependencies. However, this reordering had a bug that could accidentally change the relative order of TypeScript file extensions if one of them was a prefix of the other. That bug has been fixed in this release. You can see the issue for details.

  • Better minification of statically-determined switch cases (#​4028)

    With this release, esbuild will now try to trim unused code within switch statements when the test expression and case expressions are primitive literals. This can arise when the test expression is an identifier that is substituted for a primitive literal at compile time. For example:

    // Original code
switch (MODE) {
  case 'dev':
    installDevToolsConsole()
    break
  case 'prod':
    return
  default:
    throw new Error
}

// Old output (with --minify '--define:MODE="prod"')
switch("prod"){case"dev":installDevToolsConsole();break;case"prod":return;default:throw new Error}

// New output (with --minify '--define:MODE="prod"')
return;

  • Emit /* @​__KEY__ */ for string literals derived from property names (#​4034)

    Property name mangling is an advanced feature that shortens certain property names for better minification (I say "advanced feature" because it's very easy to break your code with it). Sometimes you need to store a property name in a string, such as obj.get('foo') instead of obj.foo. JavaScript minifiers such as esbuild and Terser have a convention where a /* @​__KEY__ */ comment before the string makes it behave like a property name. So obj.get(/* @​__KEY__ */ 'foo') allows the contents of the string 'foo' to be shortened.

    However, esbuild sometimes itself generates string literals containing property names when transforming code, such as when lowering class fields to ES6 or when transforming TypeScript decorators. Previously esbuild didn't generate its own /* @​__KEY__ */ comments in this case, which means that minifying your code by running esbuild again on its own output wouldn't work correctly (this does not affect people that both minify and transform their code in a single step).

    With this release, esbuild will now generate /* @​__KEY__ */ comments for property names in generated string literals. To avoid lots of unnecessary output for people that don't use this advanced feature, the generated comments will only be present when the feature is active. If you want to generate the comments but not actually mangle any property names, you can use a flag that has no effect such as --reserve-props=., which tells esbuild to not mangle any property names (but still activates this feature).

  • The text loader now strips the UTF-8 BOM if present (#​3935)

    Some software (such as Notepad on Windows) can create text files that start with the three bytes 0xEF 0xBB 0xBF, which is referred to as the "byte order mark". This prefix is intended to be removed before using the text. Previously esbuild's text loader included this byte sequence in the string, which turns into a prefix of \uFEFF in a JavaScript string when decoded from UTF-8. With this release, esbuild's text loader will now remove these bytes when they occur at the start of the file.

  • Omit legal comment output files when empty (#​3670)

    Previously configuring esbuild with --legal-comment=external or --legal-comment=linked would always generate a .LEGAL.txt output file even if it was empty. Starting with this release, esbuild will now only do this if the file will be non-empty. This should result in a more organized output directory in some cases.

  • Update Go from 1.23.1 to 1.23.5 (#​4056, #​4057)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses.

    This PR was contributed by @​MikeWillCook.

  • Allow passing a port of 0 to the development server (#​3692)

    Unix sockets interpret a port of 0 to mean "pick a random unused port in the ephemeral port range". However, esbuild's default behavior when the port is not specified is to pick the first unused port starting from 8000 and upward. This is more convenient because port 8000 is typically free, so you can for example restart the development server and reload your app in the browser without needing to change the port in the URL. Since esbuild is written in Go (which does not have optional fields like JavaScript), not specifying the port in Go means it defaults to 0, so previously passing a port of 0 to esbuild caused port 8000 to be picked.

    Starting with this release, passing a port of 0 to esbuild when using the CLI or the JS API will now pass port 0 to the OS, which will pick a random ephemeral port. To make this possible, the Port option in the Go API has been changed from uint16 to int (to allow for additional sentinel values) and passing a port of -1 in Go now picks a random port. Both the CLI and JS APIs now remap an explicitly-provided port of 0 into -1 for the internal Go API.

    Another option would have been to change Port in Go from uint16 to *uint16 (Go's closest equivalent of number | undefined). However, that would make the common case of providing an explicit port in Go very awkward as Go doesn't support taking the address of integer constants. This tradeoff isn't worth it as picking a random ephemeral port is a rare use case. So the CLI and JS APIs should now match standard Unix behavior when the port is 0, but you need to use -1 instead with Go API.

  • Minification now avoids inlining constants with direct eval (#​4055)

    Direct eval can be used to introduce a new variable like this:

    const variable = false
;(function () {
  eval("var variable = true")
  console.log(variable)
})()

    Previously esbuild inlined variable here (which became false), which changed the behavior of the code. This inlining is now avoided, but please keep in mind that direct eval breaks many assumptions that JavaScript tools hold about normal code (especially when bundling) and I do not recommend using it. There are usually better alternatives that have a more localized impact on your code. You can read more about this here: https://esbuild.github.io/link/direct-eval/

v0.24.2

Compare Source

  • Fix regression with --define and import.meta (#​4010, #​4012, #​4013)

    The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This

Configuration

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

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

♻ Rebasing: Whenever PR is behind base branch, 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 added the dependencies Pull requests that update a dependency file label Sep 5, 2024
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Sep 5, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update artifacts 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: docs/drupal/composer.lock
Command failed: composer update drupal/tome:1.13.0 --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - drupal/simple_oauth is locked to version 5.2.5 and an update of this package was not requested.
    - drupal/simple_oauth 5.2.5 requires league/oauth2-server ^8.3 -> satisfiable by league/oauth2-server[8.5.4].
    - lcobucci/clock 3.2.0 requires php ~8.2.0 || ~8.3.0 -> your php version (8.4.3) does not satisfy that requirement.
    - league/oauth2-server 8.5.4 requires lcobucci/clock ^2.2 || ^3.0 -> satisfiable by lcobucci/clock[3.2.0].
File name: yarn.lock
/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21616
    throw new Error(
          ^

Error: Error when performing the request to https://registry.npmjs.org/yarn/latest; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting
    at fetch (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21616:11)
    at async fetchAsJson (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21630:20)
    ... 4 lines matching cause stack trace ...
    at async Object.runMain (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23110:7) {
  [cause]: TypeError: globalThis.fetch is not a function
      at fetch (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21610:33)
      at async fetchAsJson (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21630:20)
      at async fetchLatestStableVersion (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21557:20)
      at async fetchLatestStableVersion2 (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21679:14)
      at async Engine.getDefaultVersion (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22305:23)
      at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22403:47)
      at async Object.runMain (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23110:7)
}
File name: docs/nuxt/yarn.lock
/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21616
    throw new Error(
          ^

Error: Error when performing the request to https://registry.npmjs.org/yarn/latest; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting
    at fetch (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21616:11)
    at async fetchAsJson (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21630:20)
    ... 4 lines matching cause stack trace ...
    at async Object.runMain (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23110:7) {
  [cause]: TypeError: globalThis.fetch is not a function
      at fetch (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21610:33)
      at async fetchAsJson (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21630:20)
      at async fetchLatestStableVersion (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21557:20)
      at async fetchLatestStableVersion2 (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21679:14)
      at async Engine.getDefaultVersion (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22305:23)
      at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22403:47)
      at async Object.runMain (/opt/containerbase/tools/corepack/0.31.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23110:7)
}

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Sep 5, 2024 •
edited
Loading

⚠️ No Changeset found

Latest commit: b7fb3ca

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

@coderabbitai coderabbitai
Copy link

coderabbitai bot commented Sep 5, 2024 •
edited
Loading

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.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @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 3 times, most recently from 9c95311 to 4572cc9 Compare September 9, 2024 16:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from f898a86 to 58e6db4 Compare September 22, 2024 04:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from adae594 to fe505cf Compare October 2, 2024 15:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 5cf34b9 to f362429 Compare October 10, 2024 16:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from b1dc974 to 22f9145 Compare October 24, 2024 20:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 8fb080c to cca19ca Compare October 31, 2024 01:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from cca19ca to 6adde67 Compare November 6, 2024 00:11
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from dccde78 to 9daa2f2 Compare November 23, 2024 18:44
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 50191c7 to f80b56c Compare December 4, 2024 18:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from a35dd99 to a4d9bfb Compare December 15, 2024 06:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 83165f1 to 89dfce5 Compare December 20, 2024 18:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 10ddced to 58ddcc9 Compare January 14, 2025 15:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 8e40410 to b159972 Compare January 24, 2025 16:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b159972 to dc5e8f1 Compare February 8, 2025 05:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from dc5e8f1 to b7fb3ca Compare February 8, 2025 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants