fix(deps): update all non-major dependencies

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@commitlint/cli (source)	^21.0.2 → ^21.2.1
@commitlint/config-conventional (source)	^21.0.2 → ^21.2.0
@prisma/adapter-pg (source)	^7.8.0 → ^7.9.1
@prisma/client (source)	^7.8.0 → ^7.9.1
@types/node (source)	^24.13.2 → ^24.13.3
@types/pg (source)	^8.20.0 → ^8.20.3
bullmq (source)	^5.79.1 → ^5.81.3
discord.js (source)	^14.26.4 → ^14.27.0
eslint (source)	^10.5.0 → ^10.8.0
figlet	^1.11.0 → ^1.11.4
lint-staged	^17.0.8 → ^17.3.0
prettier (source)	^3.8.4 → ^3.9.6
prisma (source)	^7.8.0 → ^7.9.1
tsdown (source)	^0.22.3 → ^0.22.14
ws	^8.21.0 → ^8.21.1
yarn (source)	4.17.0 → 4.18.0

---

Release Notes

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

v21.2.1

Compare Source

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

v21.2.0

Compare Source

Features

• resolve-extends: resolve pure-ESM presets (conventional-changelog v7/v9/v10) (#​4859) (fdb566f)

v21.1.0

Compare Source

Features

• cli: add --default-config flag to lint without a config file (#​4805) (7af27ba), closes #​3662

21.0.2 (2026-05-29)

Bug Fixes

• disallow same commit hash for --from and --to (#​4773) (121005e)

21.0.1 (2026-05-12)

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

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

v21.2.0

Compare Source

Features

• resolve-extends: resolve pure-ESM presets (conventional-changelog v7/v9/v10) (#​4859) (fdb566f)

v21.1.0

Compare Source

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

21.0.2 (2026-05-29)

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

21.0.1 (2026-05-12)

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

prisma/prisma (@​prisma/adapter-pg)

v7.9.1

Compare Source

Today, we're issuing a patch release to resolve a security advisory in a transitive dependency of Prisma CLI (via @prisma/dev).

This fixes #​29780.

It does not actually affect @prisma/dev or Prisma CLI so no urgent action is required, but it is recommended to upgrade nevertheless to avoid false positives from security scanners.

v7.9.0

Compare Source

Today, we are excited to share the 7.9.0 stable release 🎉

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Highlights

ORM

Tab completions for the Prisma CLI

Typing out CLI commands from memory is now optional. Prisma ships shell tab completions for bash, zsh, fish, and PowerShell, covering commands, subcommands, options, flags, and even option values.

Setting it up. Most projects run Prisma through a package manager, so completions are enabled through @bomb.sh/tab's package-manager integration — install it once, then source the completion for your package manager and shell:

# 1. Install @​bomb.sh/tab globally
npm install -g @​bomb.sh/tab

# 2. Wire up your package manager + shell (pnpm shown; swap in npm / yarn / bun):
echo 'source <(tab pnpm zsh)'  >> ~/.zshrc            # zsh
echo 'source <(tab pnpm bash)' >> ~/.bashrc           # bash
tab pnpm fish > ~/.config/fish/completions/pnpm.fish  # fish
tab pnpm powershell > ~/.tab-pnpm.ps1                 # PowerShell (then dot-source it from $PROFILE)

@bomb.sh/tab delegates to any locally-installed CLI that ships completions, so pnpm prisma <TAB>, pnpm exec prisma <TAB>, yarn prisma <TAB>, and bun x prisma <TAB> all complete Prisma's commands, options, and values — no per-project setup. (npx and bunx don't support completion themselves; use npm exec and bun x.)

If instead you have Prisma installed globally on your PATH, source its own completion directly: source <(prisma complete zsh) (or the bash / fish / powershell variant).

This is built on @bomb.sh/tab, the same completion library that powers other CLIs in the ecosystem — including Cloudflare, Nuxt, and Vitest — so the package-manager completions you enable for Prisma work for those tools too. A wonderful community contribution from @​AmirSa12 (#​28351) — thank you!

prisma.mp4

Prisma ORM, ready for AI agents

Coding agents are now a first-class audience for Prisma, and 7.9.0 brings the first wave of work to make Prisma projects safe and productive for them to work in.

Agent skills installed with prisma init (#​29689)

prisma init now installs the prisma/skills catalog into freshly scaffolded projects. Agents such as Claude Code, Cursor, Codex, and Windsurf start out with current, version-relevant Prisma knowledge instead of relying on whatever happened to be in their training data. The install is best-effort and never blocks scaffolding; opt out at any time with --no-skills.

npx prisma@latest init

A safer default around destructive commands (#​29684, #​29691, #​29713)

Prisma's AI safety checkpoint refuses to run destructive commands when it detects that an AI agent is at the keyboard, unless the user has given explicit consent. In this release we:

• Broadened agent detection to cover today's landscape — Codex CLI (now on Linux as well as macOS), Qwen Code, GitHub Copilot CLI, OpenCode, Cline, Goose, Amp, Crush, Augment Code, Antigravity, Replit Agent, and Devin — plus generic AI_AGENT / AGENT conventions so future agents are caught without a code change.
• Extended the guard to db push --accept-data-loss, which previously bypassed the checkpoint even though it can drop data.
• Removed the migrate-reset tool from the prisma mcp server entirely — resetting a database drops it, and that is not an operation an agent should be handed as a first-class tool. An agent that needs a reset must run the CLI, where the checkpoint applies.

Bug Fixes

Many of the fixes below are community contributions — thank you to everyone who reported and fixed these!

Prisma Client

• Fixed a severe TypeScript performance regression introduced in Prisma 7: restoring the OmitOpts generic default lets tsc reuse cached type instantiations again, bringing type-checking on large schemas back from minutes to seconds (#​29592, from @​nfl1ryxditimo12).
• The XOR type helper now rejects primitive values such as data: 5, which were previously accepted at compile time even though the runtime rejected them (#​29735, from @​kyungseopk1m).
• $queryRaw and $executeRaw now fail fast with a clear validation error when passed an invalid Date, instead of silently serializing it as null and corrupting the value sent to the database (#​29697, from @​jibin7jose).
• The generated client is no longer corrupted by a /// documentation comment that contains a */ sequence; the comment terminator is now escaped when doc comments are emitted, in both the TypeScript and JavaScript generators (#​29736, from @​kyungseopk1m).
• Improved the runtime and TypeScript error messages shown when a driver adapter is missing from the PrismaClient constructor; both now include a copy-pasteable example and a link to the driver adapters docs (#​29624).
• Unmapped database errors from driver adapters now surface as a user-facing P2039 (PrismaClientKnownRequestError) carrying the original code and message, instead of an opaque failure, which keeps schema-drift-style problems debuggable (#​29512).
• The prisma-client-js generator no longer emits a stray undefined statement when generating from a schema that declares only enums or types and no models (#​29738, from @​kyungseopk1m).
• Fixed a connection leak when an interactive transaction times out (maxWait) while it is still starting: the discarded transaction now sends an explicit ROLLBACK before the connection is returned to the pool, instead of releasing it mid-transaction. Previously, on adapters like @prisma/adapter-pg and @prisma/adapter-neon, the next query to reuse that connection could fail with there is already a transaction in progress — or silently commit the leaked transaction's work (#​29727, from @​lazerg).

CLI

• prisma validate (and other schema-loading commands) no longer hangs forever on a multi-file schema whose directories contain a symlink cycle, and no longer reports the same file twice when a directory is reachable under two spellings (e.g. /tmp → /private/tmp on macOS) (#​29740, from @​kyungseopk1m).
• On Windows, engine binaries are now cached in a stable, user-level directory (%APPDATA%\Prisma) instead of a cwd-relative node_modules\.cache, which eliminated duplicate cache directories and the bloated Serverless/Docker bundles they caused (#​29730, from @​santichausis; closes #​22574, #​6670, #​11577).

Driver Adapters

• @​prisma/adapter-pg, @​prisma/adapter-neon, @​prisma/adapter-ppg: Reading a Bytes column no longer emits Node.js' DEP0005 deprecation warning, thanks to an upstream postgres-bytea bump (#​29538, from @​kolia-zamnius).
• @​prisma/adapter-ppg: ColumnNotFound (P2022) errors now parse both quoted and unquoted PostgreSQL column names, including identifiers containing spaces, matching the fix previously applied to adapter-pg (#​29737, from @​kyungseopk1m).
• @​prisma/adapter-mssql: Setting a Bytes? (@db.VarBinary) field to null no longer fails with an implicit-conversion error; the adapter now sends the parameter typed as VarBinary instead of letting SQL Server default it to nvarchar (#​29630, from @​AnupamKumar-1).

Schema Engine

• prisma migrate status now reports a rolled-back migration that still exists on disk as unapplied, instead of incorrectly treating the schema as up to date (prisma/prisma-engines#5817, from @​goutamadwant).
• Primary-key constraint renames are now rendered as separate ALTER TABLE statements on PostgreSQL, avoiding a database error when a single table has multiple changes in one migration (prisma/prisma-engines#4906, from @​eruditmorina).

Security

• Resolved the hono security advisories at their source: @prisma/dev was updated to a version that no longer depends on hono at all, so the CLI is no longer exposed to those advisories through that path. We also patched moderate-severity advisories in ajv and uuid across production dependencies (#​29514).
• Hardened the Prisma Platform credentials file (~/.config/prisma-platform/auth.json) and its directory to 0o600 / 0o700 so OAuth tokens are no longer world-readable, bringing Prisma in line with the GitHub, AWS, and Google Cloud CLIs (#​29568, from Jaeyoung Yun).
• Bumped the openssl crate in the schema engine binaries from 0.10.74 to 0.10.81 (prisma/prisma-engines#5815).

Prisma Studio

The bundled Prisma Studio moves from 0.27.3 to 0.33.0 (#​29720), gathering up everything shipped in the Studio releases in between.

Migrations view

Studio can now visualise your migration history. This view is powered by Prisma Next — the next major version of Prisma ORM, a full TypeScript rewrite (available now in Early Access) that keeps the schema-first workflow and model-first queries you know, but treats your schema as a versioned, inspectable contract instead of compiling it into a heavy generated client. Prisma Next records every migration and its contract snapshots in the database, and Studio reads them to draw the timeline and diff below. Databases managed with classic Prisma Migrate don't carry this ledger, so the view simply stays hidden there.

When the connected database has a Prisma Next migration ledger, a Migrations entry appears in the sidebar: a newest-first timeline of every applied migration with its name, apply time, operation count, and compact chips summarizing what changed (+2 models, ~2 models +3 fields, +1 model, …). Selecting a migration opens a visual, FigJam-style diff canvas — added, removed, and changed models as colour-coded cards (NEW / UPDATED / UNCHANGED) with per-field before → after details, enum cards, and relation edges — next to a SQL panel of the executed statements and a Prisma-schema line diff. Switching migrations morphs the canvas rather than rebuilding it.

Prisma Streams browser

Studio gains first-class support for Prisma Streams: a dedicated stream browser, live stream aggregations, stream diagnostics, routing-key browsing, and a WAL-history handoff straight from your tables, plus richer stream request observability with concise event-log and OpenTelemetry span summaries.

Working with SQL

• SQL execution, linting, and navigation are now schema-aware: unqualified identifiers resolve against the schema you've selected instead of always falling back to the adapter's default schema.
• SQL result visualizations are rendered with Studio-owned chart configuration, and there's an optional Queries view backed by query-insights snapshots.
• Added copy actions to the Query Details view.

Fixes

• Fixed editing PostgreSQL text-array cells when queries are compiled with inline values.
• Avoided cancelling and repeating introspection requests when Studio first mounts, removing duplicate startup work.

Thanks to our contributors

A heartfelt thank you to the community members whose contributions shaped this release:

@​AmirSa12, @​kyungseopk1m, @​nfl1ryxditimo12, @​jibin7jose, @​santichausis, @​kolia-zamnius, @​goutamadwant, @​eruditmorina, @​lazerg, @​AnupamKumar-1, @​Swapanrishi, @​anupamme, and @​oyi77.

Prisma Compute is now in public beta

"Push code, it runs." Prisma Compute — managed hosting for TypeScript apps that run right next to your database — is now available in public beta, and free to use while the beta lasts.

Compute deploys your app as a long-lived process on Bun, colocated with your Prisma Postgres database, so there are no cold starts, no request timeouts, and no separate hosting vendor to wire up. It's a fit for REST and GraphQL APIs, full-stack apps, streaming and gRPC, and the long-running, stateful AI agents that keep connections open and hold in-process caches — "self-hosting, without the painful parts".

• Push-to-deploy from the CLI or via GitHub integration. Every deployment is an immutable, versioned release with its own preview URL, and rolling back is simply promoting a previous version.
• Branch-based environments — each branch gets its own app and database, so you can preview a change before promoting it to production.
• Auto-wires with Prisma Postgres (or bring any database), with automatic health checks and self-recovery.
• Custom domains — point a single CNAME at Prisma and Compute provisions and renews the TLS certificate for you, with no manual certificate uploads or private-key handling.

With Prisma ORM for type-safe data access, Prisma Postgres for the managed database, and now Prisma Compute for hosting, the whole stack lives in one place. Read the full story in the Prisma Compute blog series.

Enterprise support

Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.

With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.

taskforcesh/bullmq (bullmq)

v5.81.3

Compare Source

Bug Fixes

• deps: update dependency msgpackr to v2.0.5 [security] (#​4387) (6fccb59)
• deps: update dependency redis [security] (#​4369) (2a120df)
• worker: recover blocking client after sentinel disconnect, fixes… (#​4384) (93649b8)

v5.81.2

Compare Source

Bug Fixes

• prevent unhandled rejection when a connection's init fails before an 'error' listener is attached (#​4328) (315ec33)
• telemetry: emit job.state while preserving job.status compatibility (#​4293) (36a3b2a)

v5.81.1

Compare Source

Bug Fixes

• queue: retrieve jobs in same transaction under getJobs (#​4300) (python) (elixir) (php) (rust) (8571503)

v5.81.0

Compare Source

Features

• connection: add Valkey Glide client adapter (#​4321) (e2b89f7)

v5.80.12

Compare Source

Bug Fixes

• bun: match Bun RedisClient callback types and suppress teardown ConnectionClosedError (#​4329) fixes #​4212 (c7bd217)

v5.80.11

Compare Source

Bug Fixes

• worker: emit active event for all jobs moved to active fixes #​3911 (#​4326) (b002d48)

v5.80.10

Compare Source

Bug Fixes

• ci: remove stale OSV ignore (#​4320) (88730b0)

v5.80.9

Compare Source

Performance Improvements

• flow-producer: reuse queue's shared Scripts instance in jobs fixes #​4263 (#​4308) (4f4b574)

v5.80.8

Compare Source

Bug Fixes

• scheduler: walk past stale slots when re-upserting under same id (#​4299) (e8af563)

v5.80.7

Compare Source

Bug Fixes

• worker: move stalled job to failed when fetched manually (#​4294) (c4a0a4a)

v5.80.6

Compare Source

Bug Fixes

• sandbox: preserve child_process exports in null-stdio (#​4301) (5044cf8)

v5.80.5

Compare Source

Bug Fixes

• sandbox: kill children that fail init and surface refusal errors fixes #​4283 (#​4284) (7dd064e)

v5.80.4

Compare Source

Bug Fixes

• deps: update dependency ioredis to v5.11.1 [security] (#​4282) (d978d72)

v5.80.3

Compare Source

Bug Fixes

• fix potential job id integer to string conversion (#​4262) (4e8b595)

v5.80.2

Compare Source

Bug Fixes

• job-scheduler: respect offset option in upsertJobScheduler (elixir) (rust) (#​3993) (78bbb25)

v5.80.1

Compare Source

Bug Fixes

• job: enforce priority max of 2^21-1 to preserve FIFO at the boundary (#​4261) (418de1e)

v5.80.0

Compare Source

v5.79.4

Compare Source

Bug Fixes

• job-scheduler: coerce string offset in Lua helper (#​4266) (python) (elixir) (5a88614)

v5.79.3

Compare Source

Bug Fixes

• queue-events: correct delay event number type and documentation (#​3989) (6ffd88a)

v5.79.2

Compare Source

Bug Fixes

• flow: use correct data structure when retrying failed child using ignoreDependencyOnFailure fixes #​4235 (#​4236) (6f1b2e3)

discordjs/discord.js (discord.js)

v14.27.0

Compare Source

Bug Fixes

• Update clientReady event name references (#​10632) (9592aea)
• InteractionResponses: Optional parameter for update() (#​10797) (fbda4fe)
• guide: Miscellaneous fixes (#​11147) (c53c8c2)
• GuildChannel: Manageable perm check (#​11166) (8b342a1)
• StageInstanceManager#create: Correctly resolve guildScheduledEvent (#​11540) (0aabb6c)
• RoleManager: Allow null in RoleColorsResolvable to clear gradient colors (#​11536) (221680d)
• GuildChannel: Handle empty overwrite must only handle @​everyone (#​11221) (1e2fdf4)

Documentation

• Attachment: string property (d646a13)
• Fix close tags (#​10756) (4349e10)
• Replace Discord API with Discord Developers (#​10968) (538457c)
• Clarify wording for maximum values (#​11231) (9ec73fa)
• Fix incorrect casing in the ready event deprecation (#​11574) (0df0628)
• Fix typos and duplicated words in comments and guide (#​11502) (63cd992)

Features

• Send voice messages (#​11493) (fed811a)
• Guild: Add maximumStageBitrate (#​11313) (6d2cd99)
• Proper authorizing integration owners structure (#​11366) (b6db455)
• RoleManager: Add fetchMemberCounts (#​11352) (3b738ee)
• Emit voiceServerUpdate event (#​11414) (74a42bf)
• GuildMember: Add collectibles (#​11468) (b0e6aff)
• Add shared client theme support (#​11454) (16fd248)
• ClientApplication: Add fetchActivityInstance method (#​11481) (24a0606)

Refactor

• Reorder imports (40b7a60)

Typings

• WebhookMessageCreateOptions: Omit sharedClientTheme (b816b79)
• Message: Specify rawData arg type (#​11123) (c4531d4)
• UserManager: Fix send() return type to Promise<Message> (#​11337) (07c4127)

v14.26.5

Compare Source

Bug Fixes

• Detect spoiler attachments with flag (v14) (#​11561) (ce29ae9)

eslint/eslint (eslint)

v10.8.0

Compare Source

Features

• 2fee9bb feat: export ConfigObject from eslint/config (#​21082) (sethamus)

Bug Fixes

• 6b8d2f7 fix: escape reserved characters in rule id in html formatter (#​21129) (Francesco Trotta)
• 9091071 fix: prevent no-unreachable-loop crash when all loop types are ignored (#​21116) (Pixel)
• e23fafe fix: prefer-object-spread add semicolon when adding parenthesis (#​21081) (synthex-byte)
• 20b5ad0 fix: quadratic-time regex in prefer-template (#​21096) (Milos Djermanovic)
• 8b6f6c0 fix: apply ignore configs to computed methods in class-methods-use-this (#​21094) (Pixel)
• b2c608c fix: NewExpression with parenthesized callee in preserve-caught-error (#​21083) (Francesco Trotta)

Documentation

• 6ddf858 docs: fix broken Specify Parser Options anchor link (#​21106) (Minsu)
• 784dfbe docs: Clarify no-eq-null description (#​21120) (Park Harin)
• 7ec733a docs: Fix typos and grammar in glossary (#​21095) (Marry (Subin Yang))
• 92bb13f docs: replace quake link (#​21108) (Jung Hyeon Jun)
• 68eb4a5 docs: fix broken Specify Globals anchor links in rule pages (#​21103) (Minsu)
• d28f697 docs: replace Code Climate CLI links with Qlty CLI links (#​21099) (Jung Hyeon Jun)
• eccc68d docs: correct --suppressions-location option description (#​21093) (Ga eun Lee)
• c5963f7 docs: Update README (GitHub Actions Bot)

Chores

• 4fbf46d test: pin webpack version to 5.108.4 (#​21137) (Francesco Trotta)
• 2d063e2 chore: update HTTP URLs to HTTPS in JSDoc and comments (#​21101) (Bo Hyun Kim)
• eccbe7b test: add error locations to no-class-assign (#​21123) (devoil)
• e7d1e43 ci: bump actions/setup-go from 6 to 7 (#​21118) (dependabot[bot])
• e9d66d0 ci: bump actions/setup-node from 6 to 7 (#​21119) (dependabot[bot])
• ee225b6 test: Add error location details to no-eq-null rule (#​21117) (Park Harin)
• 044a627 chore: update minimatch to ^10.2.5 (#​21107) (김채영)
• fb09aa8 chore: update ecosystem plugins (#​21115) (ESLint Bot)
• 5abd878 test: add error locations to no-proto (#​21114) (Gihyeon Jeong / 정기현)
• 9715887 test: Add error location details to no-div-regex (#​21110) (Park Harin)
• a746ec6 test: add error locations to no-new-wrappers (#​21109) (Gihyeon Jeong / 정기현)
• 8dde645 test: add error locations to no-ex-assign (#​21102) (devoil)
• 13ab0ec test: add error locations to no-label-var (#​21098) (Gihyeon Jeong / 정기현)
• a99906f test: Add error location details to no-delete-var rule (#​21105) (Park Harin)
• c47e8dc chore: add missing backticks to languages/js/index.js (#​21104) (beeen)
• 0174428 chore: add missing backticks to translate-cli-options.js (#​21097) (dongkyu lee)
• 3d36589 chore: add missing backticks to serialization.js (#​21091) (이규환)
• dcc9312 test: add error locations to eqeqeq (#​21090) (Ga eun Lee)
• 2710b18 ci: Add explicit permissions to rebuild-docs-sites workflow (#​21089) (Marry (Subin Yang))
• 5d2f866 chore: update dependency prettier to v3.9.5 (#​21086) (renovate[bot])
• d584e31 chore: fix failing ecosystem test for eslint-plugin-unicorn (#​21084) (Francesco Trotta)
• bf3eda0 chore: update ecosystem plugins (#​21079) (ESLint Bot)

v10.7.0

Compare Source

Features

• cf2a9bf feat: add errorClassNames option to preserve-caught-error rule (#​21032) (sethamus)
• f8b873a feat: max-nested-callbacks option for constructor callbacks (#​21063) (fnx)
• 557fde8 feat: support computed Number.parseInt member access in radix rule (#​21041) (Pixel)
• 0b4a73b feat: add suggestions to no-compare-neg-zero (#​21034) (den$)
• 96cdd42 feat: report invalid signed numeric radix values in radix rule (#​21030) (Pixel)

Bug Fixes

• 3e7bf15 fix: apply ignoreClassesWithImplements to class expressions (#​21069) (Pixel)
• 0d7d70c fix: insert cause outside wrapping parens in preserve-caught-error (#​21062) (Mahin Anowar)
• 75ec753 fix: handle static template literals in eqeqeq rule (#​21058) (Pixel)
• b717a22 fix: prevent eqeqeq null option from reporting non-equality operators ([#​2105

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 12pm on Sunday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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: yarn.lock

➤ YN0000: · Yarn 4.18.0
➤ YN0000: ┌ Resolution step
➤ YN0016: │ @types/pg@npm:^8.20.3: All versions satisfying "^8.20.3" are quarantined
➤ YN0000: └ Completed in 6s 616ms
➤ YN0000: · Failed with errors in 6s 630ms

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud