Skip to content

chore(deps): bump the npm-deps group across 1 directory with 12 updates - #102

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-deps-01608cf1db
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-deps-01608cf1db

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the npm-deps group with 12 updates in the / directory:

Package From To
@better-auth/oauth-provider 1.7.7 1.7.22
@hono/node-server 2.1.4 2.1.7
better-auth 1.7.7 1.7.22
hono 4.13.13 4.13.18
@commitlint/cli 21.2.3 21.2.4
@commitlint/config-conventional 21.2.3 21.2.4
@playwright/test 1.64.0 1.65.0
eslint 10.12.0 10.14.0
fallow 3.32.0 3.42.0
globals 17.13.0 17.14.0
prettier 3.9.9 3.10.1
tap 21.8.0 21.8.1

Updates @better-auth/oauth-provider from 1.7.7 to 1.7.22

Release notes

Sourced from @​better-auth/oauth-provider's releases.

v1.7.22

better-auth

Bug Fixes

  • Fixed verification value consumption hanging on Cloudflare Workers when an earlier request for the same identifier ended mid-query (#12451)
  • Fixed module-scope auth instances on Cloudflare Workers logging a schema validation error on every cold start by validating on first use (#12448)
  • Fixed deferSessionRefresh refresh requests failing with a 415 error in Next.js and Nuxt (#12330)
  • Fixed ReferenceError: window is not defined when a client session subscription is cleaned up after a test environment tears down its globals (#12324)
  • Fixed client session refresh listeners piling up on the server during SSR (#12324)
  • Fixed session polling never firing when the runtime's navigator does not report connectivity (#12462)
  • Fixed OAuth sign-up rejected by a user.create.before hook returning false logging a TypeError (#12331)
  • Fixed deleteOrganization clearing the session's active organization when a beforeDeleteOrganization hook rejected the delete (#12334)
  • Fixed revokeSession, revokeSessions, and deleteUser({ token }) to expire session cookies when revoking the current session or deleting the user (#12321)
  • Fixed getSession to no longer leave an expired session in the request context after returning null (#12459)

For detailed changes, see CHANGELOG

@better-auth/core

Bug Fixes

  • Fixed introspected access tokens that fail aud, iss, exp, or nbf claim checks to return a 401 instead of a 500 (#12432)
  • Fixed getSession failing with "Failed to get session" when a user.additionalFields entry references a table outside the Better Auth schema (#12333)
  • Fixed resource-server challenges turning rejected requests into 500 errors, and added invalid_token error details when a presented token fails verification (#12445)

For detailed changes, see CHANGELOG

@better-auth/oauth-provider

Bug Fixes

  • Fixed failed requests using the DPoP authorization scheme to receive a DPoP challenge instead of a Bearer challenge (#12447)
  • Fixed resource-server challenges turning rejected requests into 500 errors, and added invalid_token error details when a presented token fails verification (#12445)
  • Fixed /oauth2/userinfo to send a WWW-Authenticate challenge on every 401 response, including DPoP failures and requests with no token (#12446)

For detailed changes, see CHANGELOG

@better-auth/drizzle-adapter

Bug Fixes

  • Fixed getSession failing with "Failed to get session" when a user.additionalFields entry references a table outside the Better Auth schema (#12333)

For detailed changes, see CHANGELOG

@better-auth/mcp

Bug Fixes

... (truncated)

Changelog

Sourced from @​better-auth/oauth-provider's changelog.

1.7.22

Patch Changes

  • #12447 5976842 Thanks @​gustavovalverde! - Answer a failed request that used the DPoP authorization scheme with a DPoP challenge. Before, an expired, revoked, or otherwise invalid DPoP-bound token got a Bearer challenge, which a client that supports only DPoP might not act on. createResourceServerChallenge accepts a new request option, either the failed Request or { authorizationHeader }, and reads the scheme from it. The resource client's verifyAccessTokenRequest, requireMcpAuth, and createMcpProtectedRequestHandler pass it automatically.

  • #12445 e9d8e59 Thanks @​gustavovalverde! - Resource-server challenges no longer turn a rejected request into a 500, and they now tell clients when the token they sent is invalid.

    createResourceServerChallenge used to throw when an error_description contained a character that RFC 6750 does not allow in that parameter. Better Auth's own DPoP message DPoP proof typ must be "dpop+jwt" was one of them. The description is now fitted into the allowed characters: " becomes ', other disallowed characters become spaces, and an empty result is left out. Invalid scope tokens in challengeScopes still throw.

    When the request presented a token that failed verification, the 401 Bearer challenge now carries error="invalid_token" and an error_description, following RFC 6750 §3 and §3.1. A request without a token still gets no error code. verifyBearerToken and verifyAccessTokenRequest now set error: "invalid_token" and error_description on their expired, invalid, inactive, and unreadable token errors, and the challenge's response body includes both fields alongside message.

  • #12446 1393028 Thanks @​gustavovalverde! - Send a WWW-Authenticate challenge on every 401 from /oauth2/userinfo. Previously, a DPoP-bound token with a missing or invalid proof, a mismatched htu or htm, or the wrong authorization scheme got a 401 with no challenge, and so did a request with no access token. A client could not tell from the response which scheme or proof algorithms to retry with.

    DPoP-bound tokens and requests that use the DPoP scheme now get a DPoP challenge with algs (RFC 9449 §7.1). Other failures keep the Bearer challenge, and a request with no token is offered both schemes. The challenge is also listed in Access-Control-Expose-Headers, so browser clients on other origins can read it. Response bodies are unchanged.

1.7.21

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.

  • #12385 fd66861 Thanks @​gustavovalverde! - Denying consent now redirects to the client only while the client is enabled and its redirect_uri is still valid. Before, a denial within the signed request lifetime still redirected to the redirect_uri after the client was disabled, the URI was removed from its registration, or allowInsecureRedirectUri or validateRedirectUri stopped accepting it. The user now sees the server error page instead.

  • #12389 db930d9 Thanks @​gustavovalverde! - On databases that do not enforce foreign keys, such as the memory adapter and MongoDB, an opaque access token could stay valid after refresh token reuse or a replayed authorization code revoked its grant, if the token request was still issuing a refresh token. That request now fails with invalid_grant, and refresh token reuse revokes every access token in the family, even past 100 refresh tokens. JWT access tokens and opaque access tokens issued without a refresh token stay valid until they expire.

  • #11911 900195d Thanks @​gustavovalverde! - When a client sent the same refresh token twice at nearly the same time, one of the requests could fail with a 500 error. This happened when the second request arrived after the first had already rotated the token. The second request counts as refresh token reuse and revokes the token family, including the tokens the first request was still issuing, so the first request then failed on the database insert. Both requests now return invalid_grant, and the client must sign in again, as after any detected reuse. The same applies when an authorization code is redeemed twice at once.

    Only opaque access tokens on databases that enforce foreign keys were affected. JWT access tokens, and duplicate refreshes inside refreshTokenReuseInterval, were not.

  • #12409 9362c0d Thanks @​bytaesu! - Refresh tokens are issued correctly when formatRefreshToken.encrypt is async. Before, the client received [object Promise] in place of the token.

  • #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.

  • #12391 79d61b0 Thanks @​gustavovalverde! - Client registration and client updates now return invalid_redirect_uri, not invalid_client_metadata, when a post_logout_redirect_uris entry uses http outside the allowed hosts or contains credentials, matching redirect_uris. Clients that match on the old error code need to check for the new one.

1.7.20

Patch Changes

  • #11904 a3f50d0 Thanks @​gustavovalverde! - OAuth provider deployments served over plain HTTP on a private network, such as a LAN address, a VPN, or a private DNS name, can now accept http redirect URIs through the new allowInsecureRedirectUri option. Return true from it for origins you control. The same option lets web clients use localhost callbacks during development. Without the option, redirect URI validation is unchanged.

    If your issuer (baseURL, or jwt.issuer when set) uses http on a non-loopback host, discovery and the iss authorization response parameter now report it as configured instead of rewriting it to https. They now match the issuer in issued tokens, so OpenID Connect sign-ins no longer fail on the mismatch. If a proxy terminates TLS in front of Better Auth, set baseURL to the public https URL.

    When an authorization request uses a registered http redirect URI that the HTTPS policy rejects, the error now appears on the server error page instead of being redirected to that URI.

    Client registration and updates now reject post-logout redirect URIs that contain credentials, such as https://user:pass@example.com/logged-out, matching the existing rule for redirect URIs.

... (truncated)

Commits
  • 116c868 chore: release v1.7.22 (#12435)
  • 5976842 fix(oauth-provider): answer failed DPoP requests with a DPoP challenge (#12447)
  • 1393028 fix(oauth-provider): send WWW-Authenticate challenges on UserInfo 401s (#12446)
  • e9d8e59 fix(oauth-provider): keep resource challenges valid and report invalid_token ...
  • b237924 chore: release v1.7.21 (#12384)
  • 4739122 fix(core): use ObjectId-shaped derived ids for Prisma ObjectId columns (#12126)
  • b0ced9d fix(generic-oauth, oauth-provider): stop sharing pending retries across reque...
  • 79d61b0 fix(oauth-provider): report rejected post-logout redirect URIs as invalid_red...
  • db930d9 fix(oauth-provider): revoke in-flight access tokens on adapters without forei...
  • 9362c0d fix: await promises that were dropped or concatenated as strings (#12409)
  • Additional commits viewable in compare view

Updates @hono/node-server from 2.1.4 to 2.1.7

Release notes

Sourced from @​hono/node-server's releases.

v2.1.7

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

v2.1.6

Security fixes

This release includes fixes for the following security issues:

Backslash in the request path is parsed as a path separator, bypassing path-based access control at a reverse proxy

Affects: all requests. The raw request-target was passed to the WHATWG URL parser, which treats a backslash in the path as / and resolves .. segments, so /admin\secret reached the application as /admin/secret. A reverse proxy that forwards the backslash unchanged applied its path-based rules to the original path. GHSA-jpvv-r467-5p4w

A request whose path contains a raw backslash is now rejected with 400 Bad Request, for HTTP/1.1, HTTP/2 and WebSocket upgrades. A percent-encoded backslash (%5C) and a backslash in the query string are still accepted.

WebSocket upgrade request-target starting with // replaces the host in c.req.url, bypassing Origin checks

Affects: upgradeWebSocket. The URL of an upgrade request was built by resolving the request-target against the Host header, so a request-target such as //attacker.example/ws set the host of c.req.url to a client-chosen value while routing still saw /ws. An application that compared Origin with the origin of c.req.url could be bypassed by a page on another site. GHSA-7v5p-43qr-wch5

The host of upgrade requests now comes from the Host header, as for ordinary requests.

Unhandled ECONNRESET on the socket during an asynchronous WebSocket upgrade crashes the process

Affects: upgradeWebSocket. While the application handled an upgrade request, the socket had no error listener. A client that reset the connection during asynchronous middleware caused an unhandled 'error' event and terminated the process. GHSA-qv5m-9pm6-hqp3

Error and close events on the socket are now handled while the application runs, and a pending upgrade is released when the socket closes.


The backslash fix also ships in @hono/node-server v1.19.18. Users of upgradeWebSocket are encouraged to upgrade to this version.

v2.1.5

What's Changed

New Contributors

... (truncated)

Commits
  • abe63c8 2.1.7
  • cc42986 Merge commit from fork
  • 123f782 2.1.6
  • cfaa79f Merge commit from fork
  • 61cc026 Merge commit from fork
  • a152a45 test: wait for the first chunk before sending the second in the readable-stre...
  • fb97395 Merge commit from fork
  • 4b47a0d 2.1.5
  • e77824a fix(serve-static): only serve GET and HEAD requests (#405)
  • 1b6e6bf fix(listener): abort the request signal when an HTTP/2 client resets the stre...
  • See full diff in compare view

Updates better-auth from 1.7.7 to 1.7.22

Release notes

Sourced from better-auth's releases.

v1.7.22

better-auth

Bug Fixes

  • Fixed verification value consumption hanging on Cloudflare Workers when an earlier request for the same identifier ended mid-query (#12451)
  • Fixed module-scope auth instances on Cloudflare Workers logging a schema validation error on every cold start by validating on first use (#12448)
  • Fixed deferSessionRefresh refresh requests failing with a 415 error in Next.js and Nuxt (#12330)
  • Fixed ReferenceError: window is not defined when a client session subscription is cleaned up after a test environment tears down its globals (#12324)
  • Fixed client session refresh listeners piling up on the server during SSR (#12324)
  • Fixed session polling never firing when the runtime's navigator does not report connectivity (#12462)
  • Fixed OAuth sign-up rejected by a user.create.before hook returning false logging a TypeError (#12331)
  • Fixed deleteOrganization clearing the session's active organization when a beforeDeleteOrganization hook rejected the delete (#12334)
  • Fixed revokeSession, revokeSessions, and deleteUser({ token }) to expire session cookies when revoking the current session or deleting the user (#12321)
  • Fixed getSession to no longer leave an expired session in the request context after returning null (#12459)

For detailed changes, see CHANGELOG

@better-auth/core

Bug Fixes

  • Fixed introspected access tokens that fail aud, iss, exp, or nbf claim checks to return a 401 instead of a 500 (#12432)
  • Fixed getSession failing with "Failed to get session" when a user.additionalFields entry references a table outside the Better Auth schema (#12333)
  • Fixed resource-server challenges turning rejected requests into 500 errors, and added invalid_token error details when a presented token fails verification (#12445)

For detailed changes, see CHANGELOG

@better-auth/oauth-provider

Bug Fixes

  • Fixed failed requests using the DPoP authorization scheme to receive a DPoP challenge instead of a Bearer challenge (#12447)
  • Fixed resource-server challenges turning rejected requests into 500 errors, and added invalid_token error details when a presented token fails verification (#12445)
  • Fixed /oauth2/userinfo to send a WWW-Authenticate challenge on every 401 response, including DPoP failures and requests with no token (#12446)

For detailed changes, see CHANGELOG

@better-auth/drizzle-adapter

Bug Fixes

  • Fixed getSession failing with "Failed to get session" when a user.additionalFields entry references a table outside the Better Auth schema (#12333)

For detailed changes, see CHANGELOG

@better-auth/mcp

Bug Fixes

... (truncated)

Changelog

Sourced from better-auth's changelog.

1.7.22

Patch Changes

  • #12324 80c407b Thanks @​bytaesu! - Fixed ReferenceError: window is not defined when a client session subscription is cleaned up after a test environment such as happy-dom tears down its globals.

  • #12462 d32a30a Thanks @​bytaesu! - Fixed session polling never firing when the runtime's navigator does not report connectivity.

  • #12324 80c407b Thanks @​bytaesu! - Fixed client session refresh listeners piling up on the server during SSR.

  • #12321 946177e Thanks @​bytaesu! - Revoking your current session with revokeSession or revokeSessions, and deleting your account with deleteUser({ token }), now expire the session cookies, so a cached session is no longer returned afterwards.

  • #12459 d210421 Thanks @​bytaesu! - getSession no longer leaves an expired session in the request context after returning null.

  • #12331 485567e Thanks @​bytaesu! - OAuth sign-up rejected by a user.create.before hook returning false no longer logs a TypeError. It still fails with unable_to_create_user.

  • #12334 ec3047d Thanks @​bytaesu! - Fixed deleteOrganization clearing the session's active organization when a beforeDeleteOrganization hook rejected the delete. The active organization is now cleared only after the organization is actually deleted.

  • #12330 d521343 Thanks @​bytaesu! - Fix deferSessionRefresh refresh requests failing with 415 in Next.js and Nuxt, where the bodyless POST /get-session reached the handler as an empty stream without a Content-Type.

  • #12451 71052af Thanks @​bytaesu! - On Cloudflare Workers, consuming a verification value no longer hangs when an earlier request for the same identifier ended mid-query. A superseded code can also no longer be consumed while a newer one is being verified on a database without transactions.

  • #12448 79219b4 Thanks @​bytaesu! - Schema validation now runs when the auth instance is first used instead of when it is created, so a module-scope instance on Cloudflare Workers no longer logs a validation error on every cold start. On every runtime, a mismatch is no longer logged at startup and is reported by the requests that fail.

  • Updated dependencies [6536174, 262adc0, e9d8e59, 79219b4]:

    • @​better-auth/core@​1.7.22
    • @​better-auth/drizzle-adapter@​1.7.22
    • @​better-auth/prisma-adapter@​1.7.22
    • @​better-auth/telemetry@​1.7.22
    • @​better-auth/kysely-adapter@​1.7.22
    • @​better-auth/memory-adapter@​1.7.22
    • @​better-auth/mongo-adapter@​1.7.22

1.7.21

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.

... (truncated)

Commits
  • 116c868 chore: release v1.7.22 (#12435)
  • ed1d47b chore(deps): update dependencies (#12472)
  • e4f9215 test(generic-oauth): serve provider discovery locally in helper tests (#12471)
  • d210421 fix(session): keep expired sessions out of the hook context on get-session (#...
  • d32a30a fix(client): treat unknown connectivity as online (#12462)
  • 4e26288 refactor: share the deletion step across deleteUser and its callback (#12457)
  • 6536174 fix(db): ignore references to app tables when resolving joins (#12333)
  • 946177e fix(session): expire session cookies when revoking the current session or del...
  • 80c407b fix(client): skip session refresh listeners during SSR and keep manager teard...
  • 71052af fix: keep verification consumes from hanging on Cloudflare Workers (#12451)
  • Additional commits viewable in compare view

Updates hono from 4.13.13 to 4.13.18

Release notes

Sourced from hono's releases.

v4.13.18

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

v4.13.17

What's Changed

  • fix(cookie): match the __Secure- and __Host- prefixes case-insensitively in honojs/hono#5608
  • fix(utils/url): do not match a query key across separators in honojs/hono#5607
  • fix(etag,pretty-json): cancel the discarded response body in honojs/hono#5606
  • fix(client): detect the JSON media type with whitespace before a parameter in honojs/hono#5609
  • fix(timing): honor a precision of 0 in setMetric in honojs/hono#5363
  • fix(utils/mime,ssg): match media types case-insensitively in honojs/hono#5449
  • fix(timing): escape double quotes and backslashes in Server-Timing descriptions in honojs/hono#5478
  • fix(etag): preserve commas within quoted entity tags in honojs/hono#5353
  • fix(accepts): preserve exact media type quality over subtype wildcards in honojs/hono#5427
  • fix(cookie): match the __Secure- and __Host- prefixes case-insensitively in CookieConstraint in honojs/hono#5611
  • fix(jsx): add the CSP nonce to all scripts generated by ErrorBoundary in honojs/hono#5430
  • fix(ssg): do not reuse created directories across toSSG runs in honojs/hono#5381
  • fix(aws-lambda): sanitize non-ASCII header values in API Gateway v2 events in honojs/hono#5483
  • fix(jsx): escape element and object attribute values in honojs/hono#5512
  • fix(jsx): do not render ref objects as attributes in honojs/hono#5615
  • fix(factory): keep independent return types for nine handlers in honojs/hono#5618

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

v4.13.16

... (truncated)

Commits

Updates @commitlint/cli from 21.2.3 to 21.2.4

Release notes

Sourced from @​commitlint/cli's releases.

v21.2.4

21.2.4 (2026-10-18)

Bug Fixes

Performance Improvements

Docs, etc

Full Changelog: conventional-changelog/commitlint@v21.2.3...v21.2.4

Changelog

Sourced from @​commitlint/cli's changelog.

21.2.4 (2026-10-18)

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

Commits

Updates @commitlint/config-conventional from 21.2.3 to 21.2.4

Release notes

Sourced from @​commitlint/config-conventional's releases.

v21.2.4

21.2.4 (2026-10-18)

Bug Fixes

Performance Improvements

Docs, etc

Full Changelog: conventional-changelog/commitlint@v21.2.3...v21.2.4

Changelog

Sourced from @​commitlint/config-conventional's changelog.

21.2.4 (2026-10-18)

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

Commits

Updates @playwright/test from 1.64.0 to 1.65.0

Release notes

Sourced from @​playwright/test's releases.

v1.65.0

🥟 Run tests with Bun

The test runner now runs under Bun. Bun transpiles your TypeScript test files itself, so Playwright does not use Babel or its compilation cache. Pass the --bun flag, because without it bunx playwright test runs on Node.js:

bunx --bun playwright test

Our CI runs the test runner tests under Bun 1.4.3 on Linux. Some features work differently under Bun:

  • There is no watch mode. UI mode does not run tests again when files change, and --only-changed does not follow imports.
  • Bun loads modules itself, so --tsconfig and the JSX options in tsconfig.json have no effect, and custom ESM loaders are not supported.
  • Stack traces do not include async frames, and API names do not include the class name: click instead of locator.click. This changes some step locations, step titles and error messages.
  • Console output of a test does not get into the trace and UI mode.

🚨 Reports with only failures

New failures reporter prints failures and successful retries as they occur, followed by a summary, without progress output.

New onlyFailures option of the HTML, JSON and JUnit reporters keeps only tests with unexpected outcomes, flaky tests and interrupted tests:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
reporter: [
['failures'],
['html', { onlyFailures: true }],
],
});

🎯 Test runner

  • New built-in -exclusive- test lock runs a test only when no other tests are running. All other tests continue to run in parallel with each other:

    test('restart the server', { lock: '-exclusive-' }, async () => {
      // No other test runs while this one is running.
    });
  • test.skip(), test.fixme(), test.fail() and test.slow() now accept only a description. It is recorded in the test annotation:

    test('upload a file', async ({ page }) => {
      test.skip('Not implemented yet');
    });

... (truncated)

Commits
  • a1f35e1 chore: mark v1.65.0 (#43925)
  • a99c1ab cherry-pick(#43918): Revert "fix(docker): use latest stable Chrome for Testin...
  • 6f9a7f5 cherry-pick(#43914): docs(release-notes): update Chromium version for 1.65...

    Description has been truncated

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 11, 2026
@mroderick

mroderick commented Nov 11, 2026 •

Copy link
Copy Markdown
Collaborator

Dependency Upgrade Review

Verdict: Compatible (head 15b3e90f504366446164cf62dbb1cca771c22942) · Confidence: High

Dependabot group bump of 12 packages (runtime deps patch-level: better-auth and @better-auth/oauth-provider 1.7.7→1.7.22, hono 4.13.13→4.13.18, @hono/node-server 2.1.4→2.1.7; dev deps include minor bumps to @playwright/test and prettier), plus a merged CI-only zizmor action bump. All peer ranges resolve cleanly in the lockfile, both suites and the planner round-trip probe pass, so this is safe to merge.

Checks

Check Result
planner suite pass
auth suite pass
round-trip probe pass

Contracts

Contract Status Basis
Planner OAuth round-trip (PKCE authorize → token → session) Verified Round-trip probe passed against the upgraded @better-auth/oauth-provider and better-auth.
JWT issued to audience 'planner' with github_id claim Verified auth-suite integration/jwt-payload.test.js plus probe pass.
Peer ranges satisfied (pg ^8.0.0; better-auth/@better-auth/core ^1.7.22; better-call 1.4.5; @better-fetch/fetch 1.3.3) Verified Lockfile inspection: all peers resolve to declared versions at the head.
better-auth db migration API (getMigrations → runMigrations) Verified Both scripts/migrate.js and test-instance.js run migrations on Postgres; auth-suite passed.
Magic-link flow (dev capture + SendGrid payload) Verified auth-suite features/magic-links.test.js and unit/magic-link-email.test.js pass.
Compatibility analysis — 13 packages
  • @better-auth/oauth-provider 1.7.7 → 1.7.22: Patch-band bump; its peers (better-auth and @better-auth/core ^1.7.22, @better-fetch/fetch 1.3.3, better-call 1.4.5) all resolve in the lockfile. oauthProvider plugin config (scopes, validAudiences, customIdTokenClaims) is unchanged in source.
  • better-auth ^1.7.5 → 1.7.22: Patch-band bump under the existing caret; peer pg ^8.0.0 satisfied by pg 8.23.1. getMigrations/runMigrations still resolves — scripts/migrate.js and test/helpers/test-instance.js both exercise it. Transitive @better-auth/utils 0.4.2→0.5.1 and better-call 1.4.0→1.4.5 stay within declared ranges.
  • hono ^4.13.13 → ^4.13.18: Patch bump under existing caret; satisfies hono-pino's >=4.0.0 peer. Rendering and imports (hono, hono/html) unchanged in source.
  • @hono/node-server ^2.1.4 → ^2.1.7: Patch bump under existing caret; peer hono ^4 satisfied. serve, serve-static and conninfo imports unchanged in src/index.js.
  • @commitlint/cli ^21.2.3 → ^21.2.4 (and config-conventional): Dev-tooling patch bump; commitlint.config extends the default config-conventional, no surface change.
  • @playwright/test ^1.64.0 → ^1.65.0: Minor dev-tooling bump (playwright-core 1.65.0, @opentelemetry/semantic-conventions 1.64→1.65); e2e/oauth-flow.spec.js shape unchanged and not exercised by the listed verification results.
  • eslint ^10.12.0 → ^10.14.0: Dev-tooling patch bump with transitive glob 13→14 and path-scurry 2→3 (dev-path only); eslint.config.js uses defineConfig/js.recommended, unchanged.
  • fallow 3.32.0 → 3.42.0: Dev-tooling bump with matching platform binaries (@fallow-cli/*) and fallow-type-aware; pinned exact, script-level usage only.
  • globals ^17.13.0 → ^17.14.0: Dev-tooling patch bump; used only for globals.node / globals.browser in eslint.config.js.
  • prettier ^3.9.9 → ^3.10.1: Minor dev-tooling bump via lint-staged and prettier:check script; no API surface in use.
  • tap ^21.8.0 → ^21.8.1: Dev-tooling patch bump with matching @tapjs/* patch bumps; runs the suites that passed.
  • zizmorcore/zizmor-action v0.8.0 → v0.8.1 (GitHub Action): Separate dependabot commit merged into this branch; CI workflow only, not an npm dependency and no runtime effect.
  • pino 10.4.0 / hono-pino 0.10.3 (unchanged, emitting): Left unchanged; hono-pino's hono >=4.0.0 and pino >=7.1.0 peers remain satisfied by the bumped hono. No impact from this diff.
Usage of 10 dependencies
  • better-auth: src/auth.js (betterAuth config: database pool, socialProviders.github, session, jwt plugin with issuer/audience 'planner'); src/app/utils/auth.js (Auth type import); scripts/migrate.js and test/helpers/test-instance.js (getMigrations → runMigrations).
  • @better-auth/oauth-provider: src/auth.js (oauthProvider plugin: scopes, validAudiences, accessTokenExpiresIn, customIdTokenClaims adding github_id).
  • hono: src/app/*.js — app construction and hono/html rendering across routes and components.
  • @hono/node-server: src/index.js (serve), plus serve-static and conninfo import sites.
  • hono-pino: src/app/app.js (logger middleware).
  • pg: src/auth.js (Pool), test/helpers/container.js, test-instance — unchanged by the PR.
  • pino: peer of hono-pino in src/app/app.js — unchanged by the PR.
  • date-fns: 2 import sites in src/app — unchanged by the PR.
  • eslint / globals / prettier / commitlint / fallow: eslint.config.js (globals.node, globals.browser), package.json scripts and hooks — dev tooling only.
  • tap / @playwright/test / sinon: test/**/*.test.js via tap.yml, e2e/oauth-flow.spec.js — dev tooling only.
Test coverage
  • ["Strong: auth-suite exercises the bumped runtime surface directly — features/oauth-provider.test.js, integration/oauth-flow.test.js, integration/jwt-payload.test.js, unit tests for github-provider/id-token-claims/cookies.", "Strong: probe (pass) verifies the planner↔auth round-trip, the cross-service OAuth/JWT contract the oauth-provider bump could break.", "Strong: better-auth migration API covered — test-instance.js runs runMigrations on a real Postgres container before every suite.", "Gap: the Playwright e2e suite (e2e/oauth-flow.spec.js) is not among the listed verification results, and @playwright/test moved a minor version (1.64→1.65); the integration oauth-flow test overlaps its scope.", "Gap: dev-tooling bumps (eslint, prettier, commitlint, fallow, playwright) have no test coverage beyond lint scripts; impact limited to developer workflow."].
Calibration and confidence

Confidence: High — All three verification results pass, runtime bumps are patch-band within existing carets, peer ranges resolve cleanly in the lockfile at the head, and both the OAuth contract and the migration path are exercised by tests at this head.

  1. Weakest claim: Skip of the e2e suite is the weakest evidence point, partially mitigated by the integration oauth-flow test and the passing probe.
  2. Relied on but unverified: The Playwright e2e suite was not among the listed verification results; browser-level cookie behavior under the bumped better-auth and @playwright/test is not verified by the given results.
  3. Falsifier: Running the unlisted Playwright e2e suite under @playwright/test 1.65, or running the probe against production-shaped cookies (Cloudflare __Secure- stripping) with skipStateCookieCheck behavior after the 1.7.22 bump, would falsify this verdict if either fails.
Previous verdicts
  • 2026-11-12T10:30:02.953Z head 17f36e401ad86104c0e53ce22ce13f802071759e: blocked: baseline red (Low)

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/npm-deps-01608cf1db branch from 17f36e4 to 969b2c6 Compare November 12, 2026 10:15
Bumps the npm-deps group with 12 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@better-auth/oauth-provider](https://github.com/better-auth/better-auth/tree/HEAD/packages/oauth-provider) | `1.7.7` | `1.7.22` |
| [@hono/node-server](https://github.com/honojs/node-server) | `2.1.4` | `2.1.7` |
| [better-auth](https://github.com/better-auth/better-auth/tree/HEAD/packages/better-auth) | `1.7.7` | `1.7.22` |
| [hono](https://github.com/honojs/hono) | `4.13.13` | `4.13.18` |
| [@commitlint/cli](https://github.com/conventional-changelog/commitlint/tree/HEAD/@commitlint/cli) | `21.2.3` | `21.2.4` |
| [@commitlint/config-conventional](https://github.com/conventional-changelog/commitlint/tree/HEAD/@commitlint/config-conventional) | `21.2.3` | `21.2.4` |
| [@playwright/test](https://github.com/microsoft/playwright) | `1.64.0` | `1.65.0` |
| [eslint](https://github.com/eslint/eslint) | `10.12.0` | `10.14.0` |
| [fallow](https://github.com/fallow-rs/fallow) | `3.32.0` | `3.42.0` |
| [globals](https://github.com/sindresorhus/globals) | `17.13.0` | `17.14.0` |
| [prettier](https://github.com/prettier/prettier) | `3.9.9` | `3.10.1` |
| [tap](https://github.com/tapjs/tapjs) | `21.8.0` | `21.8.1` |



Updates `@better-auth/oauth-provider` from 1.7.7 to 1.7.22
- [Release notes](https://github.com/better-auth/better-auth/releases)
- [Changelog](https://github.com/better-auth/better-auth/blob/main/packages/oauth-provider/CHANGELOG.md)
- [Commits](https://github.com/better-auth/better-auth/commits/v1.7.22/packages/oauth-provider)

Updates `@hono/node-server` from 2.1.4 to 2.1.7
- [Release notes](https://github.com/honojs/node-server/releases)
- [Commits](honojs/node-server@v2.1.4...v2.1.7)

Updates `better-auth` from 1.7.7 to 1.7.22
- [Release notes](https://github.com/better-auth/better-auth/releases)
- [Changelog](https://github.com/better-auth/better-auth/blob/main/packages/better-auth/CHANGELOG.md)
- [Commits](https://github.com/better-auth/better-auth/commits/v1.7.22/packages/better-auth)

Updates `hono` from 4.13.13 to 4.13.18
- [Release notes](https://github.com/honojs/hono/releases)
- [Commits](honojs/hono@v4.13.13...v4.13.18)

Updates `@commitlint/cli` from 21.2.3 to 21.2.4
- [Release notes](https://github.com/conventional-changelog/commitlint/releases)
- [Changelog](https://github.com/conventional-changelog/commitlint/blob/master/@commitlint/cli/CHANGELOG.md)
- [Commits](https://github.com/conventional-changelog/commitlint/commits/v21.2.4/@commitlint/cli)

Updates `@commitlint/config-conventional` from 21.2.3 to 21.2.4
- [Release notes](https://github.com/conventional-changelog/commitlint/releases)
- [Changelog](https://github.com/conventional-changelog/commitlint/blob/master/@commitlint/config-conventional/CHANGELOG.md)
- [Commits](https://github.com/conventional-changelog/commitlint/commits/v21.2.4/@commitlint/config-conventional)

Updates `@playwright/test` from 1.64.0 to 1.65.0
- [Release notes](https://github.com/microsoft/playwright/releases)
- [Commits](microsoft/playwright@v1.64.0...v1.65.0)

Updates `eslint` from 10.12.0 to 10.14.0
- [Release notes](https://github.com/eslint/eslint/releases)
- [Commits](eslint/eslint@v10.12.0...v10.14.0)

Updates `fallow` from 3.32.0 to 3.42.0
- [Release notes](https://github.com/fallow-rs/fallow/releases)
- [Changelog](https://github.com/fallow-rs/fallow/blob/main/release.toml)
- [Commits](fallow-rs/fallow@v3.32.0...v3.42.0)

Updates `globals` from 17.13.0 to 17.14.0
- [Release notes](https://github.com/sindresorhus/globals/releases)
- [Commits](sindresorhus/globals@v17.13.0...v17.14.0)

Updates `prettier` from 3.9.9 to 3.10.1
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/prettier@3.9.9...3.10.1)

Updates `tap` from 21.8.0 to 21.8.1
- [Release notes](https://github.com/tapjs/tapjs/releases)
- [Commits](https://github.com/tapjs/tapjs/compare/tap@21.8.0...tap@21.8.1)

---
updated-dependencies:
- dependency-name: "@better-auth/oauth-provider"
  dependency-version: 1.7.16
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-deps
- dependency-name: "@commitlint/cli"
  dependency-version: 21.2.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-deps
- dependency-name: "@commitlint/config-conventional"
  dependency-version: 21.2.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-deps
- dependency-name: "@hono/node-server"
  dependency-version: 2.1.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-deps
- dependency-name: "@playwright/test"
  dependency-version: 1.64.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-deps
- dependency-name: better-auth
  dependency-version: 1.7.16
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-deps
- dependency-name: eslint
  dependency-version: 10.14.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-deps
- dependency-name: fallow
  dependency-version: 3.39.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-deps
- dependency-name: globals
  dependency-version: 17.14.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-deps
- dependency-name: hono
  dependency-version: 4.13.16
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-deps
- dependency-name: prettier
  dependency-version: 3.9.10
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-deps
- dependency-name: tap
  dependency-version: 21.8.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/npm-deps-01608cf1db branch from 969b2c6 to 15b3e90 Compare November 19, 2026 10:15

This branch has not been deployed

No deployments
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 javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant