Skip to content

Update Routine updates#376

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/routine-updates
Open

Update Routine updates#376
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/routine-updates

Conversation

@renovate

@renovate renovate Bot commented May 12, 2026

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 Type Update Pending
@better-auth/core (source) 1.6.151.6.18 age confidence devDependencies patch 1.6.19
@better-auth/test-utils (source) 1.6.151.6.18 age confidence devDependencies patch 1.6.19
@better-fetch/fetch (source) 1.1.211.3.0 age confidence dependencies minor 1.3.1
@tailwindcss/postcss (source) 4.3.04.3.1 age confidence devDependencies patch
@tanstack/react-start (source) 1.167.651.168.25 age confidence devDependencies minor 1.168.26
@types/mdx (source) 2.0.132.0.14 age confidence devDependencies patch
@types/node (source) 24.12.324.13.2 age confidence devDependencies minor
@types/react (source) 19.2.1419.2.17 age confidence devDependencies patch
actions/checkout (changelog) de0fac2df4cb1c action digest
better-auth (source) 1.6.151.6.18 age confidence devDependencies patch 1.6.19
convex-helpers (source) 0.1.1160.1.119 age confidence dependencies patch
convex-test (source) 0.0.510.0.53 age confidence devDependencies patch
eslint (source) 10.3.010.5.0 age confidence devDependencies minor
eslint-config-next (source) 16.2.616.2.9 age confidence devDependencies patch
eslint-plugin-react-refresh 0.5.20.5.3 age confidence devDependencies patch
fumadocs-core 16.8.816.10.2 age confidence dependencies minor 16.10.4 (+1)
fumadocs-ui 16.8.816.10.2 age confidence dependencies minor 16.10.4 (+1)
next (source) 16.2.616.2.9 age confidence devDependencies patch
next (source) 16.2.616.2.9 age confidence dependencies patch
pkg-pr-new (source) 0.0.710.0.75 age confidence devDependencies patch
postcss (source) 8.5.148.5.15 age confidence devDependencies patch
prettier (source) 3.8.33.8.4 age confidence devDependencies patch
react (source) 19.2.619.2.7 age confidence devDependencies patch
react (source) 19.2.619.2.7 age confidence dependencies patch
react-dom (source) 19.2.619.2.7 age confidence devDependencies patch
react-dom (source) 19.2.619.2.7 age confidence dependencies patch
remeda (source) 2.34.02.39.0 age confidence dependencies minor
semver 7.8.07.8.4 age confidence dependencies patch
tailwindcss (source) 4.3.04.3.1 age confidence devDependencies patch
type-fest 5.6.05.7.0 age confidence dependencies minor
typescript-eslint (source) 8.59.28.61.0 age confidence devDependencies minor 8.61.1
vitest (source) 4.1.54.1.8 age confidence devDependencies patch 4.1.9

Release Notes

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

v1.6.18

Compare Source

Patch Changes
  • #​9583 b21a5f7 Thanks @​GautamBytes! - Fix plugin-provided client methods and additional session fields not being inferred in composite monorepos.

v1.6.17

Compare Source

