Skip to content

fix(deps): update all dependencies #186

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
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix(deps): update all dependencies #186

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 4, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@typescript-eslint/eslint-plugin (source) 8.37.0 -> 8.38.0 age adoption passing confidence devDependencies minor
@typescript-eslint/parser (source) 8.37.0 -> 8.38.0 age adoption passing confidence devDependencies minor
esbuild 0.25.6 -> 0.25.8 age adoption passing confidence devDependencies patch
eslint-config-prettier 10.1.5 -> 10.1.8 age adoption passing confidence devDependencies patch
github.com/aperturerobotics/protobuf-go-lite v0.9.1 -> v0.10.0 age adoption passing confidence require minor
github.com/evanw/esbuild v0.25.6 -> v0.25.8 age adoption passing confidence require patch
github.com/golangci/golangci-lint/v2 v2.2.2 -> v2.3.0 age adoption passing confidence require minor
github/codeql-action v3.29.2 -> v3.29.4 age adoption passing confidence action patch

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v8.38.0

Compare Source

🩹 Fixes
  • disallow extra properties in rule options (#​11397)
  • eslint-plugin: [consistent-generic-constructors] resolve conflict with isolatedDeclarations if enabled in constructor option (#​11351)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v8.38.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

evanw/esbuild (esbuild)

v0.25.8

Compare Source

  • Fix another TypeScript parsing edge case (#​4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

    class CachedDict {
  #has = (a: string) => dict.has(a);
  has = window
    ? (word: string): boolean => this.#has(word)
    : this.#has;
}

  • Fix a regression with the parsing of source phase imports

    The change in the previous release to parse source phase imports failed to properly handle the following cases:

    import source from 'bar'
import source from from 'bar'
import source type foo from 'bar'

    Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

v0.25.7

Compare Source

  • Parse and print JavaScript imports with an explicit phase (#​4238)

    This release adds basic syntax support for the defer and source import phases in JavaScript:

    • defer

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

      import defer * as foo from "<specifier>";
const bar = await import.defer("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

    • source

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

      import source foo from "<specifier>";
const bar = await import.source("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer * as foo from "<specifier>" or import defer { foo } from "<specifier>".

    This change only adds support for this syntax. These imports cannot currently be bundled by esbuild. To use these new features with esbuild's bundler, the imported paths must be external to the bundle and the output format must be set to esm.

  • Support optionally emitting absolute paths instead of relative paths (#​338, #​2082, #​3023)

    This release introduces the --abs-paths= feature which takes a comma-separated list of situations where esbuild should use absolute paths instead of relative paths. There are currently three supported situations: code (comments and string literals), log (log message text and location info), and metafile (the JSON build metadata).

    Using absolute paths instead of relative paths is not the default behavior because it means that the build results are no longer machine-independent (which means builds are no longer reproducible). Absolute paths can be useful when used with certain terminal emulators that allow you to click on absolute paths in the terminal text and/or when esbuild is being automatically invoked from several different directories within the same script.

  • Fix a TypeScript parsing edge case (#​4241)

    This release fixes an edge case with parsing an arrow function in TypeScript with a return type that's in the middle of a ?: ternary operator. For example:

    x = a ? (b) : c => d;
y = a ? (b) : c => d : e;

    The : token in the value assigned to x pairs with the ? token, so it's not the start of a return type annotation. However, the first : token in the value assigned to y is the start of a return type annotation because after parsing the arrow function body, it turns out there's another : token that can be used to pair with the ? token. This case is notable as it's the first TypeScript edge case that esbuild has needed a backtracking parser to parse. It has been addressed by a quick hack (cloning the whole parser) as it's a rare edge case and esbuild doesn't otherwise need a backtracking parser. Hopefully this is sufficient and doesn't cause any issues.

  • Inline small constant strings when minifying

    Previously esbuild's minifier didn't inline string constants because strings can be arbitrarily long, and this isn't necessarily a size win if the string is used more than once. Starting with this release, esbuild will now inline string constants when the length of the string is three code units or less. For example:

    // Original code
const foo = 'foo'
console.log({ [foo]: true })

// Old output (with --minify --bundle --format=esm)
var o="foo";console.log({[o]:!0});

// New output (with --minify --bundle --format=esm)
console.log({foo:!0});

    Note that esbuild's constant inlining only happens in very restrictive scenarios to avoid issues with TDZ handling. This change doesn't change when esbuild's constant inlining happens. It only expands the scope of it to include certain string literals in addition to numeric and boolean literals.

prettier/eslint-config-prettier (eslint-config-prettier)

v10.1.8

Compare Source

eslint-config-prettier

10.1.5

Patch Changes

10.1.4

Patch Changes

10.1.3

Patch Changes

10.1.2

Patch Changes

10.1.1

Patch Changes

  • #​309 eb56a5e Thanks @​JounQin! - fix: separate the /flat entry for compatibility

    For flat config users, the previous "eslint-config-prettier" entry still works, but "eslint-config-prettier/flat" adds a new name property for config-inspector, we just can't add it for the default entry for compatibility.

    See also #​308

    // before
import eslintConfigPrettier from "eslint-config-prettier";

// after
import eslintConfigPrettier from "eslint-config-prettier/flat";

10.1.0

Minor Changes

10.0.3

Patch Changes

10.0.2

Patch Changes

10.0.0

Major Changes

Versions before 10.0.0

Version 9.1.0 (2023-12-02)
Version 9.0.0 (2023-08-05)
  • Added: The CLI helper tool now works with eslint.config.js (flat config). Just like ESLint itself, the CLI tool automatically first tries eslint.config.js and then eslintrc, and you can force which one to use by setting the ESLINT_USE_FLAT_CONFIG environment variable. Note that the config of eslint-config-prettier has always been compatible with eslint.config.js (flat config) – it was just the CLI tool that needed updating. On top of that, the docs have been updated to mention how to use both eslint.config.js (flat config) and eslintrc, and the tests now test both config systems.
  • Changed: unicode-bom is no longer turned off. Prettier preserves the BOM if you have one, and does not add one if missing. It was wrong of eslint-config-prettier to disable that rule. If you get ESLint errors after upgrading, either add "unicode-bom": "off" to your config to disable it again, or run ESLint with --fix to fix all files according to the rule (add or remove BOM). Thanks to Nicolas Stepien (@​nstepien)!
Version 8.10.0 (2023-08-03)
Version 8.9.0 (2023-07-27)
Version 8.8.0 (2023-03-20)
Version 8.7.0 (2023-03-06)
Version 8.6.0 (2023-01-02)
Version 8.5.0 (2022-03-02)
Version 8.4.0 (2022-02-19)
Version 8.3.0 (2021-04-24)
Version 8.2.0 (2021-04-13)
Version 8.1.0 (2021-02-24)
Version 8.0.0 (2021-02-21)

  • Changed: All configs have been merged into one!

    To upgrade, change:

    {
  "extends": [
    "some-other-config-you-use",
    "prettier",
    "prettier/@&#8203;typescript-eslint",
    "prettier/babel",
    "prettier/flowtype",
    "prettier/react",
    "prettier/standard",
    "prettier/unicorn",
    "prettier/vue"
  ]
}

    Into:

    {
  "extends": [
    "some-other-config-you-use",
    "prettier"
  ]
}

    The "prettier" config now includes not just ESLint core rules, but also rules from all plugins. Much simpler!

    So … what’s the catch? Why haven’t we done this earlier? Turns out it’s just a sad mistake. I (@​lydell) was confused when testing, and thought that turning off unknown rules in a config was an error. Thanks to Georgii Dolzhykov (@​thorn0) for pointing this out!

    If you use eslint-plugin-prettier, all you need is plugin:prettier/recommended:

    {
  "extends": [
    "some-other-config-you-use",
    "plugin:prettier/recommended"
  ]
}

    (The "prettier/prettier" config still exists separately. It’s the odd one out. The main "prettier" config does not include the rules from it.)

  • Changed: The CLI helper tool now only prints warnings for arrow-body-style and prefer-arrow-callback, just like other “special rules.” This means that if you’ve decided to use those rules and eslint-plugin-prettier at the same time, you’ll get warnings but exit code zero (success).

Version 7.2.0 (2021-01-18)
Version 7.1.0 (2020-12-19)
Version 7.0.0 (2020-12-05)

  • Changed: At least ESLint 7.0.0 is now required.

  • Changed: arrow-body-style and prefer-arrow-callback are no longer turned off by default. They only need to be turned off if you use eslint-plugin-prettier. If you do, add "prettier/prettier" to your "extends" array to turn them off again.

    {
  "extends": ["prettier", "prettier/prettier"],
  "plugins": ["prettier"],
  "rules": {
    "prettier/prettier": "error"
  }
}

    Alternatively, update eslint-plugin-prettier to version 3.2.0 or later which automatically turns off these two rules in its "plugin:prettier/recommended" config.

    The CLI helper tool only warns about these rules if you have the "prettier/prettier" rule enabled for a file.

  • Changed: no-tabs is now a validatable rule. If you use it, you should enable allowIndentationTabs so that the rule works regardless of your Prettier config:

    {
  "rules": {
    "no-tabs": ["error", { "allowIndentationTabs": true }]
  }
}

  • Changed: The CLI helper tool is now called just eslint-config-prettier instead of eslint-config-prettier-check. This is so that npx eslint-config-prettier always works regardless of whether you have already installed eslint-config-prettier or not: If you have, the local installation is used; if you haven’t, npx downloads a temporary copy.

  • Changed: The CLI helper tool no longer requires you to pipe the output of eslint --print-config to it. Instead, it does that automatically for you via ESLint API:s added in ESLint v7.

    Before:

    npx eslint --print-config index.js | npx eslint-config-prettier-check

    After:

    npx eslint-config-prettier index.js

  • Improved: The npm package is now 75% smaller.

Version 6.15.0 (2020-10-27)
Version 6.14.0 (2020-10-21)
Version 6.13.0 (2020-10-16)
Version 6.12.0 (2020-09-25)
Version 6.11.0 (2020-04-21)
Version 6.10.1 (2020-03-22)
  • Improved: Recommend using npx when running the CLI helper tool.
  • Updated: Mention that eslint-config-prettier has been tested with Prettier 2.0 and the latest versions of plugins.
Version 6.10.0 (2020-01-28)
Version 6.9.0 (2019-12-27)
Version 6.8.0 (2019-12-25)
Version 6.7.0 (2019-11-19)
Version 6.6.0 (2019-11-17)
Version 6.5.0 (2019-10-26)
Version 6.4.0 (2019-10-05)
Version 6.3.0 (2019-09-10)
Version 6.2.0 (2019-09-03)
Version 6.1.0 (2019-08-19)
Version 6.0.0 (2019-06-25)

  • Changed: The CLI helper tool now considers no-confusing-arrow to conflict if you use the default value of its allowParens option. The default was changed to true in ESLint 6, which conflicts with Prettier.

    If the CLI helper tool gives you errors about this after upgrading, the solution is to change this:

    {
  "rules": {
    "no-confusing-arrow": ["error"]
  }
}

    Into this:

    {
  "rules": {
    "no-confusing-arrow": ["error", { "allowParens": false }]
  }
}

    The latter works in both ESLint 6 as well as in ESLint 5 and older.

  • Improved: eslint --print-config usage instructions. The CLI tool help text as well as the documentation has been updated to suggest commands that work in ESLint 6.0 as well as in ESLint 5 and older. (Instead of eslint --print-config ., use eslint --print-config path/to/main.js.)

Version 5.1.0 (2019-06-25)
Version 5.0.0 (2019-06-15)

  • Removed: react/self-closing-comp. This rule was added in v4.1.0 not because it conflicted with Prettier but because it was unnecessary when using Prettier. However, in v1.18.0 Prettier stopped converting empty elements to self-closing elements. So the rule is not unnecessary anymore.

    If you use Prettier v1.17.1 or older you should be able to upgrade eslint-config-prettier to v5.0.0 without having to do anything else.

    If you use Prettier v1.18.0 or newer, you might get lint errors about for example changing <div></div> into <div />. You have two options:

    • Run eslint --fix if you prefer to enforce self-closing elements where possible. This should fix all the errors.
    • Add "react/self-closing-comp": "off" to your ESLint config if you use autofix from your editor and you face the same issue as Prettier did.

  • Changed: Node.js 6 is no longer officially supported, but v5.0.0 should still work with it.

Version 4.3.0 (2019-05-16)
Version 4.2.0 (2019-04-25)
Version 4.1.0 (2019-02-26)
Version 4.0.0 (2019-01-26)
  • Breaking change: Support for eslint-plugin-typescript has been removed and replaced with support for its successor @​typescript-eslint/eslint-plugin. Thanks to TANIGUCHI Masaya (@​ta2gch) and everyone else who helped with this!
  • Changed: arrow-body-style and prefer-arrow-callback are now marked as special rules, since they might cause problems if using eslint-plugin-prettier and --fix. They are turned off by default, and the CLI helper tool will warn about them (but not error if you do enable them). This won’t break your linting checks, but do note that these rules will be disabled unless you explicitly enable them again, and that you might see new warnings when running the CLI helper tool.
Version 3.6.0 (2019-01-19)
Version 3.5.0 (2019-01-16)
  • Fixed: The eslint-plugin-vue change from 3.4.0 has been reverted. That change requires eslint-plugin-vue@5, while many use eslint-plugin-vue@4. In other words, it was an accidental breaking change. Also, after thinking about it some more, it makes sense to have a Prettier-specific list of rules, rather than using the vue/no-layout-rules list, since there can be layout rules that don’t conflict with but rather complement Prettier.
  • Added: New eslint-plugin-vue rules coming in the next version after 5.1.0.
Version 3.4.0 (2019-01-13)
  • Added: Support for eslint-plugin-typescript. Thanks to Jed Fox (@​j-f1)!
  • Improved: The eslint-plugin-vue integration is now using the vue/no-layout-rules config behind the scenes, so it should automatically stay up-to-date when new eslint-plugin-vue versions are released. Thanks to Michał Sajnóg (@​michalsnik)!
Version 3.3.0 (2018-11-11)
Version 3.2.0 (2018-11-10)
  • Added: Support for eslint-plugin-vue.
  • Fixed: The CLI helper tool should now work in Node.js 6 with npm 3 again. Thanks to Grant Snodgrass (@​meeber)!
  • Improved: Updated documentation.
Version 3.1.0 (2018-09-22)
Version 3.0.1 (2018-08-13)
  • Improved: eslint --print-config usage instructions.
Version 3.0.0 (2018-08-13)
  • Breaking change: Dropped Node.js 4 support.
Version 2.10.0 (2018-08-13)
Version 2.9.0 (2017-11-26)
Version 2.8.0 (2017-11-19)
Version 2.7.0 (2017-11-01)
Version 2.6.0 (2017-09-23)
Version 2.5.0 (2017-09-16)
Version 2.4.0 (2017-09-02)
Version 2.3.0 (2017-06-30)
Version 2.2.0 (2017-06-17)
Version 2.1.1 (2017-05-20)
  • No code changes. Just updates to the readme.
Version 2.1.0 (2017-05-13)
Version 2.0.0 (2017-05-07)

  • Changed/Improved: The CLI helper tool is now more helpful.

    • The options of special rules are now validated if possible. If a special rule is enabled with non-conflicting options, the CLI no longer warns about it.
    • If only special rules that cannot be automatically checked are found, the CLI no longer exists with a non-zero exit code. Instead, it only warns about the rules.

  • Changed: The no-confusing-arrow is now a special rule again, since it might conflict with recent Prettier versions.

  • Removed: The react/wrap-multilines rule (which has been deprecated for a while), since it was removed in eslint-plugin-react@7.

Version 1.7.0 (2017-04-19)
  • Changed: The no-confusing-arrow is no longer a special rule, but simply turned off, since recent Prettier versions make it redundant.
  • Improved: The CLI helper tool now has a more helpful message for special rules, and exits with a different status code if only special rules were found. The exit codes are now documented as well.
Version 1.6.0 (2017-04-05)
Version 1.5.0 (2017-03-04)
Version 1.4.1 (2017-02-28)
  • Improved: eslint-config-prettier is now part of the prettier organization! This version updates all URLs to point to the new home of the project.
Version 1.4.0 (2017-02-26)
Version 1.3.0 (2017-02-21)
Version 1.2.0 (2017-02-14)
Version 1.1.1 (2017-02-12)
  • Minor documentation tweak: Changed "Exceptions" into "Special rules".
Version 1.1.0 (2017-02-10)
  • Fixed: The eslint-plugin-react exclusion rules now actually work.
  • Fixed: The CLI helper tool now works in Node.js 4. Thanks to Nathan Friedly (@​nfriedly)!
  • Added: Support for eslint-plugin-flowtype.
  • Improved: Minor things for the CLI helper tool.
  • Improved: There are now tests for everything.
Version 1.0.3 (2017-02-03)
  • Fixed: "extends": "prettier/react" now actually works.
Version 1.0.2 (2017-01-30)
  • Improved: CLI helper tool instructions.
Version 1.0.1 (2017-01-29)
  • No difference from 1.0.0. Just an npm publish mistake.
Version 1.0.0 (2017-01-29)
  • Initial release.
aperturerobotics/protobuf-go-lite (github.com/aperturerobotics/protobuf-go-lite)

v0.10.0

Compare Source

golangci/golangci-lint (github.com/golangci/golangci-lint/v2)

v2.3.0

Compare Source

  1. Linters new features or changes
    • ginkgolinter: from 0.19.1 to 0.20.0 (new option: force-assertion-description)
    • iface: from 1.4.0 to 1.4.1 (report message improvements)
    • noctx: from 0.3.4 to 0.3.5 (new detections: log/slog, exec, crypto/tls)
    • revive: from 1.10.0 to 1.11.0 (new rule: enforce-switch-style)
    • wsl: from 5.0.0 to 5.1.0
  2. Linters bug fixes
    • gosec: from 2.22.5 to 2.22.6
    • noinlineerr: from 1.0.4 to 1.0.5
    • sloglint: from 0.11.0 to 0.11.1
  3. Misc.
    • fix: panic close of closed channel
github/codeql-action (github/codeql-action)

v3.29.4

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

3.29.4 - 23 Jul 2025

No user facing changes.

See the full CHANGELOG.md for more information.

v3.29.3

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

3.29.3 - 21 Jul 2025

No user facing changes.

See the full CHANGELOG.md for more information.

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 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 force-pushed the renovate/all branch 10 times, most recently from 696e194 to bb45447 Compare March 10, 2025 19:49
@renovate renovate bot force-pushed the renovate/all branch 10 times, most recently from ec3c091 to fbb3f3d Compare March 17, 2025 22:37
@renovate renovate bot force-pushed the renovate/all branch 9 times, most recently from e54b752 to 681271d Compare March 25, 2025 23:37
@renovate renovate bot force-pushed the renovate/all branch from b0e9398 to 23437bd Compare July 6, 2025 01:06
@renovate renovate bot changed the title fix(deps): update all dependencies fix(deps): update all dependencies - autoclosed Jul 6, 2025
@renovate renovate bot closed this Jul 6, 2025
@renovate renovate bot changed the title fix(deps): update all dependencies - autoclosed fix(deps): update all dependencies Jul 7, 2025
@renovate renovate bot reopened this Jul 7, 2025
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 08ab830 to 4cc43d0 Compare July 11, 2025 23:36
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from f8dff6c to b0bb318 Compare July 17, 2025 03:43
@renovate renovate bot changed the title fix(deps): update all dependencies fix(deps): update all dependencies - autoclosed Jul 17, 2025
@renovate renovate bot closed this Jul 17, 2025
@renovate renovate bot changed the title fix(deps): update all dependencies - autoclosed fix(deps): update all dependencies Jul 18, 2025
@renovate renovate bot reopened this Jul 18, 2025
@renovate renovate bot changed the title fix(deps): update all dependencies chore(deps): update dependency eslint-config-prettier to v10.1.7 Jul 18, 2025
@renovate renovate bot changed the title chore(deps): update dependency eslint-config-prettier to v10.1.7 chore(deps): update dependency eslint-config-prettier to v10.1.8 Jul 18, 2025
@renovate renovate bot changed the title chore(deps): update dependency eslint-config-prettier to v10.1.8 fix(deps): update all dependencies Jul 19, 2025
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from c424bc9 to 4533752 Compare July 21, 2025 23:51
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jul 21, 2025

ℹ Artifact update notice

File name: tools/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 13 additional dependencies were updated

Details:

Package Change
github.com/AlwxSin/noinlineerr v1.0.4 -> v1.0.5
github.com/bombsimon/wsl/v5 v5.0.0 -> v5.1.0
github.com/go-viper/mapstructure/v2 v2.3.0 -> v2.4.0
github.com/mgechev/revive v1.10.0 -> v1.11.0
github.com/nunnatsa/ginkgolinter v0.19.1 -> v0.20.0
github.com/securego/gosec/v2 v2.22.5 -> v2.22.6
github.com/sonatard/noctx v0.3.4 -> v0.3.5
github.com/spf13/pflag v1.0.6 -> v1.0.7
github.com/uudashr/iface v1.4.0 -> v1.4.1
go-simpler.org/sloglint v0.11.0 -> v0.11.1
golang.org/x/crypto v0.39.0 -> v0.40.0
golang.org/x/exp/typeparams v0.0.0-20250210185358-939b2ce775ac -> v0.0.0-20250620022241-b7579e27df2b
golang.org/x/text v0.26.0 -> v0.27.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

Copilot code review Copilot Copilot left review comments

Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

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