Repository navigation
docs: cooldown force-only Governance, NVM4313 list, unblock Deploy - #99
Merged
Merged
Conversation
Cooldown exists on Community and Certified. Only HKLM policy force needs Governance. NVM4313 also refuses ProgramData and drive roots.
Point firewall at /guide/firewall and registry at the /cfg/registry slug so the production build can ship.
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
C:\), matching the installer.npm run buildcurrently fails becausefeatures/malicious-package-blockerlinks to/features/firewalland/cfg/enterprise/registry. Point those at/guide/firewalland/cfg/registryso Deploy can pick up PR docs: SIEM Event 120, InstallRoot, npx cooldown #95 (/guide/siem,/troubleshooting/error-codes).Test plan
gh workflow run Deploy --ref main