f1605e246b
feat(server): support query overcapacity member count of workspace ( #12050 )
...
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- **New Features**
- Workspace quota information now includes a new metric: the count of members exceeding seat capacity ("overcapacityMemberCount"), available in both numeric and human-readable formats.
- The workspace quota display and related queries have been updated to show this new overcapacity member count alongside existing quota metrics.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-04-30 09:47:50 +00:00
2e1bed061e
feat(server): delay subscription after invitation accepted or approved ( #11992 )
2025-04-30 14:27:47 +08:00
a75ae38308
fix(nbstore): fix cloud blob in ios and android ( #11938 )
2025-04-30 10:25:15 +08:00
4662ee8da7
chore: add crossorigin to resource tags ( #12031 )
...
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- **New Features**
- Added the crossorigin attribute to all CSS and JavaScript tags in generated HTML, improving compatibility for cross-origin resource loading.
- **Tests**
- Updated tests to verify the presence of the crossorigin attribute in script tags.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-04-28 12:25:13 +00:00
f0e2361e81
feat(server): support importing users with password ( #11978 )
...
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- **New Features**
- Added support for an optional password field when creating a new user via the user creation form or API.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-04-25 03:38:34 +00:00
ff133d1267
refactor(server): reduce server logs ( #11931 )
...
close CLOUD-201
2025-04-23 11:41:48 +00:00
f918573ba8
fix(server): config defaults ( #11879 )
2025-04-22 04:26:28 +00:00
5e0d1fae98
chore(server): allow preflight workspace blob url ( #11783 )
2025-04-18 01:23:14 +00:00
38e8806787
feat(server): add doc embedding switch for workspace ( #11760 )
...
fix AI-33
2025-04-17 07:13:22 +00:00
18fae0f1aa
fix: host app with subpath ( #11739 )
...
closes #11719
2025-04-17 01:29:48 +00:00
681c61a300
chore(admin): allow config avatar public path ( #11689 )
...
close #11677
2025-04-15 12:54:55 +00:00
7257f1b55b
chore(server): remove enable flag in mail config ( #11680 )
...
close #11625
2025-04-15 09:18:10 +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
f2f1a10715
fix(server): initial user plan ( #11687 )
2025-04-15 03:59:22 +00:00
a166760041
fix(server): adjust expire time of invite link ( #11609 )
2025-04-10 11:13:27 +00:00
e1bd2047c4
feat(server): add table support for doc parse ( #11508 )
...
fix AF-2478
2025-04-07 09:59:20 +00:00
3792464fa0
fix(server): early exit in doc parse ( #11507 )
2025-04-07 09:30:06 +00:00
ea9de7b542
feat(server): add transcript block indexing ( #11487 )
...
fix AF-2469
2025-04-07 05:51:06 +00:00
70a318f1c4
fix(server): auto-accept pending invitations by link in team workspace ( #11433 )
...
close CLOUD-192
2025-04-03 07:19:14 +00:00
c8392d0cbe
fix(server): auto-accept pending invitations by link ( #11409 )
...
close CLOUD-192
2025-04-02 13:24:03 +00:00
85d176ce6f
chore(server): customize config merge logic ( #11400 )
2025-04-02 09:48:45 +00:00
f2e2072878
feat(server): s3 presigned url ( #11364 )
2025-04-01 15:14:07 +00:00
dad858014f
feat(admin): adapt new config system ( #11360 )
...
feat(server): add test mail api
feat(admin): adapt new config system
2025-04-01 15:00:10 +00:00
eb219b2c48
chore(server): watch storages config updates ( #11367 )
2025-04-01 12:52:45 +00:00
6276732efc
chore(server): reschedule doc merging jobs ( #11318 )
2025-04-01 10:57:54 +00:00
1b93d3d8d2
chore(server): bump nestjs and express ( #11259 )
2025-03-28 14:00:19 +00:00
64c7fb1d66
chore(server): validate function not actually used ( #11263 )
2025-03-28 12:51:19 +00:00
ca301f0dab
chore(server): patch config system ( #11260 )
2025-03-28 08:19:04 +00:00
e22f66f1cc
fix(server): auto import config.json ( #11255 )
2025-03-28 06:12:56 +00:00
69f393fe2f
refactor(server): change invitation request link to workspace members tab ( #11191 )
...
close CLOUD-184
2025-03-28 05:27:20 +00:00
bfa7e9a007
ci: install @types/affine__env on server build ( #11252 )
2025-03-28 05:01:47 +00:00
0ea38680fa
refactor(server): config system ( #11081 )
2025-03-27 12:32:28 +00:00
4d6115bb00
fix(server): move avatar attachment before setting cid reference ( #11231 )
...
close CLOUD-187
2025-03-27 08:00:18 +00:00
5fcdc99f23
feat(server): add team user with team workspace in dev environment ( #11228 )
...
close CLOUD-186
2025-03-27 07:26:28 +00:00
8f124c5070
fix(server): use client doc title when server title is empty ( #11210 )
...
close CLOUD-185
2025-03-27 00:41:23 +00:00
07e098aef1
fix(server): send invitation review notification ( #11203 )
2025-03-26 09:44:03 +00:00
a8c86c5ede
refactor(server): rename settings to user-settings ( #11161 )
2025-03-25 08:47:27 +00:00
4d15c32242
feat(server): add invitation status to getInviteInfo response ( #11158 )
...
close CLOUD-182
2025-03-25 06:51:26 +00:00
9bad6fa12d
feat(server): send review request when team member count over quota limit ( #11126 )
2025-03-25 06:51:26 +00:00
314e5795eb
feat(server): add full content support for doc ( #11149 )
2025-03-25 03:25:41 +00:00
bf5d8b1211
feat(server): get full content for doc embedding ( #11138 )
2025-03-25 01:10:43 +00:00
28f8639aff
feat(server): send invitation review notification ( #10418 )
2025-03-24 03:32:24 +00:00
ed888d6507
feat(server): send invitation accepted notification ( #10421 )
2025-03-24 02:27:24 +00:00
d7b3dc683b
feat(server): send invitation notification ( #10219 )
...
close PD-2307 CLOUD-150
2025-03-24 02:27:23 +00:00
42745f059d
feat(server): send mention email ( #10859 )
...
close CLOUD-170
2025-03-20 09:26:42 +00:00
21c4a29f55
refactor(server): mail service ( #10934 )
2025-03-19 17:00:19 +00:00
89a0880bb3
feat(server): record pending updates count to metrics ( #10991 )
...
close CLOUD-161
2025-03-19 15:10:25 +00:00
33d57b455a
chore(server): revert access control in sync module ( #11011 )
2025-03-19 12:58:56 +00:00
ddd6c97b08
refactor(server): improve workspace content retrieval from database ( #10964 )
2025-03-19 12:16:53 +00:00
d00fd8316d
refactor(server): remove unused randomDoc method ( #10985 )
...
close CLOUD-177
2025-03-19 06:45:22 +00:00
forehalo