5.105.1
(fix): Materialize Git LFS assets when building docs versions from Git refs.
5.105.0
(feat): Support GraphQL schemas whose SDL is split across multiple files. GraphQL specs that share a
namespace — including specs that declare no name, which all belong to the same unnamed
group — are now compiled into a single schema, so federated subgraphs (which reference types
owned by sibling files and extend the same Query/Mutation types) can be documented as one
API. Federation composition directives such as @key, @external and @link are ignored
(through federation v2.9, so @cost, @listSize, @context and @fromContext too),
members marked @inaccessible are omitted along with everything that references them (matching
the client-facing API schema produced by composition), and @deprecated is now surfaced on
operations, fields, arguments and enum values. Merging is first-wins throughout — types,
members, directive definitions, root operation types and operation examples — and every
discarded declaration is reported, naming the files involved.
5.104.1
(fix): Retry Swagger 2.0 to OpenAPI 3 conversion in lenient mode when strict conversion fails, instead
of dropping the spec. Specs using constructs such as type: ['null', string] now load, with a
warning naming the strict-mode error.
5.104.0
(feat): Add the opt-in respect-per-spec-base-path setting to apply each OpenAPI document’s plain x-fern-base-path
to that document’s own endpoints instead of collapsing to one API-wide base path.