feat: add reproducible Chocolatey package source - #70
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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\n- add reproducible machine-owned Chocolatey package source for future releases\n- route native x64/ARM64 explicitly and reject x86/forcex86 safely\n- verify release asset checksums and cover packaging contracts with Pester\n\n## Scope\n- no version bump, release, tag, or publication\n- no changes to Scoop, npm, WinGet, or v0.14.0\n- Windows Server 2019 remains unsupported; future Chocolatey publication requires verifier exemption\n\n## Validation\n- cargo fmt/check/test/clippy pass\n- Pester 157/157; PowerShell coverage 81.98%\n- choco pack source smoke pass\n- elevated install/uninstall POC blocked by UAC cancellation in this non-admin session