Skip to content

chore(deps): Update all non-major dependencies - #92

Merged
chertik77 merged 1 commit into
mainfrom
renovate/all-minor-patch
Nov 16, 2026
Merged

chertik77 merged 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@better-auth/passkey (source) ^1.7.18 → ^1.7.22 age confidence
@better-auth/redis-storage (source) ^1.7.18 → ^1.7.22 age confidence
@hono/node-server ^2.1.6 → ^2.1.8 age confidence
better-auth (source) ^1.7.18 → ^1.7.22 age confidence
hono (source) ^4.13.17 → ^4.13.18 age confidence
prettier (source) ^3.9.10 → ^3.10.1 age confidence
resend ^6.37.0 → ^6.38.0 age confidence
typescript-eslint (source) ^8.72.1 → ^8.72.2 age confidence

Release Notes

better-auth/better-auth (@​better-auth/passkey)

v1.7.22

Compare Source

v1.7.21

Compare Source

Patch Changes
  • #​12388 070d101 Thanks @​gustavovalverde! - If a wildcard in baseURL.allowedHosts covers your passkey rpID, such as rpID: "example.com" with allowedHosts: ["*.example.com"], your server now starts without a passkey origin. Since 1.7.16 it threw at startup unless origin was set, and passkeys then worked only on the origins listed there, so tenants added at runtime needed a redeploy.

    In that setup, without origin, a passkey is accepted only from an exact allowedHosts entry, the fallback origin, or an origin listed exactly in trustedOrigins. The host the request names and wildcard entries do not count. To allow tenants added at runtime, return their origins from a trustedOrigins function that checks your tenant records. If you set origin, or no wildcard covers your rpID, nothing changes.

v1.7.20

Compare Source

v1.7.19

Compare Source

better-auth/better-auth (@​better-auth/redis-storage)

v1.7.22

Compare Source

v1.7.21

Compare Source

v1.7.20

Compare Source

v1.7.19

Compare Source

honojs/node-server (@​hono/node-server)

v2.1.8

Compare Source

What's Changed

  • fix(request): forward duplex to the native request in #​409
  • fix(utils): do not chain a promise per chunk while streaming a response in #​417
  • fix(listener): cancel the response body when the client has already disconnected in #​412
  • fix(utils): cancel late HTTP/2 response bodies in #​419
  • fix(listener): do not send a complete response when the body fails during the early read in #​420

Full Changelog: honojs/node-server@v2.1.7...v2.1.8

v2.1.7

Compare Source

Security fixes

This release includes a fix for the following security issue:

serveStatic with allowPercentInPath still allows the double-decode middleware bypass

