Repository navigation
Enable hosted Defender before gated release publication - #20
Merged
Merged
Conversation
debug23win
marked this pull request as ready for review
October 5, 2026 23:04
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.
The v3.8.4 release built all Revit packages and the installer but correctly stopped because GitHub's Windows image had Defender inactive. Activate Defender only on the disposable github-hosted Windows runner, remove its two whole-drive exclusions, update intelligence, and retain the mandatory original payload/archive/installer scan gate. Developer-machine invocation is rejected; no bypass/fallback publication is added.
Validation: CI #116 passed commit 6459d0e. Isolated PowerShell checks cover the local guard, enabling-only preferences, removal of only runner drive exclusions, and bounded fail-closed behavior. Actual Defender activation and a compiled-DLL scan on the GitHub-hosted runner both passed. Existing unit, WPF, MCP, subscription CLI and installer checks also passed. Safety reports now capture protection state on failure.
Prepare v3.8.5 with all verified modeling changes from the unpublished v3.8.4 build; keep existing tags unchanged. README and release notes explain the failed publication and new security step.