Conversation
**What changed** `@types/pg` was moved from a `devDependency` to a regular `dependency` in `adapter-pg`'s `package.json`, and the pnpm lockfile entries were updated accordingly. **Why** When using `adapter-pg`, the TypeScript types for `pg` are not automatically available — they live in `@types/pg`, which is a separate package that the adapter consumed only as a dev dependency. Because of this, consumers who install `adapter-pg` end up with a poor developer experience: the adapter's types fail to load correctly at the consumer's side, since TypeScript can't resolve the underlying `pg` types without `@types/pg` being present. The problem is subtle and frustrating: the user has no reason to know that `adapter-pg` internally depends on `@types/pg`, and nothing tells them they need to install it manually. The fix is to make `@types/pg` a direct, non-dev dependency so it is automatically installed whenever `adapter-pg` is installed — both for the end user's type resolution and for the build itself. **Impact** No runtime behavior changes. This is a types-only fix that improves the out-of-the-box TypeScript experience for anyone using `adapter-pg`. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated PostgreSQL adapter dependencies: moved type definitions from development-only to runtime dependencies so they're available when the adapter is installed. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Fixes #5509 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Enhanced JSDoc documentation to include the `distinct` option for findMany operations in the JavaScript client generator * Added support for documenting the `distinct` option across findMany, findFirst, and findFirstOrThrow operations in the TypeScript client generator <!-- end of auto-generated comment: release notes by coderabbit.ai -->
…ap (#29052) Use a private property instead of the `WeakMap` workaround and resolve the TODO comment. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Refactor** * Improved internal storage mechanism for better performance and maintainability. --- **Note:** This release contains internal optimizations with no changes to user-facing functionality or behavior. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )