5.75.0
(feat): Add a new smart-casing-digit-word-boundary option to generators.yml. When enabled
alongside smart-casing, snake_case names preserve the word boundary after a digit run
(e.g., ConversationsV2Configuration → conversations_v2_configuration,
Int32Value → int32_value). The option defaults to false, restoring the
pre-5.70.3 behavior where the digit run stays fused to the following word
(conversations_v2configuration).
5.74.3
(chore): Move internal docs-publish logs that expose implementation details (docs ledger deploy mode, per-locale segment counts, FDR publish, ledger deployment IDs) from INFO to DEBUG level, so they only appear when debug logging is enabled.
5.74.2
(fix): Fix discriminated union variants that reference a nested oneOf/anyOf being
wrapped in a spurious “value” property. The OpenAPI importer now merges
the nested oneOf variants into a single object with optional fields,
preserving the correct wire format.
5.74.1
(fix): Bump @fern-api/generator-cli to 0.9.49. Self-hosted push/PR commits created with a
personal access token (ghp_/github_pat_) are now attributed to fern-api[bot]
as author and committer instead of the PAT owner.
5.74.0
(feat): Add support for webhook signature schemes that transmit a hash of the raw request
body separately rather than signing the body directly (for example, Twilio’s
bodySHA256 query parameter for JSON bodies). HMAC webhook signatures now accept a
body-hash-binding with an algorithm, encoding, and a location (currently a
query-parameter on the notification URL). The field is threaded through the Fern
Definition schema, the IR, and the OpenAPI importer, and validation requires
notification-url in payload-format.components when a query-parameter binding is
configured.
5.73.0
(internal): Forward the GitHub Actions OIDC request variables (ACTIONS_ID_TOKEN_REQUEST_URL and
ACTIONS_ID_TOKEN_REQUEST_TOKEN) into the local-generation Docker container, so tooling running
inside a generator (e.g. npm publish to an npm trusted publisher) can mint a short-lived OIDC
token instead of relying on a long-lived registry token. No effect outside GitHub Actions OIDC jobs.
The OIDC request token is redacted from the logged container command line.