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 #731

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 5, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@babel/core (source) 7.25.2 -> 7.26.0 age adoption passing confidence
@babel/preset-env (source) 7.25.4 -> 7.26.0 age adoption passing confidence
@changesets/cli (source) 2.27.7 -> 2.27.11 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.39.0 age adoption passing confidence
core-js (source) 3.38.1 -> 3.39.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.24.2 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.9 age adoption passing confidence
yarn (source) 3.8.5 -> 3.8.7 age adoption passing confidence

Release Notes

babel/babel (@​babel/core)

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
babel/babel (@​babel/preset-env)

v7.26.0

Compare Source

🚀 New Feature
  • babel-core, babel-generator, babel-parser, babel-plugin-syntax-import-assertions, babel-plugin-syntax-import-attributes, babel-preset-env, babel-standalone, babel-types
  • babel-core
  • babel-compat-data, babel-plugin-proposal-regexp-modifiers, babel-plugin-transform-regexp-modifiers, babel-preset-env, babel-standalone
  • babel-parser
  • babel-generator, babel-parser, babel-plugin-syntax-flow
  • babel-helpers, babel-preset-typescript, babel-runtime-corejs3
  • babel-generator, babel-parser
🐛 Bug Fix
💅 Polish
  • babel-plugin-proposal-json-modules, babel-plugin-transform-json-modules, babel-standalone
🏠 Internal
🏃‍♀️ Performance
  • babel-helper-module-transforms, babel-plugin-transform-modules-commonjs

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.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.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.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 change fixes the regression.

    This fix was contributed by @​sapphi-red.

v0.24.1

