🌿 ✨ [Scheduled] Upgrade Fern CLI

[fern-api]

Upgrading from 0.46.20 to 0.50.12 - Changelog

0.50.12

• fix: Increase undici timeouts to make sure that fern generate --docs completes.

0.50.11

• fix: The CLI now supports a --log-level trace option to filter out noise from the
  debug log level.

0.50.10

• fix: An addition to the broken link checker to further reduce false positives.

0.50.9

• fix: The Fern CLI no longer logs the full API request when finishing docs registration,
  reducing unnecessary log output.

0.50.8

• fix: An additional fix to the OpenRPC parser for respecting tags when
  organizing methods in the API Reference.

22 additional updates, see more




0.50.7

fix: The OpenRPC parser now respects method names as well as tags for
organization the navigation.

0.50.6

fix: The broken link checker is updated to reduce false positives.

0.50.5

fix: The Fern CLI is updated to create the organization if it doesn't exist when fern token is called.

0.50.4

internal: The docs.yml now supports a separate configurtation for feature-flags which allows Fern to render
pieces of content depending on whether or not certain feature flags are enabled for particular user.

This feature is in alpha stage; please contact [email protected] to learn more!

navigation:
  - page: Page 1
    feature-flag: my-feature-flag-a # single boolean flag
  - page: Page 2
    feature: # multiple boolean flags
      - flag: my-feature-flag-a
      - flag: my-feature-flag-b
  - section: Section Title
    viewers: role-a
    feature-flag: # configurable match
      flag: my-feature-flag-a
      fallback-value: "ga"
      match: "beta"
    layout: []

0.50.3

internal: Fixes an issue where optional, nullable properties resulted in a double optional in the
IRv55 -> IRv54 migration.

0.50.2

fix: The docs now includes alpha support for parsing openrpc specs. To leverage this feature,
simply define an API section in your docs.yml and point at an openrpc spec.

navigation: 
  - api: API Reference
    openrpc: <path to openrpc file>

0.50.1

fix: Fixes an issue where nullable schemas were not coerced into optional values.

fix: Fixes an issue where fern check would fail for optional, nullable properties.

0.50.0

internal: The CLI is capable of migrating the latest TypeScript generator to IRv55.

0.49.1

fix: The OpenAPI v2 parser now supports x-fern-global-headers and fixes an issue with generating webhook content.

0.49.0

feat: The OpenAPI importer now supports respecting nullable properties in schemas. When enabled, nullable properties will
be preserved in the gnerated SDK. By default (without this setting), nullable properties are treated as optional.
To enable this, configure the setting in your generators.yml:

api:
 specs:
   - openapi: ./path/to/openapi.yml
     settings:
       respect-nullable-schemas: true

0.48.1

fix: The Mintlify docs importer now correctly generates the proper display-name key in the docs.yml file.

0.48.0

feat: Adds support for nullable types in the Fern definition, such as the following:

types:
  User:
    properties:
      name: string
      email: nullable<string>

0.47.6

feat: The IR now pulls in additional request properties from the OAuth getToken endpoint to support custom OAuth schemas.

0.47.5

feat: Fixes an issue with broken link checking in the OpenAPI v2 parser.

0.47.4

feat: Allows for creating nullable types and pass formats on strings using the OpenAPI v2 parser.

0.47.3

feat: Add the JSON schema to the generators.yml file for validation and autocomplete.

0.47.2

feat: The CLI now supports checking for broken links in your docs. You will see warnings in fern check if your docs link to any
page that can't be resolved, and the --strict-broken-links option will cause the command to fail (exit with a non-zero exit code) if
any broken links are found. You can also run the new command fern docs broken-links to only check for broken links (ignoring
other possible errors), with the --strict option to cause the command to fail if any broken links are found.

0.47.1

feat: Fixes a bug where the OpenAPI parser stopped respecting the =unions: v1 setting in your generators.yml which configures the parser to generate more
idiomatic discriminated unions.

api:
  specs:
    - openapi: ./path/to/openapi.yml
      settings:
        unions: v1

0.47.0

feat: The CLI now supports publishing docs using the improved OpenAPI v2 parser. You can set openapi-parser-v2: true
in your docs.yml to use the new parser.

0.46.23

feat: The CLI now validates that method and group name overrides in OpenAPI settings are not duplicated.

0.46.22

feat: Support configuration of Google Analytics and Google Tag Manager in API Docs.

0.46.21

fix: The CLI now supports the prefer-undiscriminated-unions-with-literals setting in OpenAPI settings.