Patch Changes
  • #​9993 baeaa00 Thanks @​gustavovalverde! - Add the optional incrementOne adapter method and the optional SecondaryStorage.increment method. incrementOne atomically applies signed numeric deltas to a single row under a where-clause guard (for example, decrementing a remaining-uses counter only while it is still positive) and returns the updated row, or null when the guard matched no row. Adapters that do not implement it natively keep working through a transaction-based fallback. SecondaryStorage.increment atomically increments a counter and sets its time-to-live only when the key is first created.

  • #​9987 7343284 Thanks @​bytaesu! - Fixed a memory leak where the JWKS cache could grow on every access token verification.

  • #​10003 fdef997 Thanks @​gustavovalverde! - Microsoft Entra ID sign-in now honors the configured tenant restriction. tenantId: "organizations" rejects personal Microsoft accounts, and tenantId: "consumers" rejects work and school accounts. Both were accepted before.

  • #​9993 baeaa00 Thanks @​gustavovalverde! - Concurrent requests can no longer slip past the configured rate limit. The in-memory rate-limit store no longer grows without bound, and the database backend removes expired entries on its own. A custom rate-limit storage may implement a new optional consume method for strict enforcement; without it, the previous behavior is kept and a one-time warning is logged.

  • #​10003 fdef997 Thanks @​gustavovalverde! - A Reddit user with no email now receives a non-routable placeholder address (<id>@&#8203;reddit.invalid) instead of one on the real reddit.com domain, so it cannot match a deliverable mailbox. The address stays unverified, and mapProfileToUser can supply a real email.

  • #​9993 baeaa00 Thanks @​gustavovalverde! - Add internalAdapter.reserveVerificationValue. It atomically records a single-use marker (such as a replay tombstone) so that exactly one of several concurrent callers succeeds and the rest observe that the marker is already taken. Database-backed verification storage is atomic; secondary-storage-only verification is best-effort.

  • #​9990 1dbf5bb Thanks @​gustavovalverde! - Hardens how requests are trusted across several flows. Rate limiting is now enforced even when a client IP cannot be determined, instead of being skipped. When baseURL is not configured, password-reset and verification links use the current request's host rather than the host of the first request the server handled, and a request-scoped trustedOrigins callback no longer affects other concurrent requests. The OAuth proxy, Google One Tap, and the Expo authorization proxy reject redirect and callback targets that are not in trustedOrigins. Google reCAPTCHA and Cloudflare Turnstile accept optional expectedAction and allowedHostnames to reject tokens minted for a different action or hostname. Server-side fetches reject additional reserved IPv6 ranges, and malformed redirect parameters return a 400 instead of a 500.

  • #​10003 fdef997 Thanks @​gustavovalverde! - WeChat sign-in now succeeds with the documented default setup, which previously failed because WeChat returns no email address. The created user receives a stable, unverified placeholder email; supply a real one with mapProfileToUser.

v1.6.16

Compare Source

Patch Changes
  • #​9974 cb1cbfa Thanks @​Bekacru! - Validate Facebook opaque access tokens against the configured app. Previously verifyIdToken returned true for any non-JWT token and getUserInfo called Graph /me with the caller-supplied token without checking which app issued it, so tokens issued for other Facebook apps were not distinguished on the direct sign-in path. Facebook tokens are now inspected via the debug_token endpoint, requiring is_valid, an app_id that matches one of the configured client ids, and a user_id that matches the returned profile, before the token is accepted. A client secret must be configured for access-token sign-in to work.

  • #​9974 cb1cbfa Thanks @​Bekacru! - Enforce the Google hd (hosted domain) option against the id token. Previously hd was only sent to Google as an authorization hint, which does not by itself restrict sign-in to the configured Workspace domain. When hd is set, the hd claim on the verified id token (verifyIdToken) and the decoded callback profile (getUserInfo) must be present and match, otherwise sign-in is rejected.

  • #​9974 cb1cbfa Thanks @​Bekacru! - Scope the JWKS cache per source. Access-token verification previously kept a single global key set and reused it whenever it contained a key matching the token's kid, without considering which JWKS source the verification was for. When verifying tokens against more than one source, a token could end up matched against keys fetched for a different source if the two shared a kid. The cache is now keyed per JWKS source and honors a TTL, so each verification uses the keys for its own source and rotated or removed keys are no longer used after the TTL elapses.

  • #​9974 cb1cbfa Thanks @​Bekacru! - Cryptographically verify PayPal ID tokens on direct sign-in. Previously verifyIdToken only decoded the JWT and checked that a sub claim was present, performing no signature, issuer, audience, or expiration checks, so any well-formed token paired with a valid access token would be accepted. The token is now verified against PayPal's issuer and published JWKS (RS256) or the client secret (HS256), with the aud pinned to the configured clientId, a maxTokenAge bound, and the nonce checked when supplied.

  • #​9974 cb1cbfa Thanks @​Bekacru! - Stop mapping the Reddit oauth_client_id to the user's email. Reddit's identity scope does not return an email address, and the provider previously stored oauth_client_id (which identifies the OAuth application and is the same for every user of the app) as user.email with has_verified_email as emailVerified. This collapsed all Reddit users of the same app onto a single "verified" email, which could enable implicit account linking/takeover. The Reddit provider now uses the email returned from mapProfileToUser when provided, otherwise falls back to a unique per-user synthetic address (<reddit-user-id>@&#8203;reddit.com), and no longer marks it as verified. Provide a real email via mapProfileToUser if you need the actual address.

  • #​9974 cb1cbfa Thanks @​Bekacru! - Fix verifyAccessToken silently dropping the configured audience check during remote introspection. Previously, when a required audience was set in verifyOptions but the introspection response omitted the aud claim, audience validation was skipped and any active token from the issuer was accepted — so a token issued for a different resource or client on the same issuer could also pass verification. Verification now requires the claim: a missing or mismatching aud is rejected. Authorization servers that legitimately omit aud from introspection responses (it is OPTIONAL per RFC 7662) can opt back into the old behavior with the new remoteVerify.allowMissingAudience: true flag, which still rejects mismatching audiences.

