chore(dependency): update dependency pg-mem to v3 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pg-mem	^2.8.1 -> ^3.0.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

oguimbal/pg-mem (pg-mem)

v3.0.3

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source

Mainly a refactoring #​411, which now allows preparing statements before executing them.

• Migration of unit tests to Bun
• Supports binding query parameters
• Support of postgres.js, fixes #​386 and thanks to @​smcclure17 to have attempted with #​398
• Can now spawn a postgres server bound to a pg-mem instance, via db.adapter.bindServer() (using pg-server under the hood - ⚠️ NB: this is still very degraded, expect issues with complex use cases) => will help to solve #​27, and fixes #​360

v3.0.0

Compare Source

v2.9.1

Compare Source

forgot this one in the 2.9.0:

• support mixed queries #​410 thanks to @​vacodoceo

v2.9.0

Compare Source

Changes

• adapter now support newer versions of Slonik
• newest version of mikoorm #​361 thanks to @​murbanowicz
• Fix pg-mem crashes when setval has three arguments instead of two #​375 thanks to @​neruchev
• feat(functions): Added concat_ws #​378 thanks to @​Alexnortung
• feat: Support clientConfigurationInput forwarding to slonik. #​382 thanks to @​ovstetun
• export replaceQueryArgs$ from adapters.ts #​385 thanks to @​mmkal
• feat(binary-operators): Added date minus date #​388 thanks to @​Alexnortung
• Fix AST coverage check error #​389 thanks to @​zookatron
• Add GREATEST and LEAST functions #​399 thanks to @​Igggr

Breaking change

• adapter.createSlonik():
  • now does not accept a number argument as query latency (accepts an object as argument)
  • must be awaited

---

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 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: pnpm-lock.yaml

Scope: all 16 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/grammyjs/storages/packages/file:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@grammyjs%2Fstorage-utils: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/grammyjs/storages/packages/file

@grammyjs/storage-utils is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.