Skip to content

fix(deps): update all non-major npm dependencies - #166

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-non-major-npm-dependencies
Open

fix(deps): update all non-major npm dependencies#166
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-non-major-npm-dependencies

Conversation

@renovate

@renovate renovate Bot commented May 29, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@auth/core (source) 0.34.3 → 0.41.3 age confidence
@prisma/adapter-pg (source) 7.8.0 → 7.10.0 age confidence
@prisma/client (source) 7.8.0 → 7.10.0 age confidence
@types/node (source) 22.19.19 → 22.20.5 age confidence
@types/pg (source) 8.20.0 → 8.23.1 age confidence
@types/react (source) 19.2.15 → 19.3.0 age confidence
@types/react-dom (source) 19.2.3 → 19.3.0 age confidence
@typescript-eslint/eslint-plugin (source) 8.60.0 → 8.71.1 age confidence
@typescript-eslint/parser (source) 8.60.0 → 8.71.1 age confidence
eslint (source) 9.39.4 → 9.39.5 age confidence
eslint-config-next (source) 16.2.6 → 16.4.0 age confidence
eslint-plugin-prettier 5.5.5 → 5.5.6 age confidence
next (source) 16.2.6 → 16.4.0 age confidence
next-auth (source) 4.24.14 → 4.24.15 age confidence
pg (source) 8.21.0 → 8.23.1 age confidence
prettier (source) 3.8.3 → 3.9.9 age confidence
prisma (source) 7.8.0 → 7.10.0 age confidence
react (source) 19.2.6 → 19.3.0 age confidence
react-dom (source) 19.2.6 → 19.3.0 age confidence
swr (source) 2.4.1 → 2.5.1 age confidence

Release Notes

nextauthjs/next-auth (@​auth/core)

v0.41.3

Compare Source

Bugfixes
  • core: getToken() now returns null instead of throwing when the Authorization header contains a malformed Bearer value
  • core: OAuth state, nonce, and PKCE check cookies are now bound to the provider that created them and are rejected when a different provider handles the callback
  • core: email addresses are Unicode-normalized (NFKC) before validation in the default email normalizer, closing a homoglyph @ bypass
