fix(deps): 🐛 🔗 update all dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update	Pending
@apollo/server (source)	4.9.5 -> 4.10.0					dependencies	minor
@aws-sdk/client-cloudformation (source)	3.461.0 -> 3.490.0					dependencies	minor
@aws-sdk/client-lambda (source)	3.461.0 -> 3.490.0					dependencies	minor
@commitlint/cli (source)	18.4.3 -> 18.4.4					devDependencies	patch
@commitlint/config-conventional (source)	18.4.3 -> 18.4.4					devDependencies	patch
@commitlint/types (source)	18.4.3 -> 18.4.4					devDependencies	patch
@graphql-tools/utils (source)	10.0.11 -> 10.0.12					dependencies	patch
@prisma/client (source)	5.6.0 -> 5.8.0					dependencies	minor	5.8.1
@smithy/util-waiter (source)	2.0.14 -> 2.0.16					dependencies	patch
@types/aws-lambda (source)	8.10.129 -> 8.10.131					devDependencies	patch
@types/lint-staged (source)	13.2.2 -> 13.3.0					devDependencies	minor
@types/node (source)	20.10.4 -> 20.11.0					devDependencies	minor	20.11.5 (+4)
@typescript-eslint/eslint-plugin (source)	6.13.1 -> 6.18.1					devDependencies	minor	6.19.0
@typescript-eslint/parser (source)	6.13.1 -> 6.18.1					devDependencies	minor	6.19.0
actions/cache	704facf -> e12d46a					action	digest
actions/setup-node	8f152de -> b39b52d					action	digest
aws-cdk (source)	2.111.0 -> 2.121.1					devDependencies	minor
aws-cdk-lib (source)	2.111.0 -> 2.121.1					dependencies	minor
aws-cdk-lib (source)	2.111.0 -> 2.121.1					devDependencies	minor
csv-parse (source)	5.5.2 -> 5.5.3					dependencies	patch
csv-stringify (source)	6.4.4 -> 6.4.5					dependencies	patch
esbuild	0.19.8 -> 0.19.11					devDependencies	patch
eslint (source)	8.54.0 -> 8.56.0					devDependencies	minor
eslint-config-prettier	9.0.0 -> 9.1.0					devDependencies	minor
eslint-config-turbo (source)	1.10.16 -> 1.11.3					devDependencies	minor
eslint-plugin-import	2.29.0 -> 2.29.1					devDependencies	patch
lint-staged	15.1.0 -> 15.2.0					devDependencies	minor
pnpm (source)	8.11.0 -> 8.14.1					packageManager	minor
prettier (source)	3.1.0 -> 3.2.2					devDependencies	minor	3.2.3
prettier-plugin-packagejson	2.4.6 -> 2.4.9					devDependencies	patch
prettier-plugin-sql (source)	0.17.0 -> 0.18.0					devDependencies	minor
prisma (source)	5.6.0 -> 5.8.0					devDependencies	minor	5.8.1
tsx	4.6.0 -> 4.7.0					devDependencies	minor
turbo (source)	1.10.16 -> 1.11.3					devDependencies	minor
typescript (source)	5.3.2 -> 5.3.3					devDependencies	patch

---

Release Notes

apollographql/apollo-server (@​apollo/server)

v4.10.0

Compare Source

Minor Changes

• #​7786 869ec98 Thanks @​ganemone! - Restore missing v1 skipValidation option as dangerouslyDisableValidation. Note that enabling this option exposes your server to potential security and unexpected runtime issues. Apollo will not support issues that arise as a result of using this option.

• #​7803 e9a0d6e Thanks @​favna! - allow stringifyResult to return a Promise<string>

  Users who implemented the stringifyResult hook can now expect error responses to be formatted with the hook as well. Please take care when updating to this version to ensure this is the desired behavior, or implement the desired behavior accordingly in your stringifyResult hook. This was considered a non-breaking change as we consider that it was an oversight in the original PR that introduced stringifyResult hook.

