Repository navigation
test(windows): symlink privilege is mandatory only on GitHub Actions - #866
Merged
Merged
Conversation
…s, not any CI=true runner The local job runner exports CI=true. On the P520 (non-admin, no Developer Mode) verify-signed-bundle then failed with WINDOWS_CI_SYMLINK_PRIVILEGE_REQUIRED (node_verify:test job 763edd47). Audited GitHub Actions Windows CI still throws; a workstation now records the assertion as NOT EXECUTED via t.diagnostic. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AjjQnxAvtbQCFYE3y8yrq8
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.
P520 full suite on main 38ff4ab (job 763edd47) failed: local runner sets CI=true so the symlink fixture helper demanded privilege. Now only GITHUB_ACTIONS=true makes it mandatory (audited CI unchanged); on a workstation the assertion is reported NOT EXECUTED via diagnostic, never as pass. No production code change.
Not claimed: those symlink assertions executed on the P520.
Generated by Claude Code