chore: version packages#5
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
7 times, most recently
from
April 11, 2026 00:34
1d9da19 to
d027069
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
April 20, 2026 23:16
9777e37 to
9efcccc
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 18, 2026 22:54
9efcccc to
cb472bb
Compare
Member
|
No longer using changesets/changesets to version |
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@interline-io/tlv2-auth@0.2.0
Minor Changes
#4
691139dThanks @irees! - Add synchronous Nitro plugin for Cloudflare Workers compatibility with @auth0/auth0-nuxt. Add opt-inautoAppBaseUrlmodule option that derives auth0appBaseUrlfrom the requestHostheader for branch/preview deploys. Note:autoAppBaseUrltrusts thex-forwarded-protoandHostheaders — only enable on platforms where these are set by a trusted edge proxy.#8
03e262fThanks @irees! - Removenuxt-csurffrom the module. CSRF protection is now the responsibility of consuming applications.The API proxy is no longer registered by default. Set
proxy: truein module options to enable it.The proxy now respects
requireLogin— unauthenticated requests return 401 when enabled.Fix SSRF vulnerability in proxy target resolution where scheme-relative URLs (e.g.
//attacker.com) could redirect requests to arbitrary hosts.#9
8f5f298Thanks @irees! - Always install auth0-nuxt at build time with placeholder defaults so Auth0 credentials are purely a runtime concern. WhenNUXT_AUTH0_*env vars are absent, auth gracefully no-ops and users are treated as anonymous.Breaking: Module option
proxyrenamed toproxyEnabled.Fix redirect loop when
returnTotargets an auth route.Ephemeral session secret generation is now dev-only; production requires
NUXT_AUTH0_SESSION_SECRETto be set explicitly.#7
603855bThanks @irees! - AddauthPrefixandproxyPrefixmodule options to configure the URL prefixes for auth routes and the API proxy. Defaults remain/authand/proxy. CSRF protection on the proxy is now enforced on all HTTP methods (including GET) via Nitro route rules.Patch Changes
#12
45205ffThanks @irees! - Add opt-in trace logging gated behindTL_LOG=trace. Uses a guard pattern (if (traceEnabled)) to avoid argument evaluation when tracing is off. Covers the auth0 middleware, session endpoint, proxy handler, and SSR auth header injection.Enable the proxy in the playground and add a proxy test UI for exercising the full auth flow locally.
#13
a45d5f7Thanks @irees! - Registeraudiencein the auth0 runtimeConfig schema so consuming apps can setNUXT_AUTH0_AUDIENCEwithout a type error duringnuxt build.Replace
addImportsDirwith explicitaddImportsto eliminate "Duplicated imports" warnings.#15
392dbb0Thanks @drewda! - Docs: clarify thatNUXT_AUTH0_CLIENT_IDmust be set at build time even when real credentials are supplied only at runtime (e.g. Cloudflare Pages dashboard). Otherwise, placeholders get baked in and runtime env vars are silently ignored.#23
831c2a6Thanks @irees! - Fix authenticated proxy requests being rejected by the backend withtoken is malformed: token contains an invalid number of segments(HTTP 401).The
auth.serverplugin injectedAuthorization/apikeyonto backend requests withHeaders.append(). Because the server-side proxy already attaches those headers, the request — which flows through the patchedglobalThis.fetch— had them appended a second time, comma-joining intoAuthorization: "Bearer <tok>, Bearer <tok>". Switched both injection paths ($fetchonRequestand theglobalThis.fetchoverride) toHeaders.set(), which is idempotent.Also stop forwarding the browser session cookie to the backend API in the proxy: it's irrelevant to the API and the encrypted auth0-nuxt session cookie duplicates the JWT.