Patch Changes

• #​7793 9bd7748 Thanks @​bnjjj! - General availability of subscription callback protocol

• #​7799 63dc50f Thanks @​stijnbe! - Fix type of ApolloServerPluginUsageReporting reportTimer

• #​7740 fe68c1b Thanks @​barnisanov! - Uninstalled body-parser and used express built-in body-parser functionality instead(mainly the json middleware)

aws/aws-sdk-js-v3 (@​aws-sdk/client-cloudformation)

v3.490.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.489.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.485.0

Compare Source

Features

• credential-providers: add credentialScope field (#​5606) (04c1459)

v3.484.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.481.0

Compare Source

Features

• codegen for command class builder (#​5604) (4835de4)

v3.478.0

Compare Source

Features

• codegen for paginator factory (#​5590) (e54099b)

v3.477.0

Compare Source

Features

• xml codegen reduction (#​5566) (3ed7c81)

v3.476.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.474.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.473.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.470.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.468.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.467.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.466.0

Compare Source

Features

• client-cloudformation: Including UPDATE_* states as a success status for CreateStack waiter. (e8ef172)

v3.465.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

v3.462.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-cloudformation

aws/aws-sdk-js-v3 (@​aws-sdk/client-lambda)

v3.490.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.489.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.485.0

Compare Source

Features

• credential-providers: add credentialScope field (#​5606) (04c1459)

v3.484.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.481.0

Compare Source

Features

• codegen for command class builder (#​5604) (4835de4)

v3.478.0

Compare Source

Features

• codegen for paginator factory (#​5590) (e54099b)

v3.477.0

Compare Source

Features

• xml codegen reduction (#​5566) (3ed7c81)

v3.476.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.474.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.473.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.470.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.468.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.465.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

v3.462.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-lambda

conventional-changelog/commitlint (@​commitlint/cli)

v18.4.4

Compare Source

Note: Version bump only for package @​commitlint/cli

conventional-changelog/commitlint (@​commitlint/config-conventional)

v18.4.4

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

conventional-changelog/commitlint (@​commitlint/types)

v18.4.4

Compare Source

Note: Version bump only for package @​commitlint/types

ardatan/graphql-tools (@​graphql-tools/utils)

v10.0.12

Compare Source

Patch Changes

• 5ae0394 Thanks @​ardatan! - Print comments as blocks

prisma/prisma (@​prisma/client)

v5.8.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or posting on X about the release. 🌟

Highlights

Happy New Year from your friends at Prisma! 🎊

In the last 4 weeks, we resolved some bugs on the ORM and made some progress on some exciting features that we’re not yet ready to announce. Stay tuned for the upcoming releases, in which we’ll be announcing new features. 😉

relationJoins improvements: Relation loading strategy per query (Preview)

In version 5.7.0, we released relationJoins into Preview. The relationJoins feature enables support for JOINs for relation queries.

This release adds support for the ability to specify the strategy used to fetch relational data per query when the Preview feature is enabled. This will enable you to choose the most efficient strategy for fetching relation data depending on your use case.

You can now load relation data using either of the following strategies:

• join — uses JOINs to fetch relation data
• query — uses sub-queries to fetch relation data

When the relationJoins Preview feature is enabled, by default, the relation fetching strategy used is join. You can override the default behavior by using the relationLoadStrategy query option.

To get started, enable the Preview feature:

// schema.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["relationJoins"]
}

… and specify the relation loading strategy for your query as follows:

await prisma.user.findMany({
  relationLoadStrategy: 'query',
  include: {
    posts: true,
  },
})

Try it out and share your feedback and create a bug report if you encounter any issues.

Survey: Edge functions support

We’re working on bringing Edge function support to Prisma ORM and we would appreciate your input by submitting a response to our survey. By filling out the survey, you will be considered for our Early Access cohort as soon as we have something for you to try out.

Fixes and improvements

Prisma Client

• Log output of Node-API library engine is different
• target and timestamp are undefined in info events in Data Proxy client
• Wrong types of timestamp and duration in query events with Data Proxy
• Using citext fields with neon database driver causes conversion error
• Add FreeBSD 14 as a new platform
• PostgresError { code: "54023", message: "cannot pass more than 100 arguments to a function", severity: "ERROR", detail: None, column: None, hint: None }
• Int[] return as null

Prisma Migrate

• Prisma Migrate errors with Environment is non-interactive when VERCEL env var is defined

Language tools (e.g. VS Code)

• Add quickfix for Error validating field 'id' in model 'Post': MongoDB '@​default(auto())' fields must have 'ObjectId' native type.
• Append mention of update to "preview feature not known" error message

Credits

Huge thanks to @​anuraaga, @​onichandame, @​LucianBuzzo, @​RobertCraigie, @​fqazi, @​KhooHaoYit, @​alencardc, @​Oreilles, @​tinola, @​AikoRamalho, @​luxaritas for helping!

Company news

🎉 A billion queries and counting: Prisma Accelerate

Prisma Accelerate, our global database cache has served over 1 billion queries since its General Availability launch.

We’d like to give a shoutout to our team and everyone who’s been with us on this journey. Stay tuned for some exciting products and features in the pipeline for 2024!

🔮 Prisma ORM Ecosystem

Are you building a cool tool, extension, generator, CLI tool or anything else, for Prisma ORM? Let us know.

We would like to learn about it and feature it on our Ecosystem page.

💼 We’re hiring

If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you. Check out our Careers page for open positions.

v5.7.1

Compare Source

Today, we are issuing the 5.7.1 patch release.

This patch fixes multiple small problems in our relationJoins preview feature. If you ran into problems when testing relationJoins before, please give it another go with 5.7.1 and share your feedback or create a bug report if you encounter any issues.

Fixes in Prisma Client

• relationJoins: Int[] return as null
• relationJoins: fails when filtering includes by isNot: null
• relationJoins: "The table (not available) does not exist in the current database."
• relationJoins: PostgresError { code: "54023", message: "cannot pass more than 100 arguments to a function", severity: "ERROR", detail: None, column: None, hint: None }
• relationJoins: Inconsistent column data: Unexpected conversion failure from String to datetime. Reason: $trailing input

v5.7.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or posting on X (formerly Twitter) about the release.

Highlights

✨ In this release, we improved the SQL queries Prisma Client generates for you with two new Preview features, the driver adapters, and support for the database drivers we currently support. 5.7.0 will be the last release of the year. Stay tuned for the next one in January! ✨

Preview support for JOINs for relation queries for PostgreSQL and CockroachDB

We’re excited to announce Preview support for JOINs in Prisma Client when querying relations. Support for JOINs has been a long-standing feature request, and this release adds support for PostgreSQL and CockroachDB. The upcoming releases will expand support for other databases Prisma supports.

To get started using JOINs, enable the Preview feature in your Prisma schema:

// schema.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["relationJoins"]
}

Run prisma generate to regenerate Prisma Client and enable the Preview feature.

Prisma Client will use a JOIN in your query to fetch relation data for a majority of the cases.

Example queries

1-1 relation queries example

Prisma Client query

await prisma.user.findUnique({
	where: {
		id: 1
	},
	include: {
		profile: true
	}
})

SQL

SELECT
	"t1"."id",
	"t1"."name",
	"User_profile"."__prisma_data__" AS "profile"
FROM
	"public"."User" AS "t1"
	LEFT JOIN LATERAL (
		SELECT
			COALESCE(JSON_AGG("__prisma_data__"), '[]') AS "__prisma_data__"
		FROM
			(
				SELECT
					"t4"."__prisma_data__"
				FROM
					(
						SELECT
							JSON_BUILD_OBJECT(
								'id',
								"t3"."id",
								'bio',
								"t3"."bio",
								'userId',
								"t3"."userId"
							) AS "__prisma_data__"
						FROM
							(
								SELECT
									"t2".*
								FROM
									"public"."Profile" AS "t2"
								WHERE
									"t1"."id" = "t2"."userId"
							) AS "t3"
					) AS "t4"
			) AS "t5"
	) AS "User_profile" ON TRUE
WHERE "t1"."id" = $1
LIMIT $2

1-m relation queries example

Prisma Client query

await prisma.user.findUnique({
	where: {
		id: 1
	},
	include: {
		posts: true
	}
})

SQL

SELECT
	"t1"."id",
	"t1"."name",
	"User_posts"."__prisma_data__" AS "posts"
FROM
	"public"."User" AS "t1"
	LEFT JOIN LATERAL (
		SELECT
			COALESCE(JSON_AGG("__prisma_data__"), '[]') AS "__prisma_data__"
		FROM
			(
				SELECT
					"t4"."__prisma_data__"
				FROM
					(
						SELECT
							JSON_BUILD_OBJECT(
								'id',
								"t3"."id",
								'title',
								"t3"."title",
								'content',
								"t3"."content",
								'published',
								"t3"."published",
								'authorId',
								"t3"."authorId"
							) AS "__prisma_data__"
						FROM
							(
								SELECT
									"t2".*
								FROM
									"public"."Post" AS "t2"
								WHERE
									"t1"."id" = "t2"."authorId"
									/* root select */
							) AS "t3"
							/* inner select */
					) AS "t4"
					/* middle select */
			) AS "t5"
			/* outer select */
	) AS "User_posts" ON TRUE
WHERE "t1"."id" = $1
LIMIT $2

m-n relation queries example

Prisma Client query

await prisma.post.findUnique({
	where: {
		id: 1
	},
	include: {
		tags: true
	}
})

SQL

SELECT
	"t1"."id",
	"t1"."title",
	"t1"."content",
	"t1"."published",
	"t1"."authorId",
	"Post_tags_m2m"."__prisma_data__" AS "tags"
FROM
	"public"."Post" AS "t1"
	LEFT JOIN LATERAL (
		SELECT
			COALESCE(JSON_AGG("__prisma_data__"), '[]') AS "__prisma_data__"
		FROM
			(
				SELECT
					"Post_tags"."__prisma_data__"
				FROM
					"public"."_PostToTag" AS "t2"
					LEFT JOIN LATERAL (
						SELECT
							JSON_BUILD_OBJECT('id', "t4"."id", 'name', "t4"."name") AS "__prisma_data__",
							"t4"."id"
						FROM
							(
								SELECT
									"t3".*
								FROM
									"public"."Tag" AS "t3"
								WHERE
									"t2"."B" = "t3"."id"
									/* root select */
							) AS "t4"
					) AS "Post_tags" ON TRUE
				WHERE
					"t2"."A" = "t1"."id"
			) AS "Post_tags_m2m_1"
	) AS "Post_tags_m2m" ON TRUE
WHERE "t1"."id" = $1
LIMIT $2

Share your feedback and create a bug report if you encounter any issues.

Prisma’s distinct option now uses SQL queries (Preview)

From this release, Prisma Client’s distinct option now uses the native SQL DISTINCT ON for unordered queries with PostgreSQL and CockroachDB. The upcoming releases will expand support for the other databases that Prisma supports.

Prisma Client already supports querying for distinct records. However, Prisma Client took care of the post-processing for distinct records in memory.

To get started, enable the Preview feature in your Prisma schema:

// schema.prisma
generator client {
  provide

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "before 4am on the first day of the month" (UTC), 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.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/icssc/peterportal-api-next).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4xMDMuMSIsInVwZGF0ZWRJblZlciI6IjM3LjEzNS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->