Compare Source

  • Allow es2024 as a target in tsconfig.json (#​4004)

    TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

    {
      "compilerOptions": {
        "target": "ES2024"
      }
    }

    As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

    This fix was contributed by @​billyjanitsch.

  • Allow automatic semicolon insertion after get/set

    This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

    class Foo {
      get
      *x() {}
      set
      *y() {}
    }

    The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

  • Allow quoted property names in --define and --pure (#​4008)

    The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

    // The following code now transforms to "return true;\n"
    console.log(esbuild.transformSync(
      `return process.env['SOME-TEST-VAR']`,
      { define: { 'process.env["SOME-TEST-VAR"]': 'true' } },
    ))

    Note that if you're passing values like this on the command line using esbuild's --define flag, then you'll need to know how to escape quote characters for your shell. You may find esbuild's JavaScript API more ergonomic and portable than writing shell code.

  • Minify empty try/catch/finally blocks (#​4003)

    With this release, esbuild will now attempt to minify empty try blocks:

    // Original code
    try {} catch { foo() } finally { bar() }
    
    // Old output (with --minify)
    try{}catch{foo()}finally{bar()}
    
    // New output (with --minify)
    bar();

    This can sometimes expose additional minification opportunities.

  • Include entryPoint metadata for the copy loader (#​3985)

    Almost all entry points already include a entryPoint field in the outputs map in esbuild's build metadata. However, this wasn't the case for the copy loader as that loader is a special-case that doesn't behave like other loaders. This release adds the entryPoint field in this case.

  • Source mappings may now contain null entries (#​3310, #​3878)

    With this change, sources that result in an empty source map may now emit a null source mapping (i.e. one with a generated position but without a source index or original position). This change improves source map accuracy by fixing a problem where minified code from a source without any source mappings could potentially still be associated with a mapping from another source file earlier in the generated output on the same minified line. It manifests as nonsensical files in source mapped stack traces. Now the null mapping "resets" the source map so that any lookups into the minified code without any mappings resolves to null (which appears as the output file in stack traces) instead of the incorrect source file.

    This change shouldn't affect anything in most situations. I'm only mentioning it in the release notes in case it introduces a bug with source mapping. It's part of a work-in-progress future feature that will let you omit certain unimportant files from the generated source map to reduce source map size.

  • Avoid using the parent directory name for determinism (#​3998)

    To make generated code more readable, esbuild includes the name of the source file when generating certain variable names within the file. Specifically bundling a CommonJS file generates a variable to store the lazily-evaluated module initializer. However, if a file is named index.js (or with a different extension), esbuild will use the name of the parent directory instead for a better name (since many packages have files all named index.js but have unique directory names).

    This is problematic when the bundle entry point is named index.js and the parent directory name is non-deterministic (e.g. a temporary directory created by a build script). To avoid non-determinism in esbuild's output, esbuild will now use index instead of the parent directory in this case. Specifically this will happen if the parent directory is equal to esbuild's outbase API option, which defaults to the lowest common ancestor of all user-specified entry point paths.

  • Experimental support for esbuild on NetBSD (#​3974)

    With this release, esbuild now has a published binary executable for NetBSD in the @esbuild/netbsd-arm64 npm package, and esbuild's installer has been modified to attempt to use it when on NetBSD. Hopefully this makes installing esbuild via npm work on NetBSD. This change was contributed by @​bsiegert.

    ⚠️ Note: NetBSD is not one of Node's supported platforms, so installing esbuild may or may not work on NetBSD depending on how Node has been patched. This is not a problem with esbuild. ⚠️

v0.24.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.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#​3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
    cd esbuild
    go build ./cmd/esbuild
    ./esbuild --version
    
  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#​3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#​3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#​3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#​3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

express-rate-limit/express-rate-limit (express-rate-limit)

v7.5.0

Compare Source

Added
  • Implemented the combined RateLimit header according to the eighth draft of the IETF RateLimit header specificiation. Enable by setting standardHeaders: 'draft-8'.
  • Added a new identifier option, used as the name for the quota policy in the draft-8 headers.
  • Added a new headersDraftVersion validation check to identifies cases where an unsupported version string is passed to the standardHeaders option.

You can view the full changelog here.

v7.4.1

Compare Source

You can view the changelog here.

yyx990803/launch-editor (launch-editor)

v2.9.1

Compare Source

v2.9.0

Compare Source

v2.8.2

Compare Source

bahmutov/start-server-and-test (start-server-and-test)

v2.0.9

Compare Source

Bug Fixes

v2.0.8

Compare Source

v2.0.7

Compare Source

Bug Fixes

v2.0.6

Compare Source

Bug Fixes
  • deps: update dependency debug to v4.3.7 (78c6f53)
yarnpkg/berry (yarn)

v3.8.7

Compare Source

v3.8.6

Compare Source


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
Copy link
Contributor Author

renovate bot commented Sep 5, 2024

⚠️ 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.1) 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.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21609
    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.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21609:11)
    at async fetchAsJson (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21623:20)
    ... 4 lines matching cause stack trace ...
    at async Object.runMain (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23102:5) {
  [cause]: TypeError: globalThis.fetch is not a function
      at fetch (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21603:33)
      at async fetchAsJson (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21623:20)
      at async fetchLatestStableVersion (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21550:20)
      at async fetchLatestStableVersion2 (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21672:14)
      at async Engine.getDefaultVersion (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22298:23)
      at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22396:47)
      at async Object.runMain (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23102:5)
}

File name: docs/nuxt/yarn.lock
/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21609
    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.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21609:11)
    at async fetchAsJson (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21623:20)
    ... 4 lines matching cause stack trace ...
    at async Object.runMain (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23102:5) {
  [cause]: TypeError: globalThis.fetch is not a function
      at fetch (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21603:33)
      at async fetchAsJson (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21623:20)
      at async fetchLatestStableVersion (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21550:20)
      at async fetchLatestStableVersion2 (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21672:14)
      at async Engine.getDefaultVersion (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22298:23)
      at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22396:47)
      at async Object.runMain (/opt/containerbase/tools/corepack/0.30.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23102:5)
}

Copy link

changeset-bot bot commented Sep 5, 2024

⚠️ No Changeset found

Latest commit: 89dfce5

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 Sep 5, 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.


🪧 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 3 times, most recently from a88292b to 83165f1 Compare December 20, 2024 06:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 83165f1 to 89dfce5 Compare December 20, 2024 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants