Repository navigation
Version Packages - #212
Merged
Merged
Version Packages#212
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
@seamless-auth/fastify@0.11.1
Patch Changes
88ae99c: Detect Fastify proxy trust from its behaviour, not its configuration (docs(fastify): an explicit trustProxy hop count no longer forwards the client IP #208).
The adapter refused to forward a client-controlled address when
trustProxywastrue, by readingtrustProxyfrominitialConfig. Fastify 5 does not expose it there, so the check never fired, and withtrustProxy: truea caller could choose the client IP the auth API rate limits and audits against. The adapter now asks Fastify's ownrequest.ipabout a request from documentation addresses (RFC 5737). When the application trusts every address it drops the client IP and warns, as intended.The README recommended a hop count, which Fastify 5.12.1 and later ignore: they trust no proxy, so
request.ipis the proxy and every user shares one address on the auth API. The README now recommends the proxy's address or subnet, orresolveClientIp, and the adapter warns once when requests carryX-Forwarded-Forthat nothing trusts.