Skip to content

ci: pin fern-api to 5.26.4 and drop global CLI install steps#335

Merged
Devon-White merged 1 commit into
mainfrom
nko/ci-install-fern-preview
May 20, 2026
Merged

ci: pin fern-api to 5.26.4 and drop global CLI install steps#335
Devon-White merged 1 commit into
mainfrom
nko/ci-install-fern-preview

Conversation

@Devon-White
Copy link
Copy Markdown
Collaborator

Summary

  • Pins fern-api devDependency to 5.26.4, matching the CLI version declared in fern/fern.config.json (was ^5.23.3).
  • Removes the npm install -g fern-api steps added in ci: install fern-api globally in workflows that invoke fern #334 from check.yml and publish-docs.yml. With fern-api as a pinned workspace devDependency, yarn install puts fern in node_modules/.bin, so every workflow that calls yarn fern-check, yarn build, npx fern generate, etc. resolves the binary automatically.
  • Refreshes yarn.lock to the new resolved version.

This also fixes the preview-docs.yml failure (/bin/sh: 1: fern: not found) that #334 missed — once branches merge this, the preview workflow's yarn build step will find fern via the lockfile.

Test plan

  • fern-check workflow passes on this PR (uses yarn fern-check only)
  • preview-docs workflow generates a preview URL (uses yarn build which calls fern generate)
  • After merge, downstream PR branches that pull in main get a working preview

Bump fern-api devDependency from ^5.23.3 to 5.26.4 to match the CLI
version declared in fern/fern.config.json, and remove the
`npm install -g fern-api` steps added in #334. With fern-api as a
pinned workspace devDependency, yarn install puts fern in
node_modules/.bin so every workflow that calls yarn fern-check,
yarn build, etc. resolves the binary without a global install.
@Devon-White Devon-White merged commit 36388d0 into main May 20, 2026
2 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant