Skip to main content

v0.3.3

Fixed​

  • API keys identify the caller on public routes. A valid key on a @Public() route now attaches the owning user (so @CurrentUser() works), matching JWT optional-auth. A missing/invalid key is tolerated; protected routes stay strict — an invalid key is denied with no fallback. See the API Keys guide.