Re-enable the Fern Check workflow - #677
Merged
Merged
Conversation
Move fern_check.yml back into .github/workflows so pull requests and pushes to main validate the specs again. Pin actions/checkout to a commit, drop persisted git credentials, declare read-only permissions, cap the job at 15 minutes, and cancel superseded pull request runs. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
The v4.3.0 pin declares Node.js 20, which GitHub-hosted runners now force onto Node.js 24 with a deprecation warning on every run. v6.1.0 declares Node.js 24 and still honours the pnpm version pinned in package.json. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
pkubicki
approved these changes
Sep 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
No spec validation has run on pull requests since the workflows were disabled in June, and spec errors have reached main more than once because Fern Check was never a required status. It needs no secrets, so it can run safely on pull requests from any branch, including forks.
How?
Brings the workflow back from the disabled folder, pins both actions to a commit, and gives the job read-only access with no persisted git credentials. Once this lands, a follow-up settings change makes the check a required status on main.
Generated with Claude Code