better-auth/better-auth (@​better-auth/test-utils)

v1.6.18

Compare Source

Patch Changes

v1.6.17

Compare Source

Patch Changes

v1.6.16

Compare Source

Patch Changes
better-auth/better-fetch (@​better-fetch/fetch)

v1.3.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.2.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.2.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.2.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
tailwindlabs/tailwindcss (@​tailwindcss/postcss)

v4.3.1

Compare Source

Added
  • Add --silent option to suppress output in @tailwindcss/cli (#​20100)
Fixed
  • Remove deprecation warnings by using Module#registerHooks instead of Module#register on Node 26+ (#​20028)
  • Canonicalization: don't crash when plugin utilities throw for unsupported values (#​20052)
  • Allow @apply to be used with CSS mixins (#​19427)
  • Ensure not-* correctly negates @container queries, including style(…) queries (#​20059)
  • Ensure drop-shadow-* color utilities work with custom shadow values containing calc(…) (#​20080)
  • Fix 'Sourcemap is likely to be incorrect' warnings when using @tailwindcss/vite (#​20103)
  • Ensure @tailwindcss/webpack can be installed in Rspack projects without requiring webpack as a peer dependency (#​20027)
  • Canonicalization: don't suggest invalid calc(…) expressions (e.g. px-[calc(1rem+0px)]px-[calc(1rem+0)]) (#​20127)
  • Canonicalization: avoid suggesting large spacing-scale values for arbitrary lengths (e.g. left-[99999px]left-[99999px], not left-24999.75) (#​20130)
  • Ensure @tailwindcss/cli in --watch mode recovers when a tracked dependency is deleted and restored (#​20137)
  • Ensure standalone @tailwindcss/cli binaries are ignored when scanning for class candidates (#​20139)
  • Ensure class candidates are extracted from Twig addClass(…) and removeClass(…) calls (#​20198)
  • Don't crash in the Ruby or Vue preprocessors when scanning files containing invalid UTF-8 bytes (#​19588)
  • Allow @variant to be used inside addBase (#​19480)
  • Ensure @source globs with symlinks are preserved (#​20203)
  • Ensure later @source rules can re-include files excluded by earlier @source not rules (#​20203)
  • Upgrade: don't migrate empty class rules to invalid @utility rules (#​20205)
  • Ensure transitions between inset-shadow-none and other inset shadows work correctly (#​20208)
  • Ensure explicitly referenced @source directories are scanned even when ignored by git (#​20214)
  • Ensure @source globs ending in **/* preserve dynamic path segments to avoid scanning too many files (#​20217)
  • Canonicalization: don't fold calc(…) divisions when the result would require high precision (e.g. w-[calc(100%/3.5)]w-[calc(100%/3.5)], not w-[28.571428571428573%]) (#​20221)
  • Serve ESM type declarations to ESM importers of @tailwindcss/postcss (#​20228)
Changed
  • Generate 0 instead of calc(var(--spacing) * 0) for spacing utilities like m-0 and left-0 (#​20196)
  • Generate var(--spacing) instead of calc(var(--spacing) * 1) for spacing utilities like m-1 and left-1 (#​20196)
TanStack/router (@​tanstack/react-start)

v1.168.25

Compare Source

Patch Changes

v1.168.24

Compare Source

Patch Changes

v1.168.23

Compare Source

Patch Changes

v1.168.22

Compare Source

Patch Changes

v1.168.21

Compare Source

Patch Changes

v1.168.20

Compare Source

Patch Changes

v1.168.19

Compare Source

Patch Changes

v1.168.18

Compare Source

Patch Changes

v1.168.17

Compare Source

Patch Changes

v1.168.16

Compare Source

Patch Changes

v1.168.15

Compare Source

Patch Changes

v1.168.14

Compare Source

Patch Changes
  • #​7492 71fb329 - Avoid pulling the client hydration entry into root @tanstack/react-start and @tanstack/solid-start imports by re-exporting Hydrate from framework client Hydrate-only subpaths.

  • Updated dependencies [71fb329]:

v1.168.13

Compare Source

Patch Changes

v1.168.12

Compare Source

Patch Changes
  • Add Vite bundled dev mode support for TanStack Start. Start now recognizes Vite's experimental.bundledDev opt-in, uses the bundled dev client entry in the dev manifest, keeps server requests pointed at the latest client build output, and preserves import-pro

Note

PR body was truncated to here.


Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • Monday through Friday (* * * * 1-5)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

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


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel

vercel Bot commented May 12, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
better-auth Ready Ready Preview, Comment Jun 17, 2026 7:13pm

Request Review

@pkg-pr-new

pkg-pr-new Bot commented May 12, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@convex-dev/better-auth@376

commit: 5fab04d

@renovate renovate Bot force-pushed the renovate/routine-updates branch from 63dc237 to 87fb859 Compare May 13, 2026 09:38
@renovate renovate Bot changed the title Update Routine updates to v1.6.10 Update Routine updates May 13, 2026
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 87fb859 to 8e9ad8a Compare May 14, 2026 18:34
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 8e9ad8a to 4d7b750 Compare May 14, 2026 20:25
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 4d7b750 to 1787003 Compare May 15, 2026 01:29
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 1787003 to 931f226 Compare May 15, 2026 17:14
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 931f226 to 267cd41 Compare May 16, 2026 12:42
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 267cd41 to e56c97b Compare May 16, 2026 17:23
@renovate renovate Bot force-pushed the renovate/routine-updates branch from e56c97b to 0351eb0 Compare May 16, 2026 21:10
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 0351eb0 to 1c30557 Compare May 17, 2026 09:36
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 1c30557 to fe7ffe2 Compare May 18, 2026 01:28
@renovate renovate Bot force-pushed the renovate/routine-updates branch from fe7ffe2 to 8545fd6 Compare May 18, 2026 11:11
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 8545fd6 to 541d1b4 Compare May 18, 2026 20:39
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 541d1b4 to 470bc50 Compare May 19, 2026 01:42
@renovate renovate Bot force-pushed the renovate/routine-updates branch from f63f20d to 2d561dd Compare May 22, 2026 09:53
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 2d561dd to 8ebc2c3 Compare May 22, 2026 15:47
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 8ebc2c3 to c85954d Compare May 22, 2026 17:57
@renovate renovate Bot force-pushed the renovate/routine-updates branch from c85954d to 1540bb6 Compare May 22, 2026 23:08
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 1540bb6 to bc74f48 Compare May 22, 2026 23:23
@renovate renovate Bot force-pushed the renovate/routine-updates branch from bc74f48 to 6fea059 Compare May 23, 2026 09:56
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 6fea059 to 6c27629 Compare May 23, 2026 12:24
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 6c27629 to 8a95d30 Compare May 23, 2026 21:41
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 8a95d30 to 7ac7b81 Compare May 24, 2026 00:48
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 7ac7b81 to 2f2291a Compare May 24, 2026 08:41
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 2f2291a to 9da4dbe Compare May 24, 2026 20:35
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 9da4dbe to 21066f2 Compare May 25, 2026 01:58
@renovate renovate Bot force-pushed the renovate/routine-updates branch from 21066f2 to e4a7540 Compare May 26, 2026 15:43
@renovate renovate Bot force-pushed the renovate/routine-updates branch from e4a7540 to 940f01b Compare May 27, 2026 01:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants