liuyi
2e1bed061e
feat(server): delay subscription after invitation accepted or approved ( #11992 )
2025-04-30 14:27:47 +08:00
darkskygit
21dc550b9d
feat(server): add doc meta for ignored docs ( #12021 )
...
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- **New Features**
- Ignored documents in workspace embedding now display additional metadata, including document title, creation and update timestamps, and the names and avatars of users who created or updated the document.
- **Enhancements**
- The list of ignored documents provides richer information for easier identification and management within the workspace.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-04-28 11:56:09 +00:00
darkskygit
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
fengmk2
ff133d1267
refactor(server): reduce server logs ( #11931 )
...
close CLOUD-201
2025-04-23 11:41:48 +00:00
darkskygit
ddb739fa13
feat: add pagination support for workspace config ( #11859 )
...
fix AI-78
2025-04-23 11:25:41 +00:00
darkskygit
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
darkskygit
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
darkskygit
38e8806787
feat(server): add doc embedding switch for workspace ( #11760 )
...
fix AI-33
2025-04-17 07:13:22 +00:00
renovate
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
darkskygit
84ff54f9d7
feat(server): make slide audio transcript parallel ( #11692 )
2025-04-15 03:59:23 +00:00
fengmk2
a5eb1b9985
fix(server): correct notification pagination by using 'lt' instead of 'gt' for createdAt ( #11430 )
2025-04-03 01:25:35 +00:00
fengmk2
f3e9b4bbf0
feat(server): search workspace users support case insensitive ( #11422 )
...
close CLOUD-193
2025-04-02 14:33:07 +00:00
forehalo
6276732efc
chore(server): reschedule doc merging jobs ( #11318 )
2025-04-01 10:57:54 +00:00
forehalo
0ea38680fa
refactor(server): config system ( #11081 )
2025-03-27 12:32:28 +00:00
darkskygit
3b9d64d74d
feat(server): update trascript endpoint ( #11196 )
2025-03-27 10:18:49 +00:00
darkskygit
2e5ce44e1b
fix(server): make status optional ( #11176 )
2025-03-27 02:44:29 +00:00
forehalo
ae552c97cf
fix(server): raw user query ( #11151 )
2025-03-26 00:58:38 +00:00
fengmk2
a8c86c5ede
refactor(server): rename settings to user-settings ( #11161 )
2025-03-25 08:47:27 +00:00
forehalo
15173db62c
fix(server): add missing disabled query field ( #11123 )
2025-03-24 08:04:48 +00:00
fengmk2
28f8639aff
feat(server): send invitation review notification ( #10418 )
2025-03-24 03:32:24 +00:00
fengmk2
d7b3dc683b
feat(server): send invitation notification ( #10219 )
...
close PD-2307 CLOUD-150
2025-03-24 02:27:23 +00:00
darkskygit
5acba9d5a0
feat(server): adapt context model ( #11028 )
...
expose more field in listContextObject
2025-03-21 05:36:45 +00:00
darkskygit
b24376a9f7
feat(server): impl context model ( #11027 )
2025-03-20 10:24:28 +00:00
darkskygit
b099546164
feat(server): copilot job models ( #10732 )
2025-03-19 14:34:14 +00:00
fengmk2
5dcbae6f86
feat(server): add settings model ( #10755 )
...
close CLOUD-166
2025-03-18 00:41:21 +00:00
forehalo
8b67496951
refactor(server): saving past_due subscription in db ( #10908 )
...
close CLOUD-122
2025-03-17 10:17:14 +00:00
fengmk2
114e89961f
fix(server): add mode property on mention doc input ( #10853 )
2025-03-14 08:23:28 +00:00
fengmk2
aa3bfb0a05
fix(server): only return workspace user fields ( #10700 )
...
close CLOUD-164
2025-03-12 10:35:00 +00:00
forehalo
1b62b4b625
feat(server): support making doc private in workspace ( #10744 )
2025-03-12 03:18:24 +00:00
forehalo
50da76d4af
feat(server): import users ( #10762 )
...
close CLOUD-167
2025-03-12 02:52:19 +00:00
forehalo
ea72599bde
feat(server): ban account ( #10761 )
...
close CLOUD-158
2025-03-12 02:52:18 +00:00
fengmk2
289d3cd20e
feat(server): get public user by id ( #10434 )
...
close CLOUD-160
2025-03-06 15:25:06 +00:00
fengmk2
7302c4f954
feat(server): notification system ( #10053 )
...
closes CLOUD-52
2025-03-06 15:25:05 +00:00
fengmk2
81694a1144
feat(server): add workspace name and avatarKey to database ( #10513 )
...
close CLOUD-153
2025-03-06 15:25:05 +00:00
fengmk2
c76b2504fe
feat(server): add doc title and summary to database ( #10505 )
...
close CLOUD-152
2025-03-06 14:27:42 +00:00
fengmk2
d2b45783ea
feat(server): use zod parse to impl input validation ( #10566 )
...
close CLOUD-124
2025-03-06 10:40:01 +00:00
fengmk2
70a0337ea3
refactor(server): use DocModel to access doc meta ( #10593 )
2025-03-05 12:10:28 +00:00
fengmk2
687c26304a
refactor(server): split HistoryModel from DocModel ( #10604 )
2025-03-05 12:10:28 +00:00
fengmk2
b247b8e26c
refactor(server): merge PageModel into DocModel ( #10592 )
2025-03-05 19:49:14 +08:00
liuyi
61162c59fc
refactor(server): permission ( #10449 )
2025-03-05 15:57:00 +08:00
fengmk2
3d2c4fe007
feat(server): add user existence check and optimize permission queries ( #10402 )
2025-03-05 01:49:33 +00:00
liuyi
abad289783
fix(server): limit max batch pulled doc updates ( #10578 )
2025-03-03 09:19:17 +00:00
fengmk2
67b6c28d67
refactor(server): use user model on oauth plugin ( #10031 )
...
close CLOUD-117
2025-02-10 20:26:34 +08:00
fengmk2
0757f29f83
refactor(server): use doc model on doc cron job ( #10057 )
2025-02-10 09:52:44 +00:00
fengmk2
09b5eb60eb
refactor(server): handle ConnectedAccount on user model ( #10030 )
2025-02-09 08:31:02 +00:00
fengmk2
36ed81bcc6
refactor(server): use doc model on PgWorkspaceDocStorageAdapter ( #9852 )
...
close CLOUD-104
2025-02-07 12:21:58 +00:00
forehalo
0b9d30b55a
refactor: rename all page query to doc ( #10019 )
2025-02-07 11:40:59 +00:00
liuyi
00b1f01f9b
feat(server): add public user type ( #10006 )
2025-02-07 04:03:59 +00:00
forehalo
7c7febd495
refactor(server): remove never used column in page permission ( #9985 )
2025-02-06 10:52:05 +00:00
forehalo
d873a78534
feat(server): align pro plan for free in selfhost ( #9973 )
...
close AF-2099
2025-02-06 05:25:06 +00:00
