Run the v4 toolchain in CI, and reset Fern Replay - #210
Merged
Conversation
Two things kept the v4 generation red, neither of them SDK code. CI ran bare yarn. The v4 TypeScript generator pins pnpm in package.json and emits a vitest config, so yarn 1.x rejected the manifest and the job failed during install, before compiling anything. Corepack activates the pinned pnpm instead, and the test and build steps follow it. Fern Replay records each generation's tree hash in .fern/replay.lock and re-applies everything that has diverged since as a customization, independently of .fernignore. The lock here is v3's history, so v3's wrapper and its frozen package.json still read as customizations. Removing it lets v4 start with no recorded customizations, and it stops being frozen because the file is Fern's own state.
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
1 participant
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.
Two things kept the v4 generation red, neither of them SDK code.
CI ran bare
yarn. The v4 TypeScript generator pins"packageManager": "pnpm@10.33.0"and emits a vitest config. yarn 1.x rejects that manifest outright:The job died during install, before compiling a line. Corepack activates the pinned pnpm instead. (The generated manifest is correct; the mangled string is yarn's own error formatting.)
Fern Replay was re-applying v3.
.fern/replay.lockrecords each generation's tree hash and re-applies everything that has diverged since as a customization, independently of.fernignore. The lock here is v3's history, so v3's wrapper and its frozenpackage.jsonstill read as customizations. Removing it lets v4 start clean; it also stops being frozen, since it is Fern's own state.CI on this PR fails, and cannot pass in isolation
This is a sequencing constraint, not a defect. The workflow and the manifest have to change together:
package.json(yarn@1.22.22) andyarn.lock, because Fern owns those files now and has not regenerated them yetpnpm install --frozen-lockfiletherefore has nopnpm-lock.yamlto read, and install fails.githubis deliberately frozen — the SDK Release audit fails closed otherwise — so the generation PR cannot carry this workflow change itselfWhat I can verify: the current generated head (#209) contains both
package.jsonwithpnpm@10.33.0and a 59 KBpnpm-lock.yaml. So the moment a generation lands on top of this, install resolves and the job runs.The sibling PRs are different: zep-python#338 and zep-go#103 are self-consistent and should go green on their own.