@clerk/astro
4.1.27 · 18 Nov 2026MIT46.5k / weekRepositoryHomepagenpmAtom feed
Upgrading @clerk/astro From 2.17.18 to 3.0.18
16 releases in betweenevery note read
Reading releases, release notes and advisories…
- 7
- changes to make
- 0
- advisories fixed
- 6
- new
- 7
- fixes
Before you upgrade
Tick each one off as you go- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
Security
- 3.0.13
Bump
astrodevDependency floor to5.18.1to pick up an upstream security fix.
Release by release
3.0.16 – 3.0.183 releases, nothing new or fixed in the notes
- Fixed
Normalize URL paths in
createPathMatcherto prevent route protection bypass
- Fixed
3.0.14nothing new or fixed in the note
- Security
Bump
astrodevDependency floor to5.18.1to pick up an upstream security fix. - Fixed
Simplified keyless service initialization.
- Security
3.0.8 – 3.0.123 releases, nothing new or fixed in the notes
- Fixed
Fix Cloudflare Pages compatibility by falling through to
locals.runtime.envwhencloudflare:workersenv is missing the requested key
- Fixed
3.0.2 – 3.0.64 releases, nothing new or fixed in the notes
- Fixed
Update README prerequisites to match actual
package.jsonengine and peer dependency constraints.
- Fixed
2 other lines we could not sort, mostly version bumps
- 3.0.0
Renamed all
__unstable_*methods to__internal_*(for internal APIs) - 3.0.0
Renamed all
experimental__*andexperimental_*methods to__experimental_*(for beta features)
28 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.