Packages

@clerk/astro

4.1.27 · 18 Nov 2026MIT46.5k / weekRepositoryHomepagenpmAtom feed

Upgrading @clerk/astro From 2.1.5 to 2.17.18

139 releases in betweennotes for 138

Reading releases, release notes and advisories…

Other targets from 2.1.5Clears its 2 advisories2.17.11Latest4.1.27
  1. 2.1.5yours
  2. 70 releases
  3. 2.11.0breaking
  4. 67 releases
  5. 2.17.18target
3+
changes to make
2
advisories fixed
25+
new
18+
fixes

Counted from 138 of 139 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking2.11.0
  • Deprecated2.14.3
  • Deprecated2.4.0

Security

Release by release

  1. 2.17.18

    18 Nov 20262 fixes
    • Fixed

      Fix $billingStore so it emits the billing namespace only after Clerk has loaded. Before, it could emit while clerk.load() was still running, so a call like getPlans() in a subscriber could fail with a dev_browser_unauthenticated error on development instances.

    • Fixed

      Fix clerkMiddleware so it adds Clerk's tags to the page once, right before the closing </head> tag. It now finds that tag even when a streamed response splits it across two chunks. The server data now goes in <meta> tags, and clerk-js is preloaded with a <link> tag and loaded by the integration's page script.

  2. 2.17.11 – 2.17.177 releases, nothing new or fixed; 1 without a note

  3. 2.17.10

    15 Apr 20261 fix
    • Fixed

      Normalize URL paths in createPathMatcher to prevent route protection bypass

  4. 2.17.3 – 2.17.97 releases, nothing new or fixed in the notes

  5. 2.17.2

    13 Feb 20261 fix
    • Fixed

      Fixed an issue when using ClientRouter where Clerk components don't load until navigation is performed.

  6. 2.17.1nothing new or fixed in the note

  7. 2.17.0

    4 Feb 20261 new
    • New

      Add $billingStore for access to the Clerk.billing object containing various Clerk Billing methods.

  8. 2.16.17

    30 Jan 20261 fix
    • Fixed

      Fixed an error when using Control components (<SignedIn />, <SignedOut />) in prerendered pages

384 internal lines (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.