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
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
1bb324eeed
feat(server): update gql endpoint & workspace doc match test ( #11104 )
2025-03-25 10:09:22 +00:00
fengmk2
a8c86c5ede
refactor(server): rename settings to user-settings ( #11161 )
2025-03-25 08:47:27 +00:00
fengmk2
28f8639aff
feat(server): send invitation review notification ( #10418 )
2025-03-24 03:32:24 +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
darkskygit
d8373f66e7
feat(server): context awareness for copilot ( #9611 )
...
fix PD-2167
fix PD-2169
fix PD-2190
2025-03-13 11:44:55 +00:00
forehalo
ea72599bde
feat(server): ban account ( #10761 )
...
close CLOUD-158
2025-03-12 02:52:18 +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
43ded6aa38
feat(server): add blocked state to workspace docs ( #10585 )
...
close CLOUD-162
2025-03-05 12:49:33 +00:00
liuyi
61162c59fc
refactor(server): permission ( #10449 )
2025-03-05 15:57:00 +08:00
darkskygit
a725df6ebe
feat(server): basic context api ( #10056 )
...
fix CLOUD-97
fix CLOUD-98
2025-02-11 10:45:01 +00:00
forehalo
0b9d30b55a
refactor: rename all page query to doc ( #10019 )
2025-02-07 11:40:59 +00:00
Brooooooklyn
41107eafae
feat(server): allow to set default role in page ( #9963 )
2025-02-06 17:18:50 +00:00
forehalo
7c7febd495
refactor(server): remove never used column in page permission ( #9985 )
2025-02-06 10:52:05 +00:00
forehalo
7826e2b7c8
refactor(server): use feature model ( #9932 )
2025-02-05 10:27:26 +00:00
Brooooooklyn
abeff8bb1a
feat(server): doc level permission ( #9760 )
...
close CLOUD-89 CLOUD-90 CLOUD-91 CLOUD-92
2025-02-05 07:06:57 +00:00
forehalo
d03447f52e
fix(server): should redeem onetime invoice only once ( #9927 )
...
fix CLOUD-115
2025-02-02 09:18:06 +00:00
forehalo
994d758c07
feat(server): support selfhost licenses ( #8947 )
2025-01-22 10:21:07 +00:00
forehalo
2f80b4f822
feat(nbstore): add cloud implementation ( #8810 )
2024-12-10 10:48:27 +00:00
DarkSky
9365958a02
feat(server): team quota ( #8955 )
2024-12-09 18:51:54 +09:00
forehalo
5bf8ed1095
feat(server): support team workspace subscription ( #8919 )
...
close AF-1724, AF-1722
2024-12-05 08:31:01 +00:00
forehalo
4055e3aa67
refactor(server): payment service ( #8906 )
2024-12-05 08:31:00 +00:00
forehalo
69fb5c06f4
feat(server): support onetime payment subscription ( #8369 )
2024-10-10 10:12:40 +00:00
forehalo
0add8917f9
feat(server): enable share og information for docs ( #7794 )
2024-09-10 04:03:52 +00:00
darkskygit
34eac4c24e
feat: improve ai query performance ( #8170 )
2024-09-09 09:39:28 +00:00
darkskygit
2a135d8a93
feat: add index for snapshots ( #8163 )
2024-09-08 13:49:41 +00:00
forehalo
63e1fce3ca
perf(server): accelerate user workspace permission queries ( #8161 )
2024-09-08 12:04:00 +00:00
forehalo
be4df0f8ac
fix(server): created user in update table should not have defualt value ( #8134 )
2024-09-06 06:42:04 +00:00
forehalo
8b0afd6eeb
refactor(server): auth ( #7994 )
2024-09-03 09:03:39 +00:00
darkskygit
d93d39e29d
feat: add editor record ( #7938 )
...
fix CLOUD-58, CLOUD-61, CLOUD-62, PD-1607, PD-1608
2024-09-02 09:37:39 +00:00
forehalo
e20bdbf925
feat(server): make server storage adapters ( #7902 )
2024-08-21 05:30:26 +00:00
darkskygit
339c39c1ec
feat: improve prompt management ( #7853 )
2024-08-14 08:38:36 +00:00
liuyi
171a974904
fix(server): use timestamp with timezone ( #7847 )
2024-08-13 15:32:24 +08:00
forehalo
4ec89ebd69
chore(server): standardize server db names and columns ( #7674 )
2024-07-31 07:59:23 +00:00
darkskygit
bf6c9a5955
feat: add prompt level config ( #7445 )
2024-07-08 08:11:22 +00:00
forehalo
de91027852
feat(server): support lifetime subscription ( #7405 )
...
closes CLOUD-48
- [x] lifetime subscription quota
- [ ] tests
2024-07-08 07:41:26 +00:00
darkskygit
61870c04d0
feat: fork session support ( #7367 )
2024-07-03 03:10:09 +00:00
forehalo
638fc62601
feat(server): runtime setting support ( #5602 )
...
---
<details open="true"><summary>Generated summary (powered by <a href="https://app.graphite.dev ">Graphite</a>)</summary>
> ## TL;DR
> This pull request adds a new migration file, a new model, and new modules related to runtime settings. It also introduces a new `Runtime` service that allows getting, setting, and updating runtime configurations.
>
> ## What changed
> - Added a new migration file `migration.sql` that creates a table called `application_settings` with columns `key` and `value`.
> - Added a new model `ApplicationSetting` with properties `key` and `value`.
> - Added a new module `RuntimeSettingModule` that exports the `Runtime` service.
> - Added a new service `Runtime` that provides methods for getting, setting, and updating runtime configurations.
> - Modified the `app.module.ts` file to import the `RuntimeSettingModule`.
> - Modified the `index.ts` file in the `fundamentals` directory to export the `Runtime` service.
> - Added a new file `def.ts` in the `runtime` directory that defines the runtime configurations and provides a default implementation.
> - Added a new file `service.ts` in the `runtime` directory that implements the `Runtime` service.
>
> ## How to test
> 1. Run the migration script to create the `application_settings` table.
> 2. Use the `Runtime` service to get, set, and update runtime configurations.
> 3. Verify that the runtime configurations are stored correctly in the database and can be retrieved and modified using the `Runtime` service.
>
> ## Why make this change
> This change introduces a new feature related to runtime settings. The `Runtime` service allows the application to dynamically manage and modify runtime configurations without requiring a restart. This provides flexibility and allows for easier customization and configuration of the application.
</details>
2024-05-28 06:43:53 +00:00
darkskygit
5ba9e2e9b1
fix: choose provider correctly ( #7081 )
...
fix no provider error in caption generate action
2024-05-27 09:57:39 +00:00
darkskygit
937b8bf166
feat: history cleanup ( #7007 )
...
fix AFF-1069
2024-05-24 08:00:05 +00:00
darkskygit
13f40f435d
feat: improve query performence ( #6764 )
2024-05-06 09:12:04 +00:00
darkskygit
9f349a2300
feat: text to image impl ( #6437 )
...
fix CLOUD-18
fix CLOUD-28
fix CLOUD-29
2024-04-10 12:13:39 +00:00
darkskygit
7c38a54f81
feat: copilot controller ( #6272 )
...
fix CLOUD-27
2024-04-10 11:58:40 +00:00
darkskygit
46a368d7f1
feat: add session impl ( #6254 )
2024-04-10 11:15:25 +00:00
