Fix corrupt retry.js symlink introduced by #185#189
Merged
Conversation
PR #185 accidentally added a trailing newline to the retry.js symlink target, causing GitHub Actions to fail with a "could not find file" error when resolving the path at runtime. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
reakaleek
approved these changes
Jun 16, 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.
Summary
docs-builder/preview/cleanup/scripts/retry.jssymlink target../../../../scripts/retry.js\ninstead of../../../../scripts/retry.js, causing GitHub Actions to fail when resolving the file path at runtimeae6d37e)Fixes the error reported in https://elastic.slack.com/archives/C02762N267P/p1781601076237139:
Test plan
🤖 Generated with Claude Code