Affects: serveStatic with allowPercentInPath: true. The fix for GHSA-rmxm-3fg6-px4f rejects a path containing %, but the allowPercentInPath option skipped that check entirely. A malformed percent sequence such as /static/%%36%31dmin/secret.txt was routed as /static/%61dmin/secret.txt, so middleware on /static/admin/* did not run, and serveStatic then decoded %61 to a and served static/admin/secret.txt. The default configuration was already fixed in 2.1.3. GHSA-fj57-4f93-cfw6

serveStatic now accepts the second decode only when its result equals the routed path with %25 replaced by %. File names containing a literal %, requested as %25, are served as before.


The same fix ships in hono v4.13.18 (GHSA-74fm-fwc7-3fwp).

Full Changelog: honojs/node-server@v2.1.6...v2.1.7

better-auth/better-auth (better-auth)

v1.7.22

Compare Source

Patch Changes

v1.7.21

Compare Source

Patch Changes
  • #​12126 4739122 Thanks @​hardikguptaofficialgit! - On Prisma with MongoDB, when your id columns use @db.ObjectId, magic link and email OTP sign-in for users with an unverified email no longer fail with a 500 (Malformed ObjectID). SAML sign-in, DPoP-bound OAuth requests, and private_key_jwt client authentication are fixed the same way, and Sign-In with Ethereum now keeps the email the user supplied instead of a placeholder. Setups with plain String id columns and other databases are unaffected.

  • #​12392 a277020 Thanks @​gustavovalverde! - Fixed the device approval page showing a valid code as invalid when the same signed-in user looked it up twice at once, such as under React Strict Mode in development.

  • #​12052 1c3410a Thanks @​lakshya-dhariwal! - If you set advanced.backgroundTasks.handler and your database adapter runs transactions (the built-in Kysely connection, MongoDB with client, or Prisma or Drizzle with transaction: true), email sign-up now keeps the database writes made while sending the verification email or running onExistingUserSignUp. Before, those writes failed because the sign-up had already been saved. With emailOTP({ overrideDefaultEmailVerification: true }), the code was never stored, so new users could not verify their email.

    Whatever adapter or background handler you use, a sign-up verification email now goes out after the new user is saved, and onExistingUserSignUp, when a duplicate sign-up triggers it, runs after the request's database work completes. If sendVerificationEmail throws, the sign-up succeeds and the error is logged; before, the sign-up failed. To reject a sign-up, use a databaseHooks.user.create.before hook. If onExistingUserSignUp throws, the error is logged and the request still returns the generic response.

  • #​12179 9105261 Thanks @​ghazy2001! - Generic OAuth providers configured with discoveryHeaders now send those headers when fetching the provider's signing keys from a jwks_uri on the same origin as discoveryUrl. Before, the keys request went out without them. Providers whose key endpoint requires the headers rejected it, so every ID token failed verification and sign-in failed. A jwks_uri on another origin still gets no headers.

    With discoveryHeaders set, the discovery request now follows redirects only within the origin of discoveryUrl, so the headers no longer reach another host. If your discoveryUrl redirects to another origin, discovery now fails and Better Auth logs an error. Set discoveryUrl to the final URL. Providers without discoveryHeaders are unaffected.

  • #​12401 c3a94c5 Thanks @​gustavovalverde! - Generic OAuth providers configured with authorizationHeaders now send those headers when refreshing an access token, not only when exchanging the authorization code. Before, a provider whose token endpoint requires one of those headers accepted the sign-in but rejected every refresh. Providers without authorizationHeaders are unaffected.

    refreshAccessToken and refreshAccessTokenRequest from @better-auth/core/oauth2 accept an optional headers input for providers that need extra headers on refresh. Client authentication headers still take precedence over it.

    Extra headers whose names differ only in case from a client authentication header, such as Authorization with authentication: "basic", no longer produce a combined, invalid header on the code exchange or refresh. Client authentication replaces them, including headers a custom tokenEndpointAuth hook sets in any casing.

  • #​12404 9b40ac6 Thanks @​bytaesu! - Plugin packages no longer import from the better-auth root, so bundlers that split code stop emitting unused Kysely chunks when used with better-auth/minimal.

  • #​12395 b0ced9d Thanks @​gustavovalverde! - On Cloudflare Workers, sign-ins with a genericOAuth provider that uses discoveryUrl, and OAuth provider requests that use a configured resource (resources), no longer hang. An auth instance created at module scope retries discovery and resource seeding on later requests. Previously, if the request running that retry ended first, every later request that needed it waited forever. Each request now retries on its own until one succeeds.

    On other runtimes, concurrent requests may send a few more discovery requests or resource lookups while the identity provider or database is unreachable.

  • #​11912 5c12074 Thanks @​gustavovalverde! - If you use PostgreSQL and other schemas in the same database are dropped while Better Auth reads the database, for example one schema per tenant or parallel test runs, the startup schema check and npx auth@latest migrate no longer fail intermittently with schema "…" does not exist or relation "…" does not exist. The startup schema check now reads only the schemas on the connection's search_path, plus any schema set with schemaName or a schema plugin, and migrate reads only the schema it migrates. Before, both read every schema in the database. If no other schemas change while Better Auth reads the database, nothing changes for you.

  • #​12403 e64f624 Thanks @​bytaesu! - SIWE verification no longer includes the internal error message (for example a database error) in its 401 response. The original error is now logged on the server instead.

  • Updated dependencies [4739122, c3a94c5, 4080630, 5c12074, b241ffc, 57fa843, 1a79da5, 2d10ae7, ef4d4f7]:

v1.7.20

Compare Source

Patch Changes

v1.7.19

Compare Source

Patch Changes
  • #​12323 a10121d Thanks @​bytaesu! - Fixed the active-sessions list in secondary storage being stored without an expiry when the last remaining session had less than a second left.

  • #​12335 c41f8ff Thanks @​bytaesu! - Fixed /admin/create-user leaving a user without a credential account when the password was rejected (for example by the Have I Been Pwned plugin), which made retrying with the same email fail with USER_ALREADY_EXISTS_USE_ANOTHER_EMAIL.

  • #​12338 e786566 Thanks @​bytaesu! - Fixed /admin/create-user leaving a user without a credential account when creating that account failed, which made retrying with the same email fail with USER_ALREADY_EXISTS_USE_ANOTHER_EMAIL.

  • #​12336 ac778b7 Thanks @​bytaesu! - Client actions now send the HTTP method passed in the second-argument fetch options, the same as when it is nested under fetchOptions. Passing a lowercase get or HEAD method no longer fails because a request body was attached.

  • #​12246 5eb69d8 Thanks @​AryaKesharwani! - /device/token now returns invalid_client instead of invalid_grant when validateClient rejects the client_id, matching /device/code and RFC 6749 section 5.2.

  • #​12319 4b0327b Thanks @​bytaesu! - Plugin schema overrides (modelName and field names) no longer leak into other instances of the same plugin in one process.

  • #​12320 2d5ef64 Thanks @​bytaesu! - Fix OAuth sign-in failing with state_mismatch during the daylight saving time fall-back hour on servers that do not run in UTC. The stored OAuth state is no longer created already expired.

  • #​12337 5f0a0fc Thanks @​bytaesu! - The OpenAPI schema now documents query parameters for endpoints whose query schema is wrapped in z.optional(), such as /get-session and Stripe's /subscription/list.

  • #​12332 89e74b8 Thanks @​bytaesu! - Fixed organization.getInvitation returning a missing, expired, or non-pending invitation error without a code. It now returns INVITATION_NOT_FOUND like the other invitation endpoints.

  • #​12318 525bd7a Thanks @​bytaesu! - Fix listMembers failing with a syntax error on PostgreSQL and MSSQL when the filter or offset matches no members.

  • #​12366 23a60a3 Thanks @​bytaesu! - Fixed SIWE sign-in leaving a user behind when creating its wallet address or account failed, which blocked that wallet from signing in again.

  • #​12340 29e45f8 Thanks @​bytaesu! - Fixed social sign-up hanging on single-connection databases when the username plugin is enabled and the provider profile maps a username.

  • Updated dependencies [8412a5f, 34ee100]:

honojs/hono (hono)

v4.13.18

Compare Source

Security fixes

This release includes fixes for the following security issues:

validator() skips validation for requests whose Content-Type parameters are formatted differently

Affects: validator('json') and validator('form') in hono/validator. A Content-Type with whitespace before ;, a trailing ;, or an unusual parameter name was not recognized, so the validator saw an empty object while the handler could read all fields. This completes the fix for GHSA-4h7h-rv7c-7m2v. The validator now decides by the media type alone, as c.req.parseBody() does. GHSA-92p4-j3wq-jmqx

bodyLimit() keeps every transfer chunk of a request body in memory

Affects: bodyLimit() in hono/body-limit. A body sent in very small transfer chunks was retained as one object per chunk, so a request within the configured limit could exhaust memory. The body is now buffered in one array bounded by maxSize. GHSA-39q9-qp46-w8xg

mount() and app.mount() forward a wrong path when a custom getPath adds a prefix

Affects: mount() in hono/mount and app.mount() on 4.13.16 and 4.13.17. With a getPath that prepends a prefix such as the host name, one segment too many was removed from the forwarded path, so middleware scoped inside the mount prefix could be skipped. The prefix is removed from the routed path again. Paths that would change meaning when forwarded now get 400, and an optional regular expression parameter in a mount path throws. GHSA-h25j-2p75-qj33

serveStatic() serves a path that was decoded twice when allowPercentInPath is enabled

Affects: serveStatic() in hono/serve-static and the runtime adapters, only with allowPercentInPath: true. A malformed percent escape in the request path was decoded a second time, so a path that middleware registered on the encoded form did not see could still reach a static file. The file path must now be the same as the routed path, and otherwise the response is 404. GHSA-74fm-fwc7-3fwp


Users who rely on validator(), bodyLimit(), mount() with a custom getPath, or serveStatic() with allowPercentInPath are strongly encouraged to upgrade to this version.

Full Changelog: honojs/hono@v4.13.17...v4.13.18

prettier/prettier (prettier)

v3.10.1

Compare Source

diff

GraphQL: Fix empty selection set with comments (#​20504 by @​fisker)
# Input
fragment F on Query {
  # x
}

# Prettier 3.10.0
Error: Comment "x" was not printed. Please report this error!

# Prettier 3.10.1
fragment F on Query {
  # x
}

v3.10.0

Compare Source

diff

🔗 Release Notes

resend/resend-node (resend)

v6.38.0

Compare Source

What's Changed

Full Changelog: resend/resend-node@v6.37.0...v6.38.0

typescript-eslint/typescript-eslint (typescript-eslint)

v8.72.2

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.


Configuration

📅 Schedule: (in timezone Europe/London)

  • Branch creation
    • "before 6am on monday"
  • 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 dependencies Pull requests that update a dependency file label Nov 16, 2026
@chertik77
chertik77 merged commit e7b6c67 into main Nov 16, 2026
2 checks passed
@chertik77
chertik77 deleted the renovate/all-minor-patch branch November 16, 2026 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant