-
Couldn't load subscription status.
- Fork 3.4k
chore: remove ssh-keyscan as it shouldn't be necessary
#32817
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
+2
−3
Conversation
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
06e4d7f to
3f1aee5
Compare
ssh-keyscan as it shouldn't be necessary
ssh-keyscan as it shouldn't be necessaryssh-keyscan as it shouldn't be necessary
3f1aee5 to
b36e218
Compare
ryanthemanuel
approved these changes
Oct 27, 2025
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.
Additional details
Currently, our windows builds are failing with this error:
due to this issue PowerShell/Win32-OpenSSH#2140
The reason it was introduced in the first place to our CI is we run the
stabletag forwindows-server-2022-gui, which just recently bumped from2024.04.1to2024.12.1, which includes a newer version Open SSH for Windows.To mitigate this, I think we can just remove the
ssh-keyscanmethod from our CI job as the checkout job should have updated keys. My guess is we used this to patch around some previous checkout issues and I would like to try and remove it first and see if any issues creep up in the future as opposed to possibility maintaining something we likely no longer need.Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation?type definitions?Note
Removes the ssh-keyscan step and switches branch filters/conditions to
chore/fix_buildsin CircleCI configs.update_known_hostsstep fromnode_modules_install(dropsssh-keyscanusage).setup_should_persist_artifactsbranch condition to usechore/fix_buildsinstead ofryanm/fix/rename-exclude-from-ai.workflows/@main.ymlto includechore/fix_buildsand remove the old branch.Written by Cursor Bugbot for commit b36e218. This will update automatically on new commits. Configure here.