Update dependency drizzle-orm to ^0.45.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
drizzle-orm (source)	^0.44.5 → ^0.45.0

---

Release Notes

drizzle-team/drizzle-orm (drizzle-orm)

v0.45.2

Compare Source

• Fixed sql.identifier(), sql.as() escaping issues. Previously all the values passed to this functions were not properly escaped
  causing a possible SQL Injection (CWE-89) vulnerability

Thanks to @​EthanKim88, @​0x90sh and @​wgoodall01 for reaching out to us with a reproduction and suggested fix

v0.45.1

Compare Source

• Fixed pg-native Pool detection in node-postgres transactions breaking in environments with forbidden require() (#​5107)

v0.45.0

Compare Source

• Fixed pg-native Pool detection in node-postgres transactions
• Allowed subqueries in select fields
• Updated typo algorythm => algorithm
• Fixed $onUpdate not handling SQL values (fixes #​2388, tests implemented by L-Mario564 in #​2911)
• Fixed pg mappers not handling Date instances in bun-sql:postgresql driver responses for date, timestamp types (fixes #​4493)

v0.44.7

Compare Source

• fix durable sqlite transaction return value #​3746 - thanks @​joaocstro

v0.44.6

Compare Source

• feat: add $replicas reference #​4874

---

Configuration

📅 Schedule: (UTC)

• 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 this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: next-auth@4.21.1
npm error Found: nodemailer@7.0.6
npm error node_modules/nodemailer
npm error   nodemailer@"^7.0.6" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional nodemailer@"^6.6.5" from next-auth@4.21.1
npm error node_modules/next-auth
npm error   next-auth@"~4.21.1" from the root project
npm error   peer next-auth@"~4.21.1" from @sidebase/nuxt-auth@1.1.0
npm error   node_modules/@sidebase/nuxt-auth
npm error     @sidebase/nuxt-auth@"1.1.0" from the root project
npm error     1 more (@dcc-bs/authentication.bs.js)
npm error
npm error Conflicting peer dependency: nodemailer@6.10.1
npm error node_modules/nodemailer
npm error   peerOptional nodemailer@"^6.6.5" from next-auth@4.21.1
npm error   node_modules/next-auth
npm error     next-auth@"~4.21.1" from the root project
npm error     peer next-auth@"~4.21.1" from @sidebase/nuxt-auth@1.1.0
npm error     node_modules/@sidebase/nuxt-auth
npm error       @sidebase/nuxt-auth@"1.1.0" from the root project
npm error       1 more (@dcc-bs/authentication.bs.js)
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-05-07T18_49_05_646Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-07T18_49_05_646Z-debug-0.log