Changelog

3.12.0

(feat): Add support for publishing to npmjs.org using OIDC from GitHub Actions.

To use OIDC for publishing to npmjs.org, you need to follow two steps:

1. Follow the instructions in “Step 1: Add a trusted publisher on npmjs.com”.

2. Set the output.token field to OIDC in generators.yml to enable this feature:

   1
   # In generators.yml
   2
   groups:
   3
     ts-sdk:
   4
       generators:
   5
         - name: fernapi/fern-typescript-sdk
   6
           output:
   7
             location: npm
   8
             package-name: your-package-name
   9
             token: OIDC # previously this would be set to something like ${NPM_TOKEN}
   10
           ...

   This will take care of “Step 2: Configure your CI/CD workflow”.

For local generation, you’ll need Fern CLI version 0.94.0 or later.

(feat): Update GitHub Actions setup-node action to v4 in the generated CI workflow.

3.11.1

(fix): Generate streaming response section in README.md for streaming response endpoints.

3.11.0

(feat): Add linter and formatter configuration options to configure code linters and formatters for the generated SDK.

• linter:
  • biome: Use Biome as the code linter. This is the default.
  • none: Do not include a code linter.
• formatter:
  • biome: Use Biome as the code formatter. This is the default.
  • prettier: Use Prettier as the code formatter.

For consistency, the package.json scripts will always include the following scripts:

• lint: Run the configured linter.
• lint:fix: Run the configured linter with auto-fix.
• format: Run the configured formatter.
• format:check: Run the configured formatter in check mode.
• check: Run both the linter and formatter in check mode.
• check:fix: Run both the linter and formatter with auto-fix. When the linter is set to none, lint and lint:fix scripts will echo a message indicating that no linter is configured.