6e034185cf
feat: title of session ( #12971 )
...
fix AI-253
2025-07-01 05:24:42 +00:00
06f27e8d6a
feat(server): allow multiple session attach to doc ( #12933 )
...
fix AI-236
2025-06-26 02:15:31 +00:00
e32c9a814a
feat(server): improve session modify ( #12928 )
...
fix AI-248
2025-06-25 12:02:21 +00:00
13b64c6780
fix(server): session update check ( #12877 )
...
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Bug Fixes**
- Improved validation to prevent updates to sessions with action prompts
and restrict certain updates on forked sessions.
- **Tests**
- Expanded and clarified test coverage for session updates, pinning
behavior, and session type conversions, with more explicit error
handling and validation scenarios.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-06-20 08:53:48 +00:00
c7113b0195
feat(server): add pinned & action filter for session query ( #12876 )
...
fix AI-222
2025-06-20 08:31:04 +00:00
dfaf69475b
fix(server): session unique index conflict ( #12865 )
2025-06-20 08:36:22 +08:00
bd04930560
feat(server): allow chat session dangling & pin session support ( #12849 )
...
fix AI-181
fix AI-179
fix AI-178
fix PD-2682
fix PD-2683
2025-06-19 13:17:01 +08:00
c846c57a12
fix(server): list context status ( #12771 )
...
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- **Bug Fixes**
- Improved handling of document statuses to ensure documents without a finished or existing status are now explicitly marked as "processing" instead of remaining undefined.
- **Tests**
- Added comprehensive new tests and snapshot entries to verify document status merging, including edge cases and concurrent operations, ensuring robust and consistent behavior.
- **Enhancements**
- Updated context document listings to display the processing status for relevant documents.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-06-10 02:35:09 +00:00
9220b973c7
feat(server): increase embedding jobs concurrency & handle empty content after trim ( #12574 )
...
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- **Improvements**
- Increased the default concurrency for background tasks, enhancing processing efficiency.
- Improved handling of empty or unsupported documents to ensure consistent processing.
- Optimized document filtering to exclude certain documents from processing, improving performance.
- **Bug Fixes**
- Enhanced detection of empty document summaries, reducing errors during processing.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-05-27 14:28:34 +00:00
2a80fbb993
feat(server): workspace embedding improve ( #12022 )
...
fix AI-10
fix AI-109
fix PD-2484
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- **New Features**
- Added a method to check if a document requires embedding, improving embedding efficiency.
- Enhanced document embeddings with enriched metadata, including title, summary, creation/update dates, and author information.
- Introduced a new type for document fragments with extended metadata fields.
- **Improvements**
- Embedding logic now conditionally processes only documents needing updates.
- Embedding content now includes document metadata for more informative context.
- Expanded and improved test coverage for embedding scenarios and workspace behaviors.
- Event emission added for workspace embedding updates on client version mismatch.
- Job queueing enhanced with prioritization and explicit job IDs for better management.
- Job queue calls updated to include priority and context identifiers in a structured format.
- **Bug Fixes**
- Improved handling of ignored documents in embedding matches.
- Fixed incorrect document ID assignment in embedding job queueing.
- **Tests**
- Added and updated snapshot and behavioral tests for embedding and workspace document handling.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-05-23 10:16:15 +00:00
6f9361caee
feat(server): trigger workspace embedding ( #12328 )
...
fix AI-127
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- **New Features**
- Added automated event handling for workspace updates and document embedding, streamlining document embedding workflows.
- Introduced detection and queuing of documents needing embedding, excluding ignored documents.
- **Improvements**
- Enhanced performance of embedding-related searches by filtering results at the database level.
- Increased concurrency for embedding job processing to improve throughput.
- **Bug Fixes**
- Improved error handling and fallback for missing document titles during embedding.
- Added safeguards to skip invalid embedding jobs based on document identifiers.
- **Tests**
- Expanded test coverage for document embedding and ignored document filtering.
- Updated end-to-end tests to use dynamic content for improved reliability.
- Added synchronization waits in document creation utilities to improve test stability.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-05-20 05:16:45 +00:00
6224344a4f
chore(server): improve ignored docs list & match ( #12307 )
...
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- **Bug Fixes**
- Improved the accuracy of document matching by excluding ignored documents from search results.
- **Chores**
- Updated internal handling of ignored document lists for better consistency and reliability.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-05-15 09:36:28 +00:00
cecf545590
feat(server): improve context metadata & matching ( #12064 )
...
fix AI-20
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- **New Features**
- Enhanced file metadata with MIME type, blob ID, and file name across context and workspace, now visible in UI and API.
- Added workspace-level matching for files and documents with configurable thresholds and workspace scoping in search queries.
- Introduced a new error type and user-friendly messaging for global workspace context matching failures.
- **Bug Fixes**
- Improved consistent handling of file MIME types and nullable context IDs for accurate metadata.
- **Documentation**
- Updated GraphQL schema, queries, and mutations to include new metadata fields, optional parameters, and error types.
- **Style**
- Added new localization strings for global context matching error messages.
- **Tests**
- Extended test coverage with new and updated snapshot tests for metadata and matching logic.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-05-14 06:32:29 +00:00
5f5de8e89d
feat(server): workspace doc update event from indexer ( #12186 )
...
fix AI-108
fix AI-109
fix AI-13
2025-05-09 07:35:47 +00:00
3feea3dc6c
feat(server): docs pagination ( #12086 )
...
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- **New Features**
- Added paginated document listing for workspaces, allowing users to browse documents with pagination controls.
- Enhanced document details to display creation and update timestamps, as well as information about the creator and last updater.
- **Bug Fixes**
- Updated deprecation notice for workspace document metadata fields to guide users to the latest recommended field.
- **Tests**
- Added new tests to verify document info retrieval and pagination functionality.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-04-30 10:39:00 +00:00
2e1bed061e
feat(server): delay subscription after invitation accepted or approved ( #11992 )
2025-04-30 14:27:47 +08:00
49c57ca649
fix(server): query workspace embed files ( #11982 )
...
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- **New Features**
- Expanded file chunk matching to include both context and workspace file embeddings, providing broader and more relevant search results.
- **Improvements**
- Enhanced result ranking by introducing a re-ranking step for combined embedding matches, improving the relevance of returned file chunks.
- Adjusted file count reporting to reflect the total number of workspace files instead of ignored documents for more accurate workspace file statistics.
- Renamed and streamlined workspace file management methods for clearer and more consistent API usage.
- **Bug Fixes**
- Prevented embedding similarity queries when embedding is disabled for a workspace, improving system behavior consistency.
- **Tests**
- Added comprehensive tests to verify workspace embedding management, including enabling, matching, and disabling embedding functionality.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-04-25 08:32:32 +00:00
ddb739fa13
feat: add pagination support for workspace config ( #11859 )
...
fix AI-78
2025-04-23 11:25:41 +00:00
5397fba897
feat(server): global embedding gql endpoint ( #11809 )
...
fix AI-30
fix AI-31
fix PD-2487
2025-04-23 11:25:41 +00:00
f2adb9f72c
feat(server): workspace file embedding & ignored docs model impl ( #11804 )
...
fix AI-30
fix AI-31
2025-04-21 05:34:10 +00:00
38e8806787
feat(server): add doc embedding switch for workspace ( #11760 )
...
fix AI-33
2025-04-17 07:13:22 +00:00
b249939093
chore: bump up prisma monorepo to v6 (major) ( #8964 )
...
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [@prisma/client](https://www.prisma.io ) ([source](https://redirect.github.com/prisma/prisma/tree/HEAD/packages/client )) | [`^5.22.0` -> `^6.0.0`](https://renovatebot.com/diffs/npm/@prisma%2fclient/5.22.0/6.0.1 ) | [](https://docs.renovatebot.com/merge-confidence/ ) | [](https://docs.renovatebot.com/merge-confidence/ ) | [](https://docs.renovatebot.com/merge-confidence/ ) | [](https://docs.renovatebot.com/merge-confidence/ ) |
| [@prisma/instrumentation](https://www.prisma.io ) ([source](https://redirect.github.com/prisma/prisma/tree/HEAD/packages/instrumentation )) | [`^5.22.0` -> `^6.0.0`](https://renovatebot.com/diffs/npm/@prisma%2finstrumentation/5.22.0/6.0.1 ) | [](https://docs.renovatebot.com/merge-confidence/ ) | [](https://docs.renovatebot.com/merge-confidence/ ) | [](https://docs.renovatebot.com/merge-confidence/ ) | [](https://docs.renovatebot.com/merge-confidence/ ) |
| [prisma](https://www.prisma.io ) ([source](https://redirect.github.com/prisma/prisma/tree/HEAD/packages/cli )) | [`^5.22.0` -> `^6.0.0`](https://renovatebot.com/diffs/npm/prisma/5.22.0/6.0.1 ) | [](https://docs.renovatebot.com/merge-confidence/ ) | [](https://docs.renovatebot.com/merge-confidence/ ) | [](https://docs.renovatebot.com/merge-confidence/ ) | [](https://docs.renovatebot.com/merge-confidence/ ) |
---
### Release Notes
<details>
<summary>prisma/prisma (@​prisma/client)</summary>
### [`v6.0.1`](https://redirect.github.com/prisma/prisma/compare/6.0.0...6.0.1 )
[Compare Source](https://redirect.github.com/prisma/prisma/compare/6.0.0...6.0.1 )
### [`v6.0.0`](https://redirect.github.com/prisma/prisma/releases/tag/6.0.0 )
[Compare Source](https://redirect.github.com/prisma/prisma/compare/5.22.0...6.0.0 )
We’re excited to share the Prisma ORM v6 release today 🎉
As this is a major release, it includes a few breaking changes that may affect your application. Before upgrading, we recommend that you check out our [upgrade guide](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6 ) to understand the impact on your application.
If you want to have an overview of what we accomplished since v5, check out our announcement blog post: [Prisma 6: Better Performance, More Flexibility & Type-Safe SQL](https://www.prisma.io/blog/prisma-6-better-performance-more-flexibility-and-type-safe-sql ).
🌟 **Help us spread the word about Prisma by starring the repo ☝️ or [posting on X](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@​prisma%20release%20v6.0.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/6.0.0 ) about the release.**
##### Breaking changes
⚠️ This section contains a list of breaking changes. If you upgrade your application to Prisma ORM v6 without addressing these, your application is going to break! **For detailed upgrade instructions, check out the [upgrade guide](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6 ).** ⚠️
##### Minimum supported Node.js versions
The new minimum supported Node.js versions for Prisma ORM v6 are:
- for Node.js 18 the minimum supported version is **18.18.0**
- for Node.js 20 the minimum supported version is **20.9.0**
- for Node.js 22 the minimum supported version is **22.11.0**
There is no official support for Node.js <18.18.0, 19, 21, 23.
##### Minimum supported TypeScript version
The new minimum supported TypeScript version for Prisma ORM v6 is: **5.1.0**.
##### Schema change for implicit m-n relations on PostgreSQL
If you're using PostgreSQL and are defining [implicit many-to-many relations](https://www.prisma.io/docs/orm/prisma-schema/data-model/relations/many-to-many-relations#implicit-many-to-many-relations ) in your Prisma schema, Prisma ORM maintains the [relation table](https://www.prisma.io/docs/orm/prisma-schema/data-model/relations/many-to-many-relations#relation-tables ) for you under the hood. This relation table has `A` and `B` columns to represent the tables of the models that are part of this relation.
Previous versions of Prisma ORM used to create a *unique index* on these two columns. In Prisma v6, this unique index is changing to a *primary key* in order to [simplify for the default replica identity behaviour](https://redirect.github.com/prisma/prisma/issues/25196 ).
If you're defining implicit m-n relations in your Prisma schema, the next migration you'll create will contain `ALTER TABLE` statements for *all* the relation tables that belong to these relations.
##### Full-text search on PostgreSQL
The `fullTextSearch` Preview feature is promoted to General Availability only for MySQL. This means that if you're using PostgreSQL and currently make use of this Preview feature, you now need to use the new `fullTextSearchPostgres` Preview feature.
##### Usage of `Buffer`
Prisma v6 replaces the usage of [`Buffer`](https://nodejs.org/api/buffer.html ) with [`Uint8Array`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Uint8Array ) to represent fields of type `Bytes`. Make sure to replace all your occurrences of the `Buffer` type with the new `Uint8Array`.
##### Removed `NotFoundError`
In Prisma v6, we removed the `NotFoundError` in favor of `PrismaClientKnownRequestError` with error code [`P2025`](https://www.prisma.io/docs/orm/reference/error-reference#p2025 ) in [`findUniqueOrThrow()`](https://www.prisma.io/docs/orm/reference/prisma-client-reference#finduniqueorthrow ) and [`findFirstOrThrow()`](https://www.prisma.io/docs/orm/reference/prisma-client-reference#findfirstorthrow ). If you've relied on catching `NotFoundError` instances in your code, you need to adjust the code accordingly.
##### New keywords that can't be used as model names: `async`, `await`, `using`
With this release, you can't use `async`, `await` and `using` as model names any more.
***
⚠️ **For detailed upgrade instructions, check out the [upgrade guide](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6 ).** ⚠️
##### Preview features promoted to General Availability
In this release, we are promoting a number of [Preview](https://www.prisma.io/docs/orm/more/releases#preview ) features to [General Availability](https://www.prisma.io/docs/orm/more/releases#generally-available-ga ).
##### `fullTextIndex`
If you use the [full-text index](https://www.prisma.io/docs/orm/prisma-schema/data-model/indexes#full-text-indexes-mysql-and-mongodb ) feature in your app, you can now remove `fullTextIndex` from the `previewFeatures` in your Prisma schema:
```diff
generator client {
provider = "prisma-client-js"
- previewFeatures = ["fullTextIndex"]
}
```
##### `fullTextSearch`
If you use the [full-text search](https://www.prisma.io/docs/orm/prisma-client/queries/full-text-search ) feature with **MySQL** in your app, you can now remove `fullTextSearch` from the `previewFeatures` in your Prisma schema:
```diff
generator client {
provider = "prisma-client-js"
- previewFeatures = ["fullTextSearch"]
}
```
If you are using it with **PostgreSQL**, you need to update the name of the feature flag to `fullTextSearchPostgres`:
```diff
generator client {
provider = "prisma-client-js"
- previewFeatures = ["fullTextSearch"]
+ previewFeatures = ["fullTextSearchPostgres"]
}
```
##### New features
We are also releasing new features with this release:
- [cuid2() support](https://redirect.github.com/prisma/prisma-engines/pull/5047 )
- [Include unused enum definitions in `prisma generate`'s output](https://redirect.github.com/prisma/prisma/pull/25740 )
- [Improved compatibility with Deno 2](https://redirect.github.com/prisma/prisma/pull/25734 )
##### Company news
##### 🚀 Prisma Postgres is free during Early Access
In case you missed it: We recently launched [Prisma Postgres](https://www.prisma.io/blog/announcing-prisma-postgres-early-access ), a serverless database with zero cold starts, a generous free tier, connection pooling, real-time events, and a lot more! It’s entirely free during the Early Access phase, try it now!
##### ✨ Let us know what you think of Prisma ORM
We're always trying to improve! If you've recently used Prisma ORM, we'd appreciate hearing your thoughts about your experience via this [2min survey](https://pris.ly/orm/survey/release-5-22 ).
</details>
<details>
<summary>prisma/prisma (@​prisma/instrumentation)</summary>
### [`v6.0.1`](https://redirect.github.com/prisma/prisma/releases/tag/6.0.1 )
[Compare Source](https://redirect.github.com/prisma/prisma/compare/6.0.0...6.0.1 )
Today we are releasing the `6.0.1` patch release to address an issue with using Prisma Client generated in a custom output path with Next.js.
##### Changes
- [Revert `"type": "commonjs"` addition in generated `package.json`](https://redirect.github.com/prisma/prisma/pull/25767 )
### [`v6.0.0`](https://redirect.github.com/prisma/prisma/releases/tag/6.0.0 )
[Compare Source](https://redirect.github.com/prisma/prisma/compare/5.22.0...6.0.0 )
We’re excited to share the Prisma ORM v6 release today 🎉
As this is a major release, it includes a few breaking changes that may affect your application. Before upgrading, we recommend that you check out our [upgrade guide](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6 ) to understand the impact on your application.
If you want to have an overview of what we accomplished since v5, check out our announcement blog post: [Prisma 6: Better Performance, More Flexibility & Type-Safe SQL](https://www.prisma.io/blog/prisma-6-better-performance-more-flexibility-and-type-safe-sql ).
🌟 **Help us spread the word about Prisma by starring the repo ☝️ or [posting on X](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@​prisma%20release%20v6.0.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/6.0.0 ) about the release.**
#### Breaking changes
⚠️ This section contains a list of breaking changes. If you upgrade your application to Prisma ORM v6 without addressing these, your application is going to break! **For detailed upgrade instructions, check out the [upgrade guide](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6 ).** ⚠️
##### Minimum supported Node.js versions
The new minimum supported Node.js versions for Prisma ORM v6 are:
- for Node.js 18 the minimum supported version is **18.18.0**
- for Node.js 20 the minimum supported version is **20.9.0**
- for Node.js 22 the minimum supported version is **22.11.0**
There is no official support for Node.js <18.18.0, 19, 21, 23.
##### Minimum supported TypeScript version
The new minimum supported TypeScript version for Prisma ORM v6 is: **5.1.0**.
##### Schema change for implicit m-n relations on PostgreSQL
If you're using PostgreSQL and are defining [implicit many-to-many relations](https://www.prisma.io/docs/orm/prisma-schema/data-model/relations/many-to-many-relations#implicit-many-to-many-relations ) in your Prisma schema, Prisma ORM maintains the [relation table](https://www.prisma.io/docs/orm/prisma-schema/data-model/relations/many-to-many-relations#relation-tables ) for you under the hood. This relation table has `A` and `B` columns to represent the tables of the models that are part of this relation.
Previous versions of Prisma ORM used to create a *unique index* on these two columns. In Prisma v6, this unique index is changing to a *primary key* in order to [simplify for the default replica identity behaviour](https://redirect.github.com/prisma/prisma/issues/25196 ).
If you're defining implicit m-n relations in your Prisma schema, the next migration you'll create will contain `ALTER TABLE` statements for *all* the relation tables that belong to these relations.
##### Full-text search on PostgreSQL
The `fullTextSearch` Preview feature is promoted to General Availability only for MySQL. This means that if you're using PostgreSQL and currently make use of this Preview feature, you now need to use the new `fullTextSearchPostgres` Preview feature.
##### Usage of `Buffer`
Prisma v6 replaces the usage of [`Buffer`](https://nodejs.org/api/buffer.html ) with [`Uint8Array`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Uint8Array ) to represent fields of type `Bytes`. Make sure to replace all your occurrences of the `Buffer` type with the new `Uint8Array`.
##### Removed `NotFoundError`
In Prisma v6, we removed the `NotFoundError` in favor of `PrismaClientKnownRequestError` with error code [`P2025`](https://www.prisma.io/docs/orm/reference/error-reference#p2025 ) in [`findUniqueOrThrow()`](https://www.prisma.io/docs/orm/reference/prisma-client-reference#finduniqueorthrow ) and [`findFirstOrThrow()`](https://www.prisma.io/docs/orm/reference/prisma-client-reference#findfirstorthrow ). If you've relied on catching `NotFoundError` instances in your code, you need to adjust the code accordingly.
##### New keywords that can't be used as model names: `async`, `await`, `using`
With this release, you can't use `async`, `await` and `using` as model names any more.
***
⚠️ **For detailed upgrade instructions, check out the [upgrade guide](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6 ).** ⚠️
#### Preview features promoted to General Availability
In this release, we are promoting a number of [Preview](https://www.prisma.io/docs/orm/more/releases#preview ) features to [General Availability](https://www.prisma.io/docs/orm/more/releases#generally-available-ga ).
##### `fullTextIndex`
If you use the [full-text index](https://www.prisma.io/docs/orm/prisma-schema/data-model/indexes#full-text-indexes-mysql-and-mongodb ) feature in your app, you can now remove `fullTextIndex` from the `previewFeatures` in your Prisma schema:
```diff
generator client {
provider = "prisma-client-js"
- previewFeatures = ["fullTextIndex"]
}
```
##### `fullTextSearch`
If you use the [full-text search](https://www.prisma.io/docs/orm/prisma-client/queries/full-text-search ) feature with **MySQL** in your app, you can now remove `fullTextSearch` from the `previewFeatures` in your Prisma schema:
```diff
generator client {
provider = "prisma-client-js"
- previewFeatures = ["fullTextSearch"]
}
```
If you are using it with **PostgreSQL**, you need to update the name of the feature flag to `fullTextSearchPostgres`:
```diff
generator client {
provider = "prisma-client-js"
- previewFeatures = ["fullTextSearch"]
+ previewFeatures = ["fullTextSearchPostgres"]
}
```
#### New features
We are also releasing new features with this release:
- [cuid2() support](https://redirect.github.com/prisma/prisma-engines/pull/5047 )
- [Include unused enum definitions in `prisma generate`'s output](https://redirect.github.com/prisma/prisma/pull/25740 )
- [Improved compatibility with Deno 2](https://redirect.github.com/prisma/prisma/pull/25734 )
#### Company news
##### 🚀 Prisma Postgres is free during Early Access
In case you missed it: We recently launched [Prisma Postgres](https://www.prisma.io/blog/announcing-prisma-postgres-early-access ), a serverless database with zero cold starts, a generous free tier, connection pooling, real-time events, and a lot more! It’s entirely free during the Early Access phase, try it now!
##### ✨ Let us know what you think of Prisma ORM
We're always trying to improve! If you've recently used Prisma ORM, we'd appreciate hearing your thoughts about your experience via this [2min survey](https://pris.ly/orm/survey/release-5-22 ).
</details>
<details>
<summary>prisma/prisma (prisma)</summary>
### [`v6.0.1`](https://redirect.github.com/prisma/prisma/compare/6.0.0...6.0.1 )
[Compare Source](https://redirect.github.com/prisma/prisma/compare/6.0.0...6.0.1 )
### [`v6.0.0`](https://redirect.github.com/prisma/prisma/releases/tag/6.0.0 )
[Compare Source](https://redirect.github.com/prisma/prisma/compare/5.22.0...6.0.0 )
We’re excited to share the Prisma ORM v6 release today 🎉
As this is a major release, it includes a few breaking changes that may affect your application. Before upgrading, we recommend that you check out our [upgrade guide](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6 ) to understand the impact on your application.
If you want to have an overview of what we accomplished since v5, check out our announcement blog post: [Prisma 6: Better Performance, More Flexibility & Type-Safe SQL](https://www.prisma.io/blog/prisma-6-better-performance-more-flexibility-and-type-safe-sql ).
🌟 **Help us spread the word about Prisma by starring the repo ☝️ or [posting on X](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@​prisma%20release%20v6.0.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/6.0.0 ) about the release.**
##### Breaking changes
⚠️ This section contains a list of breaking changes. If you upgrade your application to Prisma ORM v6 without addressing these, your application is going to break! **For detailed upgrade instructions, check out the [upgrade guide](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6 ).** ⚠️
##### Minimum supported Node.js versions
The new minimum supported Node.js versions for Prisma ORM v6 are:
- for Node.js 18 the minimum supported version is **18.18.0**
- for Node.js 20 the minimum supported version is **20.9.0**
- for Node.js 22 the minimum supported version is **22.11.0**
There is no official support for Node.js <18.18.0, 19, 21, 23.
##### Minimum supported TypeScript version
The new minimum supported TypeScript version for Prisma ORM v6 is: **5.1.0**.
##### Schema change for implicit m-n relations on PostgreSQL
If you're using PostgreSQL and are defining [implicit many-to-many relations](https://www.prisma.io/docs/orm/prisma-schema/data-model/relations/many-to-many-relations#implicit-many-to-many-relations ) in your Prisma schema, Prisma ORM maintains the [relation table](https://www.prisma.io/docs/orm/prisma-schema/data-model/relations/many-to-many-relations#relation-tables ) for you under the hood. This relation table has `A` and `B` columns to represent the tables of the models that are part of this relation.
Previous versions of Prisma ORM used to create a *unique index* on these two columns. In Prisma v6, this unique index is changing to a *primary key* in order to [simplify for the default replica identity behaviour](https://redirect.github.com/prisma/prisma/issues/25196 ).
If you're defining implicit m-n relations in your Prisma schema, the next migration you'll create will contain `ALTER TABLE` statements for *all* the relation tables that belong to these relations.
##### Full-text search on PostgreSQL
The `fullTextSearch` Preview feature is promoted to General Availability only for MySQL. This means that if you're using PostgreSQL and currently make use of this Preview feature, you now need to use the new `fullTextSearchPostgres` Preview feature.
##### Usage of `Buffer`
Prisma v6 replaces the usage of [`Buffer`](https://nodejs.org/api/buffer.html ) with [`Uint8Array`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Uint8Array ) to represent fields of type `Bytes`. Make sure to replace all your occurrences of the `Buffer` type with the new `Uint8Array`.
##### Removed `NotFoundError`
In Prisma v6, we removed the `NotFoundError` in favor of `PrismaClientKnownRequestError` with error code [`P2025`](https://www.prisma.io/docs/orm/reference/error-reference#p2025 ) in [`findUniqueOrThrow()`](https://www.prisma.io/docs/orm/reference/prisma-client-reference#finduniqueorthrow ) and [`findFirstOrThrow()`](https://www.prisma.io/docs/orm/reference/prisma-client-reference#findfirstorthrow ). If you've relied on catching `NotFoundError` instances in your code, you need to adjust the code accordingly.
##### New keywords that can't be used as model names: `async`, `await`, `using`
With this release, you can't use `async`, `await` and `using` as model names any more.
***
⚠️ **For detailed upgrade instructions, check out the [upgrade guide](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6 ).** ⚠️
##### Preview features promoted to General Availability
In this release, we are promoting a number of [Preview](https://www.prisma.io/docs/orm/more/releases#preview ) features to [General Availability](https://www.prisma.io/docs/orm/more/releases#generally-available-ga ).
##### `fullTextIndex`
If you use the [full-text index](https://www.prisma.io/docs/orm/prisma-schema/data-model/indexes#full-text-indexes-mysql-and-mongodb ) feature in your app, you can now remove `fullTextIndex` from the `previewFeatures` in your Prisma schema:
```diff
generator client {
provider = "prisma-client-js"
- previewFeatures = ["fullTextIndex"]
}
```
##### `fullTextSearch`
If you use the [full-text search](https://www.prisma.io/docs/orm/prisma-client/queries/full-text-search ) feature with **MySQL** in your app, you can now remove `fullTextSearch` from the `previewFeatures` in your Prisma schema:
```diff
generator client {
provider = "prisma-client-js"
- previewFeatures = ["fullTextSearch"]
}
```
If you are using it with **PostgreSQL**, you need to update the name of the feature flag to `fullTextSearchPostgres`:
```diff
generator client {
provider = "prisma-client-js"
- previewFeatures = ["fullTextSearch"]
+ previewFeatures = ["fullTextSearchPostgres"]
}
```
##### New features
We are also releasing new features with this release:
- [cuid2() support](https://redirect.github.com/prisma/prisma-engines/pull/5047 )
- [Include unused enum definitions in `prisma generate`'s output](https://redirect.github.com/prisma/prisma/pull/25740 )
- [Improved compatibility with Deno 2](https://redirect.github.com/prisma/prisma/pull/25734 )
##### Company news
##### 🚀 Prisma Postgres is free during Early Access
In case you missed it: We recently launched [Prisma Postgres](https://www.prisma.io/blog/announcing-prisma-postgres-early-access ), a serverless database with zero cold starts, a generous free tier, connection pooling, real-time events, and a lot more! It’s entirely free during the Early Access phase, try it now!
##### ✨ Let us know what you think of Prisma ORM
We're always trying to improve! If you've recently used Prisma ORM, we'd appreciate hearing your thoughts about your experience via this [2min survey](https://pris.ly/orm/survey/release-5-22 ).
</details>
---
### 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.
🔕 **Ignore**: Close this PR and you won't be reminded about these updates again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/ ). View the [repository job log](https://developer.mend.io/github/toeverything/AFFiNE ).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xOS4wIiwidXBkYXRlZEluVmVyIjoiMzkuNTguMSIsInRhcmdldEJyYW5jaCI6ImNhbmFyeSIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
2025-04-15 09:05:00 +00:00
0ea38680fa
refactor(server): config system ( #11081 )
2025-03-27 12:32:28 +00:00
3b9d64d74d
feat(server): update trascript endpoint ( #11196 )
2025-03-27 10:18:49 +00:00
2e5ce44e1b
fix(server): make status optional ( #11176 )
2025-03-27 02:44:29 +00:00
1bb324eeed
feat(server): update gql endpoint & workspace doc match test ( #11104 )
2025-03-25 10:09:22 +00:00
5acba9d5a0
feat(server): adapt context model ( #11028 )
...
expose more field in listContextObject
2025-03-21 05:36:45 +00:00
b24376a9f7
feat(server): impl context model ( #11027 )
2025-03-20 10:24:28 +00:00
c16ae2d5b4
feat(server): audio transcription ( #10733 )
2025-03-20 07:12:27 +00:00
b099546164
feat(server): copilot job models ( #10732 )
2025-03-19 14:34:14 +00:00
ea72599bde
feat(server): ban account ( #10761 )
...
close CLOUD-158
2025-03-12 02:52:18 +00:00
289d3cd20e
feat(server): get public user by id ( #10434 )
...
close CLOUD-160
2025-03-06 15:25:06 +00:00
c76b2504fe
feat(server): add doc title and summary to database ( #10505 )
...
close CLOUD-152
2025-03-06 14:27:42 +00:00
687c26304a
refactor(server): split HistoryModel from DocModel ( #10604 )
2025-03-05 12:10:28 +00:00
b247b8e26c
refactor(server): merge PageModel into DocModel ( #10592 )
2025-03-05 19:49:14 +08:00
61162c59fc
refactor(server): permission ( #10449 )
2025-03-05 15:57:00 +08:00
3d2c4fe007
feat(server): add user existence check and optimize permission queries ( #10402 )
2025-03-05 01:49:33 +00:00
d970bd041c
test(server): avoid db deadlock on unittest ( #10104 )
...
https://github.com/toeverything/AFFiNE/runs/37010719190
2025-02-12 03:48:21 +00:00
67b6c28d67
refactor(server): use user model on oauth plugin ( #10031 )
...
close CLOUD-117
2025-02-10 20:26:34 +08:00
09b5eb60eb
refactor(server): handle ConnectedAccount on user model ( #10030 )
2025-02-09 08:31:02 +00:00
36ed81bcc6
refactor(server): use doc model on PgWorkspaceDocStorageAdapter ( #9852 )
...
close CLOUD-104
2025-02-07 12:21:58 +00:00
0b9d30b55a
refactor: rename all page query to doc ( #10019 )
2025-02-07 11:40:59 +00:00
d873a78534
feat(server): align pro plan for free in selfhost ( #9973 )
...
close AF-2099
2025-02-06 05:25:06 +00:00
8e7cfb6115
feat(server): userDoc model ( #9835 )
...
close CLOUD-104
2025-02-06 11:08:06 +08:00
b40f007ccf
feat(server): doc model ( #9834 )
...
close CLOUD-104
2025-02-06 02:50:27 +00:00
7826e2b7c8
refactor(server): use feature model ( #9932 )
2025-02-05 10:27:26 +00:00
abeff8bb1a
feat(server): doc level permission ( #9760 )
...
close CLOUD-89 CLOUD-90 CLOUD-91 CLOUD-92
2025-02-05 07:06:57 +00:00
6370f45928
feat(server): cluster level event system ( #9884 )
2025-01-25 14:51:03 +00:00
2088b760bf
refactor(server): rename tx to db ( #9867 )
2025-01-23 07:52:45 +00:00
f8a515e89a
feat(server): user feature model ( #9843 )
...
close CLOUD-108
2025-01-22 10:38:04 +00:00
DarkSky
