Version Packages - #49
Merged
Merged
Conversation
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
@ingram-tech/nk-auth@0.15.0
Minor Changes
907585f: Make
nextpreservation composable, and loud when it is missing.Until now
?next=only survived a sign-in redirect if a site adopted bothcreateAuthMiddlewareandrequireUserverbatim: the middleware was the onlything that set the
x-nk-auth-pathheader, the guard's sign-in URL builder wasprivate, and a site that deviated from either lost
nextwith no error. Every"sign in to see this page" landed on the default page instead.
@ingram-tech/nk-auth/middlewareexports the two halves of the middleware ontheir own:
withAuthPathHeader(request, requestHeaders)sets the header froma custom proxy in one line (the same
requestHeadersshape as nk-i18n'slocaleProxy), andclearStaleSession(request, config)is the stale-cookiehandshake.
createAuthMiddleware's middleware also accepts{ requestHeaders }so a site can forward its own headers through it.createAuthHelpersexportssignInTarget(), the sign-in URL withnextandstalecomputed, so a site's own guard wrapper doesredirect(await signInTarget())instead of re-deriving it.nextParam(defaultnext) andisSafeNext(default theinternal-path validator), for a site with an existing param name or a
trusted-origin allow-list.
signInTarget()warns once when the header is absent,naming the two ways to wire it.
@ingram-tech/nk-dev@0.14.0
Minor Changes
nk doctorwarns when a site bindscreateAuthHelpersbut nothing sets thex-nk-auth-pathheader (neithercreateAuthMiddlewarenorwithAuthPathHeader): the guards'?next=is lost silently in that shape.guide.mdnames the composable nk-auth middleware pieces.