Bump the non-breaking-changes group across 1 directory with 4 updates

[dependabot]

Bumps the non-breaking-changes group with 4 updates in the / directory: @prisma/client, @typescript-eslint/eslint-plugin, @typescript-eslint/parser and prisma.

Updates @prisma/client from 6.1.0 to 6.2.1

Release notes

Sourced from @​prisma/client's releases.

6.2.1

Today we are releasing the 6.2.1 patch release to address an issue with some of the omitApi preview feature checks having been accidentally omitted when making the feature GA. Now it is fully functional without the preview feature flag.

Changes

• prisma/prisma#25997

6.2.0

Today we're releasing Prisma ORM version 6.2.0 🎉

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

We have a number of new features in this version, including support for json and enum fields in SQLite, a new updateManyAndReturn function, support for ULID values, as well as the promotion of the omit feature from Preview to Generally Availability.

Highlights

Excluding fields via omit is now production-ready

Our number one requested feature is out of Preview and Generally Available. In 6.2.0, you no longer need to add omitApi to your list of Preview features:

generator client {
  provider        = "prisma-client-js"
- previewFeatures = ["omitApi"]
}

As a refresher: omit allows you to exclude certain fields from being returned in the results of your Prisma Client queries.

You can either do this locally, on a per-query level:

const result = await prisma.user.findMany({
  omit: {
    password: true,
  },
});

Or globally, to ensure a field is excluded from all queries of a certain model:

const prisma = new PrismaClient({
  omit: {
    user: {
      password: true
    }
  }
})
</tr></table>

... (truncated)

Commits

• 60a8268 fix(client): remove omitApi preview feature checks (#25997)
• 3b23a20 chore(deps): update engines to 6.2.0-14.4123509d24aa4dede1e864b46351bf2790323...
• 6ea6991 chore(deps): update engines to 6.2.0-12.51db5cf11ad393407e86084764bced274b48b...
• 425502f fix: node 23 support (#25971)
• 477375c chore(deps): update engines to 6.2.0-11.c49e56c20818c325095752dd0ae895b0dc7ba...
• c43e181 fix(client): allow "passing" across rpc boundary in cloudflare workers (#25914)
• 0a4ef08 chore(deps): update engines to 6.2.0-6.cc0167b764494213f0e42d0867d48643c39c83...
• ebda0b9 fix(client): make nested omit types work (#25900)
• 509b064 chore(deps): update engines to 6.2.0-4.3aa926082bfc4f57e60f2210df297fdfbc889a...
• e3e5568 feat: sqlite JSON support (#25871)
• Additional commits viewable in compare view

Updates @typescript-eslint/eslint-plugin from 8.19.0 to 8.19.1

Release notes

Sourced from @​typescript-eslint/eslint-plugin's releases.

v8.19.1

8.19.1 (2025-01-06)

🩹 Fixes

• eslint-plugin: [no-base-to-string] check array generic type (#10437)
• eslint-plugin: [no-shadow] report correctly on parameters of functions declared with the declare keyword (#10543)
• eslint-plugin: [strict-boolean-expressions] remove remaining (unsafe) autofixes (#10548)
• eslint-plugin: [no-deprecated] doesn't report on shorthand property in an object expression (#10550)

❤️ Thank You

• Kirk Waiblinger
• mdm317
• Ronen Amiel
• Yukihiro Hasegawa @​y-hsgw

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

Changelog

Sourced from @​typescript-eslint/eslint-plugin's changelog.

8.19.1 (2025-01-06)

🩹 Fixes

• eslint-plugin: [no-unnecessary-type-assertion] handle literal types (#10523)
• eslint-plugin: [no-deprecated] doesn't report on shorthand property in an object expression (#10550)
• eslint-plugin: [strict-boolean-expressions] remove remaining (unsafe) autofixes (#10548)
• eslint-plugin: [no-shadow] report correctly on parameters of functions declared with the declare keyword (#10543)
• eslint-plugin: [no-base-to-string] check array generic type (#10437)

❤️ Thank You

• Kirk Waiblinger
• mdm317
• Ronen Amiel
• Yukihiro Hasegawa @​y-hsgw

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

Commits

• 328b7df chore(release): publish 8.19.1
• 5dedb1c docs: fix incorrect variable name in a comment in code example (#10613)
• 6e05e56 fix: revert "fix(eslint-plugin): [no-unnecessary-type-assertion] handle liter...
• 82716b8 fix(eslint-plugin): [no-unnecessary-type-assertion] handle literal types (#10...
• c7154bf chore(eslint-plugin): use getConstraintInfo in no-unnecessary-template-expr...
• 63b2d3e fix(eslint-plugin): [no-deprecated] doesn't report on shorthand property in a...
• 4dbf48b fix(eslint-plugin): [strict-boolean-expressions] remove remaining (unsafe) au...
• 3bacfa7 chore: upgrade to ts-api-utils 2.0 (#10567)
• 4f50f64 docs: [return-await] make the rule no longer an extension of ESLint no-return...
• 4e7f5f8 docs: [prefer-nullish-coalescing] fix admonition (#10574)
• Additional commits viewable in compare view

Updates @typescript-eslint/parser from 8.19.0 to 8.19.1

Release notes

Sourced from @​typescript-eslint/parser's releases.

v8.19.1

8.19.1 (2025-01-06)

🩹 Fixes

• eslint-plugin: [no-base-to-string] check array generic type (#10437)
• eslint-plugin: [no-shadow] report correctly on parameters of functions declared with the declare keyword (#10543)
• eslint-plugin: [strict-boolean-expressions] remove remaining (unsafe) autofixes (#10548)
• eslint-plugin: [no-deprecated] doesn't report on shorthand property in an object expression (#10550)

❤️ Thank You

• Kirk Waiblinger
• mdm317
• Ronen Amiel
• Yukihiro Hasegawa @​y-hsgw

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

Changelog

Sourced from @​typescript-eslint/parser's changelog.

8.19.1 (2025-01-06)

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.

Commits

• 328b7df chore(release): publish 8.19.1
• See full diff in compare view

Updates prisma from 6.1.0 to 6.2.1

Release notes

Sourced from prisma's releases.

6.2.1

Today we are releasing the 6.2.1 patch release to address an issue with some of the omitApi preview feature checks having been accidentally omitted when making the feature GA. Now it is fully functional without the preview feature flag.

Changes

• prisma/prisma#25997

6.2.0

Today we're releasing Prisma ORM version 6.2.0 🎉

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

We have a number of new features in this version, including support for json and enum fields in SQLite, a new updateManyAndReturn function, support for ULID values, as well as the promotion of the omit feature from Preview to Generally Availability.

Highlights

Excluding fields via omit is now production-ready

Our number one requested feature is out of Preview and Generally Available. In 6.2.0, you no longer need to add omitApi to your list of Preview features:

generator client {
  provider        = "prisma-client-js"
- previewFeatures = ["omitApi"]
}

As a refresher: omit allows you to exclude certain fields from being returned in the results of your Prisma Client queries.

You can either do this locally, on a per-query level:

const result = await prisma.user.findMany({
  omit: {
    password: true,
  },
});

Or globally, to ensure a field is excluded from all queries of a certain model:

const prisma = new PrismaClient({
  omit: {
    user: {
      password: true
    }
  }
})
</tr></table>

... (truncated)

Commits

• d6c1639 feat(cli): report typescript version via prisma --version (#25968)
• 425502f fix: node 23 support (#25971)
• See full diff in compare view

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

[coderabbitai]

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.