chore(deps)(deps-dev): bump the dev-dependencies group with 3 updates

[dependabot]

Bumps the dev-dependencies group with 3 updates: @biomejs/biome, @effect/language-service and drizzle-kit.

Updates @biomejs/biome from 2.3.4 to 2.3.7

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.3.7

2.3.7

Patch Changes

• #8169 7fdcec8 Thanks @​arendjr! - Fixed #7999: Correctly place await after leading comment in auto-fix action from noFloatingPromises rule.

• #8157 12d5b42 Thanks @​Conaclos! - Fixed #8148. noInvalidUseBeforeDeclaration no longer reports some valid use before declarations.

  The following code is no longer reported as invalid:

  class classA {
    C = C;
  }
  const C = 0;

• #8178 6ba4157 Thanks @​dyc3! - Fixed #8174, where the HTML parser would parse 2 directives as a single directive because it would not reject whitespace in Vue directives. This would cause the formatter to erroneously merge the 2 directives into one, resulting in broken code.

  - <Component v-else:property="123" />
  + <Component v-else :property="123" />

• #8088 0eb08e8 Thanks @​db295! - Fixed #7876: The noUnusedImports rule now ignores imports that are used by @​linkcode and @​linkplain (previously supported @​link and @​see).

  The following code will no longer be a false positive:

  import type { a } from "a"
  /**
  
  {@​linkcode a}
  */
  function func() {}

#8119 8d64655 Thanks @​ematipico! - Improved the detection of the rule noUnnecessaryConditions. Now the rule isn't triggered for variables that are mutated inside a module.

This logic deviates from the original rule, hence noUnnecessaryConditions is now marked as "inspired".

In the following example, hey starts as false, but then it's assigned to a string. The rule isn't triggered inside the if check.

let hey = false;
function test() {
hey = "string";

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.3.7

Patch Changes

• #8169 7fdcec8 Thanks @​arendjr! - Fixed #7999: Correctly place await after leading comment in auto-fix action from noFloatingPromises rule.

• #8157 12d5b42 Thanks @​Conaclos! - Fixed #8148. noInvalidUseBeforeDeclaration no longer reports some valid use before declarations.

  The following code is no longer reported as invalid:

  class classA {
    C = C;
  }
  const C = 0;

• #8178 6ba4157 Thanks @​dyc3! - Fixed #8174, where the HTML parser would parse 2 directives as a single directive because it would not reject whitespace in Vue directives. This would cause the formatter to erroneously merge the 2 directives into one, resulting in broken code.

  - <Component v-else:property="123" />
  + <Component v-else :property="123" />

• #8088 0eb08e8 Thanks @​db295! - Fixed #7876: The noUnusedImports rule now ignores imports that are used by @​linkcode and @​linkplain (previously supported @​link and @​see).

  The following code will no longer be a false positive:

  import type { a } from "a"
  /**
  
  {@​linkcode a}
  */
  function func() {}

#8119 8d64655 Thanks @​ematipico! - Improved the detection of the rule noUnnecessaryConditions. Now the rule isn't triggered for variables that are mutated inside a module.

This logic deviates from the original rule, hence noUnnecessaryConditions is now marked as "inspired".

In the following example, hey starts as false, but then it's assigned to a string. The rule isn't triggered inside the if check.

let hey = false;
function test() {
hey = "string";
}

... (truncated)

Commits

• 8e97b89 ci: release (#8161)
• fb1458b feat(lint/html/vue): add useVueValidVText (#8158)
• 2dd38cf fix(schema): domains and feature kind (#8147)
• 803a44a chore: remove gold sponsor (#8135)
• 166d95b ci: release (#8076)
• 6976d03 chore: schema regression rule domains (#8133)
• 5fc5416 feat(lint/vue): add noVueVIfWithVFor, useVueHyphenatedAttributes (#8097)
• fb8e3e7 fix(noInvalidUseBeforeDeclaration): handle class, enum, import-equals (#8113)
• 0f0a658 feat(analyze): implement noSyncScripts (#8108)
• 82b9a8e feat(js_analyze): implement useFind (#8100)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​biomejs/biome since your current version.

Updates @effect/language-service from 0.55.5 to 0.56.0

Release notes

Sourced from @​effect/language-service's releases.

v0.56.0

Minor Changes

• #494 9b3edf0 Thanks @​mattiamanzati! - Add codegen CLI command to automatically update Effect codegens

  This release introduces a new CLI command effect-language-service codegen that allows you to automatically update Effect codegens in your TypeScript files from the command line. The command scans files containing @effect-codegens directives and applies the necessary code transformations.

  Usage:

  • effect-language-service codegen --file <path> - Update a specific file
  • effect-language-service codegen --project <tsconfig.json> - Update all files in a project
  • effect-language-service codegen --verbose - Show detailed output during processing

  Example:

  # Update a single file
  effect-language-service codegen --file src/MyService.ts
  Update entire project
  effect-language-service codegen --project tsconfig.json --verbose

  This is particularly useful for CI/CD pipelines or batch processing scenarios where you want to ensure all codegens are up-to-date without manual editor intervention.

Changelog

Sourced from @​effect/language-service's changelog.

0.56.0

Minor Changes

• #494 9b3edf0 Thanks @​mattiamanzati! - Add codegen CLI command to automatically update Effect codegens

  This release introduces a new CLI command effect-language-service codegen that allows you to automatically update Effect codegens in your TypeScript files from the command line. The command scans files containing @effect-codegens directives and applies the necessary code transformations.

  Usage:

  • effect-language-service codegen --file <path> - Update a specific file
  • effect-language-service codegen --project <tsconfig.json> - Update all files in a project
  • effect-language-service codegen --verbose - Show detailed output during processing

  Example:

  # Update a single file
  effect-language-service codegen --file src/MyService.ts
  Update entire project
  effect-language-service codegen --project tsconfig.json --verbose

  This is particularly useful for CI/CD pipelines or batch processing scenarios where you want to ensure all codegens are up-to-date without manual editor intervention.

Commits

• d763f15 Version Packages (#495)
• 9b3edf0 Add codegen CLI command (#494)
• See full diff in compare view

Updates drizzle-kit from 0.25.0 to 0.31.7

Release notes

Sourced from drizzle-kit's releases.

drizzle-kit@0.31.6

Bug fixes

• [BUG]: Importing drizzle-kit/api fails in ESM modules

drizzle-kit@0.31.5

• Add casing support to studio configuration and related functions

drizzle-kit@0.31.4

• Fixed halfvec, bit and sparsevec type generation bug in drizzle-kit

drizzle-kit@0.31.3

• Internal changes to Studio context. Added databaseName and packageName properties for Studio

drizzle-kit@0.31.2

Bug fixes

• Fixed relations extraction to not interfere with Drizzle Studio.

drizzle-kit@0.31.1

Fixed drizzle-kit pull bugs when using Gel extensions.

Because Gel extensions create schema names containing :: (for example, ext::auth), Drizzle previously handled these names incorrectly. Starting with this release, you can use Gel extensions without any problems. Here’s what you should do:

1. Enable extensions schemas in drizzle.config.ts

import  { defineConfig } from "drizzle-kit";
export default defineConfig({
dialect: 'gel',
schemaFilter: ['ext::auth', 'public']
});

2. Run drizzle-kit pull

3. Done!

drizzle-kit@0.31.0

Features and improvements

Enum DDL improvements

For situations where you drop an enum value or reorder values in an enum, there is no native way to do this in PostgreSQL. To handle these cases, drizzle-kit used to:

• Change the column data types from the enum to text
• Drop the old enum
• Add the new enum
• Change the column data types back to the new enum

... (truncated)

Commits

• 47ba9c8 Merge remote-tracking branch 'origin/main'
• 4e61887 +
• c66862c Merge pull request #5036 from drizzle-team/kit-checks
• 391d33b Merge branch 'main' into kit-checks
• 97f9a45 fix: Update permissions and streamline npm configuration in release workflows
• 0dfed1b Merge pull request #5035 from drizzle-team/kit-checks
• b6a6aac fix: Add environment variables for npm authentication in release workflow
• b9d7199 fix: Fix release-latest
• c314c8d Merge pull request #5034 from drizzle-team/kit-checks
• 64f4c79 +
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for drizzle-kit since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Labels

The following labels could not be found: automated, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
effect-patterns	Ready	Preview	Comment	Nov 24, 2025 4:12pm
effect-patterns-mcp-server	Error			Nov 24, 2025 4:12pm

[PaulJPhilp]

Closing stale Dependabot PR from November 24. Will allow Dependabot to regenerate fresh PRs against current stable main branch (v0.6.1). This PR had dependency resolution failures that are likely resolved in fresh regeneration.

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml