Repository navigation
chore(deps): Update all non-major dependencies - #92
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.7.18→^1.7.22^1.7.18→^1.7.22^2.1.6→^2.1.8^1.7.18→^1.7.22^4.13.17→^4.13.18^3.9.10→^3.10.1^6.37.0→^6.38.0^8.72.1→^8.72.2Release Notes
better-auth/better-auth (@better-auth/passkey)
v1.7.22Compare Source
v1.7.21Compare Source
Patch Changes
#12388
070d101Thanks @gustavovalverde! - If a wildcard inbaseURL.allowedHostscovers your passkeyrpID, such asrpID: "example.com"withallowedHosts: ["*.example.com"], your server now starts without a passkeyorigin. Since 1.7.16 it threw at startup unlessoriginwas 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 exactallowedHostsentry, thefallbackorigin, or an origin listed exactly intrustedOrigins. The host the request names and wildcard entries do not count. To allow tenants added at runtime, return their origins from atrustedOriginsfunction that checks your tenant records. If you setorigin, or no wildcard covers yourrpID, nothing changes.v1.7.20Compare Source
v1.7.19Compare Source
better-auth/better-auth (@better-auth/redis-storage)
v1.7.22Compare Source
v1.7.21Compare Source
v1.7.20Compare Source
v1.7.19Compare Source
honojs/node-server (@hono/node-server)
v2.1.8Compare Source
What's Changed
Full Changelog: honojs/node-server@v2.1.7...v2.1.8
v2.1.7Compare Source
Security fixes
This release includes a fix for the following security issue:
serveStaticwithallowPercentInPathstill allows the double-decode middleware bypassAffects:
serveStaticwithallowPercentInPath: true. The fix for GHSA-rmxm-3fg6-px4f rejects a path containing%, but theallowPercentInPathoption skipped that check entirely. A malformed percent sequence such as/static/%%36%31dmin/secret.txtwas routed as/static/%61dmin/secret.txt, so middleware on/static/admin/*did not run, andserveStaticthen decoded%61toaand servedstatic/admin/secret.txt. The default configuration was already fixed in 2.1.3. GHSA-fj57-4f93-cfw6serveStaticnow accepts the second decode only when its result equals the routed path with%25replaced by%. File names containing a literal%, requested as%25, are served as before.The same fix ships in
honov4.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.22Compare Source
Patch Changes
#12324
80c407bThanks @bytaesu! - FixedReferenceError: window is not definedwhen a client session subscription is cleaned up after a test environment such as happy-dom tears down its globals.#12462
d32a30aThanks @bytaesu! - Fixed session polling never firing when the runtime'snavigatordoes not report connectivity.#12324
80c407bThanks @bytaesu! - Fixed client session refresh listeners piling up on the server during SSR.#12321
946177eThanks @bytaesu! - Revoking your current session withrevokeSessionorrevokeSessions, and deleting your account withdeleteUser({ token }), now expire the session cookies, so a cached session is no longer returned afterwards.#12459
d210421Thanks @bytaesu! -getSessionno longer leaves an expired session in the request context after returningnull.#12331
485567eThanks @bytaesu! - OAuth sign-up rejected by auser.create.beforehook returningfalseno longer logs aTypeError. It still fails withunable_to_create_user.#12334
ec3047dThanks @bytaesu! - FixeddeleteOrganizationclearing the session's active organization when abeforeDeleteOrganizationhook rejected the delete. The active organization is now cleared only after the organization is actually deleted.#12330
d521343Thanks @bytaesu! - FixdeferSessionRefreshrefresh requests failing with 415 in Next.js and Nuxt, where the bodylessPOST /get-sessionreached the handler as an empty stream without aContent-Type.#12451
71052afThanks @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
79219b4Thanks @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]:v1.7.21Compare Source
Patch Changes
#12126
4739122Thanks @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, andprivate_key_jwtclient authentication are fixed the same way, and Sign-In with Ethereum now keeps the email the user supplied instead of a placeholder. Setups with plainStringid columns and other databases are unaffected.#12392
a277020Thanks @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
1c3410aThanks @lakshya-dhariwal! - If you setadvanced.backgroundTasks.handlerand your database adapter runs transactions (the built-in Kysely connection, MongoDB withclient, or Prisma or Drizzle withtransaction: true), email sign-up now keeps the database writes made while sending the verification email or runningonExistingUserSignUp. Before, those writes failed because the sign-up had already been saved. WithemailOTP({ 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. IfsendVerificationEmailthrows, the sign-up succeeds and the error is logged; before, the sign-up failed. To reject a sign-up, use adatabaseHooks.user.create.beforehook. IfonExistingUserSignUpthrows, the error is logged and the request still returns the generic response.#12179
9105261Thanks @ghazy2001! - Generic OAuth providers configured withdiscoveryHeadersnow send those headers when fetching the provider's signing keys from ajwks_urion the same origin asdiscoveryUrl. 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. Ajwks_urion another origin still gets no headers.With
discoveryHeadersset, the discovery request now follows redirects only within the origin ofdiscoveryUrl, so the headers no longer reach another host. If yourdiscoveryUrlredirects to another origin, discovery now fails and Better Auth logs an error. SetdiscoveryUrlto the final URL. Providers withoutdiscoveryHeadersare unaffected.#12401
c3a94c5Thanks @gustavovalverde! - Generic OAuth providers configured withauthorizationHeadersnow 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 withoutauthorizationHeadersare unaffected.refreshAccessTokenandrefreshAccessTokenRequestfrom@better-auth/core/oauth2accept an optionalheadersinput 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
Authorizationwithauthentication: "basic", no longer produce a combined, invalid header on the code exchange or refresh. Client authentication replaces them, including headers a customtokenEndpointAuthhook sets in any casing.#12404
9b40ac6Thanks @bytaesu! - Plugin packages no longer import from thebetter-authroot, so bundlers that split code stop emitting unused Kysely chunks when used withbetter-auth/minimal.#12395
b0ced9dThanks @gustavovalverde! - On Cloudflare Workers, sign-ins with agenericOAuthprovider that usesdiscoveryUrl, 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
5c12074Thanks @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 andnpx auth@latest migrateno longer fail intermittently withschema "…" does not existorrelation "…" does not exist. The startup schema check now reads only the schemas on the connection'ssearch_path, plus any schema set withschemaNameor a schema plugin, andmigratereads 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
e64f624Thanks @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.20Compare Source
Patch Changes
a3f50d0,e9b43d7,265629c,e9b43d7]:v1.7.19Compare Source
Patch Changes
#12323
a10121dThanks @bytaesu! - Fixed theactive-sessionslist in secondary storage being stored without an expiry when the last remaining session had less than a second left.#12335
c41f8ffThanks @bytaesu! - Fixed/admin/create-userleaving 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 withUSER_ALREADY_EXISTS_USE_ANOTHER_EMAIL.#12338
e786566Thanks @bytaesu! - Fixed/admin/create-userleaving a user without a credential account when creating that account failed, which made retrying with the same email fail withUSER_ALREADY_EXISTS_USE_ANOTHER_EMAIL.#12336
ac778b7Thanks @bytaesu! - Client actions now send the HTTP method passed in the second-argument fetch options, the same as when it is nested underfetchOptions. Passing a lowercasegetorHEADmethod no longer fails because a request body was attached.#12246
5eb69d8Thanks @AryaKesharwani! -/device/tokennow returnsinvalid_clientinstead ofinvalid_grantwhenvalidateClientrejects theclient_id, matching/device/codeand RFC 6749 section 5.2.#12319
4b0327bThanks @bytaesu! - Plugin schema overrides (modelNameand field names) no longer leak into other instances of the same plugin in one process.#12320
2d5ef64Thanks @bytaesu! - Fix OAuth sign-in failing withstate_mismatchduring 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
5f0a0fcThanks @bytaesu! - The OpenAPI schema now documents query parameters for endpoints whose query schema is wrapped inz.optional(), such as/get-sessionand Stripe's/subscription/list.#12332
89e74b8Thanks @bytaesu! - Fixedorganization.getInvitationreturning a missing, expired, or non-pending invitation error without acode. It now returnsINVITATION_NOT_FOUNDlike the other invitation endpoints.#12318
525bd7aThanks @bytaesu! - FixlistMembersfailing with a syntax error on PostgreSQL and MSSQL when the filter or offset matches no members.#12366
23a60a3Thanks @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
29e45f8Thanks @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.18Compare Source
Security fixes
This release includes fixes for the following security issues:
validator()skips validation for requests whoseContent-Typeparameters are formatted differentlyAffects:
validator('json')andvalidator('form')inhono/validator. AContent-Typewith 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, asc.req.parseBody()does. GHSA-92p4-j3wq-jmqxbodyLimit()keeps every transfer chunk of a request body in memoryAffects:
bodyLimit()inhono/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 bymaxSize. GHSA-39q9-qp46-w8xgmount()andapp.mount()forward a wrong path when a customgetPathadds a prefixAffects:
mount()inhono/mountandapp.mount()on 4.13.16 and 4.13.17. With agetPaththat 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-qj33serveStatic()serves a path that was decoded twice whenallowPercentInPathis enabledAffects:
serveStatic()inhono/serve-staticand the runtime adapters, only withallowPercentInPath: 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-3fwpUsers who rely on
validator(),bodyLimit(),mount()with a customgetPath, orserveStatic()withallowPercentInPathare strongly encouraged to upgrade to this version.Full Changelog: honojs/hono@v4.13.17...v4.13.18
prettier/prettier (prettier)
v3.10.1Compare Source
diff
GraphQL: Fix empty selection set with comments (#20504 by @fisker)
v3.10.0Compare Source
diff
🔗 Release Notes
resend/resend-node (resend)
v6.38.0Compare Source
What's Changed
Full Changelog: resend/resend-node@v6.37.0...v6.38.0
typescript-eslint/typescript-eslint (typescript-eslint)
v8.72.2Compare 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)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.