Other
  • deps: resolve Dependabot alerts via cross-major dependency upgrades (#​13449)
  • deps: resolve Dependabot security advisories via pnpm overrides (#​13441)
  • deps: allow nodemailer 8 in peer dependency ranges (#​13434)
  • CI formatting and proxy deploy repairs (#​13444)

v0.41.2

Compare Source

Bugfixes
  • providers: add issuer to GitHub provider for RFC 9207 compliance (#​13410)
Other
  • sync package versions with npm registry (#​13414)

v0.41.1

Compare Source

Bugfixes
Other
  • update links for Credentials-based Authentication (#​13258)

v0.41.0

Compare Source

Features

Other

  • fix build
  • adjust default fusionauth provider details (#​10868)

v0.40.0

Compare Source

Features

Bugfixes

Other

v0.39.1

Compare Source

Bugfixes

Other

v0.39.0

Compare Source

Features

  • providers: Add HuggingFace provider (#​12884) (c1f89ea)
  • providers: Improve error validation for Microsoft EntraID provider errors before decoding token (#​12876) (a05451d)

Other

v0.38.0

Compare Source

Features

Bugfixes

  • core: handle an error inside parseProviders() when providerId not found in config (#​12438) (80a2c14)
  • pages: recouple button theme to colorScheme and fix appearance for some logos in dark mode (#​12537) (b0f1538)
  • ts: make User interface overridable using module augmentation (#​12472) (7772375)
  • "state is not specified" error when using LINE provider (#​12703)
  • add a missed instance of allowInsecureRequests (#​12276)
  • More descriptive error in case that discovery endpoint returns an invalid issuer (#​12611)
  • improve client-side submodules (#​12249)

Other

v0.37.4

Compare Source

Bugfixes

  • core: vendor cookie until it has an ESM build (#​12248) (a150f1e)
  • core: filter unnecessary param before passing to session callback (c650d0c)

Other

  • fix import
  • Revert "fix(core): filter unnecessary param before passing to session callback"

v0.37.3

Compare Source

Bugfixes

  • core: carry-over request params for custom verifyRequest page (#​12166) (d6d8d4f)
  • core: use correct import for the cookie package (#​12177) (39250e3)
  • providers: update TikTok provider configuration with custom Fetch (#​12168) (2e78fa2)
  • providers: Ease authorization and scope override for Discord provider (#​12173) (39b7d9a)
  • providers: dropbox authorization params should contain token_access_type (#​12161) (8034cfe)

Other

  • deps: bump dependencies (b3e4369)
  • docs: enhance api reference with styles for providers (#​11961) (a88c7a3)
  • fix lint
  • fix(ts) mark account as optional in callbacks (#​12017)

v0.37.2

Compare Source

Bugfixes

v0.37.1

Compare Source

Bugfixes

  • providers: conform Entra ID when responding with the wrong issuer (#​11980) (e981e4d)

v0.37.0

Compare Source

Features

v0.36.0

Compare Source

Features
Bugfixes
  • correctly set isNewUser during account linking & user creation
Other

v0.35.3

Compare Source

Bugfixes

v0.35.2

Compare Source

Bugfixes

  • providers: make identifier param optional (3e8a648)
  • providers: optionally check identifier (54ba689)

v0.35.1

Compare Source

Bugfixes

v0.35.0

Compare Source

Features

Bugfixes

Other

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

v7.10.0

Compare Source

Prisma ORM 7.10.0

Prisma ORM 7.10.0 introduces a compatibility package for running Prisma 7 alongside newer Prisma versions, secures Prisma Studio's local server, and includes fixes across Prisma Client and the PostgreSQL, MariaDB, Neon, SQLite, and Prisma Postgres Serverless adapters.

Highlights

Run Prisma 7 alongside Prisma 8

This release introduces @prisma/prisma7, a compatibility package that lets you retain a matching Prisma 7 CLI and configuration while installing Prisma 8 in the same project.

Once 7.10.0 is released, a side-by-side installation can use:

npm install --save-dev prisma@8 @prisma/prisma7@7.10.0
npm install @prisma/client@7.10.0

Use prisma for the directly installed Prisma 8 CLI and prisma7 for Prisma 7:

npx prisma --version
npx prisma7 --version

npx prisma7 generate
npx prisma7 migrate dev
npx prisma7 db push

Prisma 7 now prefers version-specific configuration files, allowing its configuration to coexist with Prisma 8's prisma.config.* files:

// prisma7.config.ts
import { defineConfig } from '@prisma/prisma7/config'

export default defineConfig({
  schema: 'prisma/schema.prisma',
  migrations: {
    path: 'prisma/migrations',
  },
})

Without an explicit --config option, Prisma 7 searches for:

  1. Root-level prisma7.config.* files.
  2. .config/prisma7.* files.
  3. Existing prisma.config.* files as a backwards-compatible fallback.

The supported extensions are .js, .ts, .mjs, .cjs, .mts, and .cts. An explicit config path always takes precedence:

npx prisma7 generate --config ./custom/prisma7.config.ts

New projects initialized by the Prisma 7 CLI use prisma7.config.ts. Existing projects containing only prisma.config.* continue to work without migration or additional warnings. If a prisma7.config.* file exists but cannot be loaded, Prisma reports the error rather than silently falling back to another configuration.

The prisma7 identity is carried through CLI help, version output, shell completion, initialization, migration, database, and generation guidance. Stable Prisma concepts such as schema.prisma, Prisma Migrate, @prisma/client, and PRISMA_* environment variables remain unchanged.

Together, the separate executable and configuration namespace make it possible to operate Prisma 7 and Prisma 8 side by side without command or config-file collisions.

#​29949, #​29969, #​29994, #​30000, #​30002, #​30020

Prisma Studio security hardening

Prisma Studio's local HTTP server now:

  • Binds explicitly to 127.0.0.1 instead of all network interfaces.
  • Rejects browser requests from origins other than the active localhost or 127.0.0.1 Studio URL.
  • No longer returns wildcard CORS headers.
  • Applies the same protections across Node.js, Bun, and Deno.

This prevents network clients or malicious websites from accessing Studio's database endpoints while Studio is running.

#​29890

Prisma Client

  • Fixed P2002 errors from nested writes so meta.modelName identifies the model where the unique constraint violation occurred, including models using @@map and @@schema. #​29628
  • Fixed automatically batched findUniqueOrThrow() calls so every missing record rejects with P2025; later misses no longer resolve to undefined. #​29654
  • Parameter-chunked statements are now executed atomically in a transaction and rolled back if a later chunk fails. #​29771
  • Improved interactive transaction cleanup during $disconnect(), including transactions whose driver-level startup is still in progress. #​28768
  • Prevented transaction cleanup failures after a timeout or backend termination from becoming unhandled promise rejections. #​29611
  • Fixed fluent relation queries when relation fields are literally named select or include. #​29683
  • Fixed handling of Date and Uint8Array values created in other JavaScript realms, such as iframes, jsdom, and Node.js vm contexts. #​29177
  • Invalid Date values passed to $queryRaw or $executeRaw now throw PrismaClientValidationError instead of a generic error. #​29718
  • Fixed moduleFormat inference for the prisma-client generator in TypeScript projects using module: "node16" or "nodenext". Generated output now follows the nearest package.json type, defaulting to CommonJS when absent. #​29712
  • Deserialized Bytes values now own standalone ArrayBuffers rather than exposing unrelated contents from Node.js's shared Buffer pool. This applies to both regular and raw query results. #​29701
  • Fixed an incorrect logging context in the remote executor, including Accelerate-backed query execution. #​28892

Client extensions and observability

  • Result-extension compute callbacks now receive the current model name as a typed second argument:

    compute(data, modelName) {
  // ...
}

    The model name is also preserved when multiple extensions compose the same computed field. #​29782

  • Improved OpenTelemetry context for remotely executed queries:

    • $on('query') callbacks run within the matching db_query span.
    • Events from one operation share the same trace.
    • Error events are recorded as span exceptions.
    • Log events continue to be emitted when tracing is disabled or their reported span is unavailable.

    #​28892

Driver adapters

MariaDB
  • @prisma/adapter-mariadb now accepts an existing mariadb pool. External pools remain caller-owned unless disposeExternalPool: true is supplied. #​27992
  • Fixed pooled connection leaks during commit, rollback, and failed transaction startup. Connections are now returned with release() and transaction-specific listeners are removed before reuse. #​29612
  • Added support for bracketed IPv6 addresses in both mysql:// and mariadb:// connection strings. #​29026
  • Prevented malformed connection strings from exposing embedded passwords in retained debug output and diagnostic reports. #​27992
PostgreSQL, Neon, and Prisma Postgres Serverless
  • PostgreSQL deadlocks using SQLSTATE 40P01 are now reported as P2034 transaction write conflicts. #​29717
  • PostgreSQL RESTRICT violations using SQLSTATE 23001 are now reported as P2003, preserving an available field or constraint name. #​29554
  • @prisma/adapter-pg now preserves database constraint names when reporting unique constraint violations through P2002. #​29587
  • Prisma Postgres Serverless now prefers the named constraint for P2002, falling back to parsed field names when no constraint name is available. #​29801
  • Fixed Neon HTTP adapter serialization for typed parameters such as Bytes and DateTime. #​29747
SQLite
  • @prisma/adapter-better-sqlite3 now converts previously unhandled SQLite result codes into typed database errors instead of exposing raw driver errors.
  • The complete SQLITE_BUSY family is now mapped to socket timeout errors, with numeric extended result codes preserved where available.

#​29794

CLI and Migrate

  • prisma generate can now offer to install Prisma's agent skills. The opt-in prompt:

    • Is shown at most once per machine.
    • Is skipped in CI, containers, Git hooks, npm lifecycle scripts, and watch mode.
    • Is skipped when --no-hints is used or Prisma skills are already installed.
    • Times out after 30 seconds.
    • Never causes generation to fail if installation is unsuccessful.

    #​29690

  • A globally installed CLI now warns during prisma generate when its version differs from the project's local prisma or @prisma/client, and recommends running the local CLI. The check is best-effort and does not fail generation. #​29593

  • prisma version and prisma version --json now include the resolved Prisma CLI package path, making global-versus-local installation issues easier to diagnose. #​29573

  • Empty or generator-only schema files now report Schema must contain a datasource block from db pull, db push, and migrate dev, rather than reaching the schema engine and potentially producing inconsistent errors. #​29657

  • CLI commands now tolerate corrupt, unreadable, or unwritable command-state files. Invalid state is reinitialized, writes are atomic, and persistence failures fall back to in-memory state. #​29609

  • Studio now recognizes semicolon-delimited sqlserver:// connection strings before reporting the existing explicit message that SQL Server is not supported by Studio. #​29623

  • The AI-agent safety checkpoint now also covers interactive prisma db push confirmations involving data-loss warnings, rather than only invocations using --accept-data-loss. #​29793

Performance and reliability

  • Optimized query-plan execution by eagerly evaluating plans with one unconditional database operation and synchronously interpreting the remaining pure plan. Cached plans remain immutable. #​29004
  • Prevented call-stack overflows when rendering very large parameter lists or combining chunked results containing hundreds of thousands of rows. #​29751
  • Reduced ordinary query setup overhead by constructing fluent-relation field maps lazily and in linear time. Non-fluent queries no longer build this map. #​29752

Dependencies

  • Updated the transitive fast-uri dependency to a patched release addressing production audit advisories affecting versions through 3.1.3. #​29758

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

prisma init scaffolds a project and installs the Prisma agent skills catalog

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

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

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Europe/Berlin)

  • Branch creation
    • Between 06:00 PM and 09:59 PM, only on Friday (* 18-21 * * 5)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 renovate Bot added the deps label May 29, 2026
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch from 87514e2 to 3007811 Compare June 1, 2026 18:35
@renovate renovate Bot changed the title chore(deps): update dependency eslint-plugin-prettier to v5.5.6 fix(deps): update all non-major npm dependencies Jun 1, 2026
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 4 times, most recently from 5af791f to 133f719 Compare June 8, 2026 23:12
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 4 times, most recently from 51998a2 to b35aa85 Compare June 16, 2026 02:39
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 3 times, most recently from 391ea4c to 8082856 Compare June 22, 2026 22:01
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 7 times, most recently from 02a8080 to 8c1dc16 Compare July 1, 2026 23:46
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 5 times, most recently from 8894cd7 to 81c2789 Compare July 13, 2026 18:40
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch from 81c2789 to 64d9fff Compare July 20, 2026 22:06
@renovate

renovate Bot commented Jul 20, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ 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: dashboard/package-lock.json
npm warn Unknown env config "store". This will error in a future 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.24.15
npm error Found: @auth/core@0.41.3
npm error node_modules/@auth/core
npm error   @auth/core@"0.41.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @auth/core@"0.34.3" from next-auth@4.24.15
npm error node_modules/next-auth
npm error   next-auth@"4.24.15" from the root project
npm error
npm error Conflicting peer dependency: @auth/core@0.34.3
npm error node_modules/@auth/core
npm error   peerOptional @auth/core@"0.34.3" from next-auth@4.24.15
npm error   node_modules/next-auth
npm error     next-auth@"4.24.15" from the root project
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-10-07T01_02_53_257Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-07T01_02_53_257Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 2 times, most recently from d3abf4a to e86b7fb Compare July 21, 2026 11:43
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 4 times, most recently from 8241d1a to f932f65 Compare August 10, 2026 19:13
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 3 times, most recently from ab41e30 to 7b297a8 Compare August 17, 2026 22:58
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 3 times, most recently from f3f1657 to ecc7244 Compare August 25, 2026 17:11
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 3 times, most recently from 0702dcc to 10791bf Compare September 3, 2026 11:33
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 3 times, most recently from 29644e0 to 9ca724b Compare September 11, 2026 21:39
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 5 times, most recently from 0e05e07 to 2f42176 Compare September 21, 2026 22:04
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 4 times, most recently from 063bac2 to ab53ba9 Compare September 29, 2026 12:08
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch 3 times, most recently from b65f508 to 4a1cb67 Compare October 5, 2026 21:17
@renovate
renovate Bot force-pushed the renovate/all-non-major-npm-dependencies branch from 4a1cb67 to 949bf22 Compare October 7, 2026 01:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

deps

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants