wails
wails copied to clipboard
Bump the npm_and_yarn group across 16 directories with 11 updates
Bumps the npm_and_yarn group with 1 update in the /v2/examples/customlayout/myfrontend directory: vite. Bumps the npm_and_yarn group with 5 updates in the /v2/internal/frontend/runtime directory:
| Package | From | To |
|---|---|---|
| vite | 3.2.10 |
7.1.2 |
| vitest | 0.24.3 |
3.2.4 |
| esbuild | 0.15.12 |
0.25.0 |
| brace-expansion | 1.1.11 |
1.1.12 |
| form-data | 2.5.1 |
2.5.5 |
Bumps the npm_and_yarn group with 2 updates in the /v2/internal/frontend/runtime/dev directory: esbuild and brace-expansion. Bumps the npm_and_yarn group with 1 update in the /v2/pkg/templates/templates/lit-ts/frontend directory: vite. Bumps the npm_and_yarn group with 1 update in the /v2/pkg/templates/templates/lit/frontend directory: vite. Bumps the npm_and_yarn group with 1 update in the /v2/pkg/templates/templates/preact-ts/frontend directory: vite. Bumps the npm_and_yarn group with 1 update in the /v2/pkg/templates/templates/preact/frontend directory: vite. Bumps the npm_and_yarn group with 1 update in the /v2/pkg/templates/templates/react-ts/frontend directory: vite. Bumps the npm_and_yarn group with 1 update in the /v2/pkg/templates/templates/react/frontend directory: vite. Bumps the npm_and_yarn group with 1 update in the /v2/pkg/templates/templates/svelte-ts/frontend directory: vite. Bumps the npm_and_yarn group with 1 update in the /v2/pkg/templates/templates/svelte/frontend directory: vite. Bumps the npm_and_yarn group with 1 update in the /v2/pkg/templates/templates/vanilla-ts/frontend directory: vite. Bumps the npm_and_yarn group with 1 update in the /v2/pkg/templates/templates/vanilla/frontend directory: vite. Bumps the npm_and_yarn group with 1 update in the /v2/pkg/templates/templates/vue-ts/frontend directory: vite. Bumps the npm_and_yarn group with 1 update in the /v2/pkg/templates/templates/vue/frontend directory: vite. Bumps the npm_and_yarn group with 8 updates in the /website directory:
| Package | From | To |
|---|---|---|
| brace-expansion | 1.1.11 |
1.1.12 |
| form-data | 4.0.0 |
4.0.4 |
| @babel/helpers | 7.24.7 |
7.28.2 |
| @babel/runtime-corejs3 | 7.24.7 |
7.28.2 |
| @babel/runtime | 7.24.7 |
7.28.2 |
| http-proxy-middleware | 2.0.6 |
2.0.9 |
| image-size | 1.1.1 |
1.2.1 |
| prismjs | 1.29.0 |
1.30.0 |
Updates vite from 3.2.11 to 7.1.2
Release notes
Sourced from vite's releases.
v7.1.2
Please refer to CHANGELOG.md for details.
v7.1.1
Please refer to CHANGELOG.md for details.
[email protected]
Please refer to CHANGELOG.md for details.
[email protected]
Please refer to CHANGELOG.md for details.
[email protected]
Please refer to CHANGELOG.md for details.
v7.1.0
Please refer to CHANGELOG.md for details.
v7.1.0-beta.1
Please refer to CHANGELOG.md for details.
v7.1.0-beta.0
Please refer to CHANGELOG.md for details.
v7.0.6
Please refer to CHANGELOG.md for details.
v7.0.5
Please refer to CHANGELOG.md for details.
v7.0.4
Please refer to CHANGELOG.md for details.
v7.0.3
Please refer to CHANGELOG.md for details.
[email protected]
Please refer to CHANGELOG.md for details.
v7.0.2
Please refer to CHANGELOG.md for details.
[email protected]
Please refer to CHANGELOG.md for details.
v7.0.1
Please refer to CHANGELOG.md for details.
[email protected]
Please refer to CHANGELOG.md for details.
... (truncated)
Changelog
Sourced from vite's changelog.
7.1.2 (2025-08-12)
Bug Fixes
- client: add
[vite]prefixes to debug logs (#20595) (7cdef61)- config: make debugger work with bundle loader (#20573) (c583927)
- deps: update all non-major dependencies (#20587) (20d4817)
- don't consider ids with
npm:prefix as a built-in module (#20558) (ab33803)- hmr: watch non-inlined assets referenced by CSS (#20581) (b7d494b)
- module-runner: prevent crash when sourceMappingURL pattern appears in string literals (#20554) (2770478)
Miscellaneous Chores
- deps: migrate to
@jridgewell/remappingfrom@ampproject/remapping(#20577) (0a6048a)- deps: update rolldown-related dependencies (#20586) (77632c5)
7.1.1 (2025-08-08)
Bug Fixes
Miscellaneous Chores
7.1.0 (2025-08-07)
Features
- support files with more than 1000 lines by
generateCodeFrame(#20508) (e7d0b2a)- add
import.meta.mainsupport in config (bundle config loader) (#20516) (5d3e3c2)- optimizer: improve dependency optimization error messages with esbuild formatMessages (#20525) (d17cfed)
- ssr: add
import.meta.mainsupport for Node.js module runner (#20517) (794a8f2)- add
future: 'warn'(#20473) (e6aaf17)- add
removeServerPluginContainerfuture deprecation (#20437) (c1279e7)- add
removeServerReloadModulefuture deprecation (#20436) (6970d17)- add
server.warmupRequestto future deprecation (#20431) (8ad388a)- add
ssrFixStacktrace/ssrRewriteStacktracetoremoveSsrLoadModulefuture deprecation (#20435) (8c8f587)- client: ping from SharedWorker (#19057) (5c97c22)
- dev: add
this.fssupport (#20301) (0fe3f2f)- export
defaultExternalConditions(#20279) (344d302)- implement
removePluginHookSsrArgumentfuture deprecation (#20433) (95927d9)- implement
removeServerHotfuture deprecation (#20434) (259f45d)- resolve server URLs before calling other listeners (#19981) (45f6443)
- ssr: resolve externalized packages with
resolve.externalConditionsand addmodule-syncto default external condition (#20409) (c669c52)- ssr: support
import.meta.resolvein module runner (#20260) (62835f7)Bug Fixes
... (truncated)
Commits
42de3e6release: v7.1.2b7d494bfix(hmr): watch non-inlined assets referenced by CSS (#20581)c583927fix(config): make debugger work with bundle loader (#20573)20d4817fix(deps): update all non-major dependencies (#20587)7cdef61fix(client): add[vite]prefixes to debug logs (#20595)77632c5chore(deps): update rolldown-related dependencies (#20586)0a6048achore(deps): migrate to@jridgewell/remappingfrom@ampproject/remapping...2770478fix(module-runner): prevent crash when sourceMappingURL pattern appears in st...ab33803fix: don't consider ids withnpm:prefix as a built-in module (#20558)f4438a1release: v7.1.1- Additional commits viewable in compare view
Updates vite from 3.2.10 to 7.1.2
Release notes
Sourced from vite's releases.
v7.1.2
Please refer to CHANGELOG.md for details.
v7.1.1
Please refer to CHANGELOG.md for details.
[email protected]
Please refer to CHANGELOG.md for details.
[email protected]
Please refer to CHANGELOG.md for details.
[email protected]
Please refer to CHANGELOG.md for details.
v7.1.0
Please refer to CHANGELOG.md for details.
v7.1.0-beta.1
Please refer to CHANGELOG.md for details.
v7.1.0-beta.0
Please refer to CHANGELOG.md for details.
v7.0.6
Please refer to CHANGELOG.md for details.
v7.0.5
Please refer to CHANGELOG.md for details.
v7.0.4
Please refer to CHANGELOG.md for details.
v7.0.3
Please refer to CHANGELOG.md for details.
[email protected]
Please refer to CHANGELOG.md for details.
v7.0.2
Please refer to CHANGELOG.md for details.
[email protected]
Please refer to CHANGELOG.md for details.
v7.0.1
Please refer to CHANGELOG.md for details.
[email protected]
Please refer to CHANGELOG.md for details.
... (truncated)
Changelog
Sourced from vite's changelog.
7.1.2 (2025-08-12)
Bug Fixes
- client: add
[vite]prefixes to debug logs (#20595) (7cdef61)- config: make debugger work with bundle loader (#20573) (c583927)
- deps: update all non-major dependencies (#20587) (20d4817)
- don't consider ids with
npm:prefix as a built-in module (#20558) (ab33803)- hmr: watch non-inlined assets referenced by CSS (#20581) (b7d494b)
- module-runner: prevent crash when sourceMappingURL pattern appears in string literals (#20554) (2770478)
Miscellaneous Chores
- deps: migrate to
@jridgewell/remappingfrom@ampproject/remapping(#20577) (0a6048a)- deps: update rolldown-related dependencies (#20586) (77632c5)
7.1.1 (2025-08-08)
Bug Fixes
Miscellaneous Chores
7.1.0 (2025-08-07)
Features
- support files with more than 1000 lines by
generateCodeFrame(#20508) (e7d0b2a)- add
import.meta.mainsupport in config (bundle config loader) (#20516) (5d3e3c2)- optimizer: improve dependency optimization error messages with esbuild formatMessages (#20525) (d17cfed)
- ssr: add
import.meta.mainsupport for Node.js module runner (#20517) (794a8f2)- add
future: 'warn'(#20473) (e6aaf17)- add
removeServerPluginContainerfuture deprecation (#20437) (c1279e7)- add
removeServerReloadModulefuture deprecation (#20436) (6970d17)- add
server.warmupRequestto future deprecation (#20431) (8ad388a)- add
ssrFixStacktrace/ssrRewriteStacktracetoremoveSsrLoadModulefuture deprecation (#20435) (8c8f587)- client: ping from SharedWorker (#19057) (5c97c22)
- dev: add
this.fssupport (#20301) (0fe3f2f)- export
defaultExternalConditions(#20279) (344d302)- implement
removePluginHookSsrArgumentfuture deprecation (#20433) (95927d9)- implement
removeServerHotfuture deprecation (#20434) (259f45d)- resolve server URLs before calling other listeners (#19981) (45f6443)
- ssr: resolve externalized packages with
resolve.externalConditionsand addmodule-syncto default external condition (#20409) (c669c52)- ssr: support
import.meta.resolvein module runner (#20260) (62835f7)Bug Fixes
... (truncated)
Commits
42de3e6release: v7.1.2b7d494bfix(hmr): watch non-inlined assets referenced by CSS (#20581)c583927fix(config): make debugger work with bundle loader (#20573)20d4817fix(deps): update all non-major dependencies (#20587)7cdef61fix(client): add[vite]prefixes to debug logs (#20595)77632c5chore(deps): update rolldown-related dependencies (#20586)0a6048achore(deps): migrate to@jridgewell/remappingfrom@ampproject/remapping...2770478fix(module-runner): prevent crash when sourceMappingURL pattern appears in st...ab33803fix: don't consider ids withnpm:prefix as a built-in module (#20558)f4438a1release: v7.1.1- Additional commits viewable in compare view
Updates vitest from 0.24.3 to 3.2.4
Release notes
Sourced from vitest's releases.
v3.2.4
🐞 Bug Fixes
- Use correct path for optimisation of strip-literal - by
@mrginglymusin vitest-dev/vitest#8139 (44940)- Print uint and buffer as a simple string - by
@sheremet-vain vitest-dev/vitest#8141 (b86bf)- browser:
- Show a helpful error when spying on an export - by
@sheremet-vain vitest-dev/vitest#8178 (56007)- cli:
vitest run --watchshould be watch-mode - by@AriPerkkioin vitest-dev/vitest#8128 (657e8)- Use absolute path environment on Windows - by
@colinaaain vitest-dev/vitest#8105 (85dc0)- Throw error when
--shard x/<count>exceeds count of test files - by@AriPerkkioin vitest-dev/vitest#8112 (8a18c)- coverage:
- Ignore SCSS in browser mode - by
@sheremet-vain vitest-dev/vitest#8161 (0c3be)- deps:
- Update all non-major dependencies - in vitest-dev/vitest#8123 (93f32)
- expect:
- Handle async errors in expect.soft - by
@lzl0304in vitest-dev/vitest#8145 (68699)- pool:
- Auto-adjust
minWorkerswhen onlymaxWorkersspecified - by@AriPerkkioin vitest-dev/vitest#8110 (14dc0)- reporter:
task.metashould be available in custom reporter's errors - by@AriPerkkioin vitest-dev/vitest#8115 (27df6)- runner:
- Preserve handler wrapping on extend - by
@pengooseDevin vitest-dev/vitest#8153 (a9281)- ui:
- Ensure ui config option works correctly - by
@lzl0304in vitest-dev/vitest#8147 (42eeb)View changes on GitHub
v3.2.3
🚀 Features
- browser: Use base url instead of vitest - by
@sheremet-vain vitest-dev/vitest#8126 (1d8eb)- ui: Show test annotations and metadata in the test report tab - by
@sheremet-vain vitest-dev/vitest#8093 (c69be)🐞 Bug Fixes
- Rerun tests when project's setup file is changed - by
@sheremet-vain vitest-dev/vitest#8097 (0f335)- Revert
expect.anyreturn type - by@sheremet-vain vitest-dev/vitest#8129 (47514)- Run only the name plugin last, not all config plugins - by
@sheremet-vain vitest-dev/vitest#8130 (83862)- pool:
- Throw if user's tests use
process.send()- by@AriPerkkioin vitest-dev/vitest#8125 (dfe81)- runner:
- Fast sequential task updates missing - by
@AriPerkkioin vitest-dev/vitest#8121 (7bd11)- Comments between fixture destructures - by
@AriPerkkioin vitest-dev/vitest#8127 (dc469)- vite-node:
- Unable to handle errors where sourcemap mapping empty - by
@blake-newmanand@hi-ogawain vitest-dev/vitest#8071 (8aa25)View changes on GitHub
v3.2.2
... (truncated)
Commits
c666d14chore: release v3.2.48a18c8efix(cli): throw error when--shard x/\<count>exceeds count of test files (#...8abd7ccchore(deps): updatetinypool(#8174)93f3200fix(deps): update all non-major dependencies (#8123)0c3be6ffix(coverage): ignore SCSS in browser mode (#8161)790bc31chore: update deprecation notice for globs (#8148)c0eae7dchore: update deprecated workspace file log (#8118)14dc072fix(pool): auto-adjustminWorkerswhen onlymaxWorkersspecified (#8110)85dc019fix(cli): use absolute path environment on Windows (#8105)27df68afix(reporter):task.metashould be available in custom reporter's errors (#...- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by vitestbot, a new releaser for vitest since your current version.
Updates esbuild from 0.15.12 to 0.25.0
Release notes
Sourced from esbuild's releases.
v0.25.0
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuildin yourpackage.jsonfile (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.24.0or~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-Originheader 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 is0.0.0.0, which refers to all of the IP addresses that represent the local machine (e.g. both127.0.0.1and192.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 ofhostsinstead of a singlehoststring. This makes it possible to determine all of the hosts that esbuild's development server will accept.Thanks to
@sapphi-redfor 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-wefor 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) */
... (truncated)
Changelog
Sourced from esbuild's changelog.
Changelog: 2022
This changelog documents all esbuild versions published in the year 2022 (versions 0.14.11 through 0.16.12).
0.16.12
Loader defaults to
jsfor extensionless files (#2776)Certain packages contain files without an extension. For example, the
yargspackage contains the fileyargs/yargswhich has no extension. Node, Webpack, and Parcel can all understand code that importsyargs/yargsbecause they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for""(the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:
CLI:
esbuild --bundle --loader:=cssJS:
esbuild.build({ bundle: true, loader: { '': 'css' }, })Go:
api.Build(api.BuildOptions{ Bundle: true, Loader: map[string]api.Loader{"": api.LoaderCSS}, })In addition, the
"type"field inpackage.jsonfiles now only applies to files with an explicit.js,.jsx,.ts, or.tsxextension. Previously it was incorrectly applied by esbuild to all files that had an extension other than.mjs,.mts,.cjs, or.ctsincluding extensionless files. So for example an extensionless file in a"type": "module"package is now treated as CommonJS instead of ESM.0.16.11
Avoid a syntax error in the presence of direct
eval(#2761)The behavior of nested
functiondeclarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nestedfunctiondeclarations in its output because then the behavior would depend on whether the output was run in strict mode or not instead of respecting the strict mode behavior of the original source code. To avoid this, esbuild transforms nestedfunctiondeclarations to preserve the intended behavior of the original source code regardless of whether the output is run in strict mode or not:// Original code if (true) { function foo() {} console.log(!!foo) foo = null console.log(!!foo) }
... (truncated)
Commits
e9174d6publish 0.25.0 to npmc27dbebfixhostsinplugin-tests.js6794f60fixhostsinnode-unref-tests.jsde85afdMerge commit from forkda1de1bfix #4065: bitwise operators can return bigintsf4e9d19switch case liveness:defaultis always last7aa47c3fix #4028: minify live/deadswitchcases better22ecd30minify: more constant folding for strict equality4cdf03cfix #4053: reordering of.tsxinnode_modulesdc71977fix #3692:0now picks a random ephemeral port- Additional commits viewable in compare view
Updates brace-expansion from 1.1.11 to 1.1.12
Release notes
Sourced from brace-expansion's releases.
v1.1.12
- pkg: publish on tag 1.x c460dbd
- fmt ccb8ac6
- Fix potential ReDoS Vulnerability or Inefficient Regular Expression (#65) c3c73c8
https://github.com/juliangruber/brace-expansion/compare/v1.1.11...v1.1.12
Commits
Updates form-data from 2.5.1 to 2.5.5
Release notes
Sourced from form-data's releases.
v2.5.2
Fixes
Buffer.fromandBuffer.allocrequire node 4+- npmignore temporary build files (#532)
- move util.isArray to Array.isArray (#564)
Tests
- migrate from travis to GHA
Changelog
Sourced from form-data's changelog.
v2.5.5 - 2025-07-18
Commits
- [meta] actually ensure the readme backup isn’t published
10626c0- [Fix] use proper dependency
026abe5v2.5.4 - 2025-07-17
Fixed
- [Fix]
append: avoid a crash on nullish values[#577](https://github.com/form-data/form-data/issues/577)Commits
- [eslint] update linting config
8bf2492- [meta] add
auto-changelogb5101ad- [Tests] handle predict-v8-randomness failures in node < 17 and node > 23
0e93122- [Fix] Switch to using
cryptorandom for boundary valuesb88316c- [Fix] validate boundary type in
setBoundary()method131ae5e- [Tests] Switch to newer v8 prediction library; enable node 24 testing
c97cfbe- [Refactor] use
hasown97ac9c2- [meta] remove local commit hooks
be99d4e- [Dev Deps] remove unused deps
ddbc89b- [meta] fix scripts to use prepublishOnly
e351a97- [Dev Deps] remove unused script
8f23366- [Dev Deps] add missing peer dep
02ff026- [meta] fix readme capitalization
2fd5f61v2.5.3 - 2025-02-14
Merged
- [Fix] set
Symbol.toStringTagwhen available[#573](https://github.com/form-data/form-data/issues/573)Fixed
- [Fix] set
Symbol.toStringTagwhen available (#573)[#396](https://github.com/form-data/form-data/issues/396)Commits
- [Refactor] use
Object.prototype.hasOwnProperty.call6e682d4- [Dev Deps] update
@types/node,browserify,coveralls,eslint,formidable,in-publish,phantomjs-prebuilt,pkgfiles,pre-commit,request,tape,typescript819f6b7- Only apps should have lockfiles
b170ee2- [Deps] update
combined-stream,mime-types6b1ca1d- Bumped version 2.5.3
9457283- [Dev Deps] pin
requestwhich viatough-cookie^2.4 depends onpsl9dbe192v2.5.2 - 2024-10-10
... (truncated)
Commits
40de5a7v2.5.5026abe5[Fix] use proper dependency10626c0[meta] actually ensure the readme backup isn’t publishedefe6c26v2.5.4c97cfbe[Tests] Switch to newer v8 prediction library; enable node 24 testing0e93122[Tests] handle predict-v8-randomness failures in node < 17 and node > 23b88316c[Fix] Switch to usingcryptorandom for boundary valuesb70869d[Fix]append: avoid a crash on nullish values131ae5e[Fix] validate boundary type insetBoundary()method8bf2492[eslint] update linting config- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by ljharb, a new releaser for form-data since your current version.
Updates esbuild from 0.12.21 to 0.25.8
Release notes
Sourced from esbuild's releases.
v0.25.0
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuildin yourpackage.jsonfile (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.24.0or~0.24.0. See npm's documentation about
[!IMPORTANT]
Review skipped
Bot user detected.
To trigger a single review, invoke the
@coderabbitai reviewcommand.You can disable this status message by setting the
reviews.review_statustofalsein 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.Open a follow-up GitHub issue for this discussion.
- Files and specific lines of code (under the "Files changed" tab): Tag
@coderabbitaiin a new review comment at the desired location with your query. - PR comments: Tag
@coderabbitaiin 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
Support
Need help? Join our Discord community for assistance with any issues or questions.
CodeRabbit Commands (Invoked using PR/Issue comments)
Type @coderabbitai help to get the list of available commands.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
CodeRabbit Configuration File (.coderabbit.yaml)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yamlfile 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
Status, Documentation and Community
- Visit our Status Page to check the current availability of CodeRabbit.
- 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.
Quality Gate passed
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code