fix(generator-cli): bump @fern-api/replay to 0.18.0#16444
Merged
Conversation
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
tstanmay13
approved these changes
Jun 10, 2026
Co-Authored-By: tanmay.singh <tstanmay13@gmail.com>
4f912f5 to
04d2c72
Compare
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.
Description
Bumps
@fern-api/replayfrom 0.16.2 to 0.18.0 in generator-cli, pulling in the merged replay fixes from fern-replay#96 and fern-replay#97:.fernignore-protected files before materializing patch content (commits touching only protected paths skipgit format-patchentirely; mixed commits use a scopedgit diff parent sha -- files)docs/) now match — previously such entries were silently ignoredwrite EPIPEcrash inGitClient.execWithInputfixed (git's exit code now decides the outcome)This is what caused auth0/node-auth0 regenerations (13k typedoc files in
docs/, listed in.fernignoreasdocs/) to churn for 25+ minutes and then crash.Changes Made
packages/generator-cli/package.json:@fern-api/replay0.16.2 → 0.18.0 (+ lockfile)packages/generator-cli/versions.yml: 0.9.38 entry (rebased past 0.9.37 which landed on main in fix(generator-cli): allow AutoVersionStep to run without replay (non-replay mode) #16452; triggers generator-cli npm publish)packages/cli/cli/changes/unreleased/bump-replay-0.18.0.yml: CLI changelog entry (CLI bundles generator-cli for the local self-hosted GitHub path)pnpm-workspace.yamlintentionally left at 0.9.35 — bumping it before 0.9.38 exists on npm breakspnpm install(follow-up after publish, same as the 0.9.36/0.9.37 releases)Testing
pipeline runagainst a real auth0/node-auth0 clone with fresh generated output. Before (0.16.2): ~4 min CPU churn then unhandledwrite EPIPEcrash. After (0.18.0): pipeline succeeded in 12 seconds, 9 customer patches detected/applied, 0 conflicts, 13kdocs/files correctly excluded.Link to Devin session: https://app.devin.ai/sessions/ebae597e588c4fecb8f3802f05617c2a
Requested by: @tstanmay13