Repository navigation
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
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 release form can otherwise pair a stale prepared version with a different module: the failed Bookmarks 1.3.0 dispatch selected a 2.2.0 snapshot while Gallery already contains 3.0.1. Add reviewed Gallery version references and eight-module publishing preparation, keeping unprepared/reconciliation candidates blocked.
References pin live source/release SHAs and six downloaded Gallery archive/runtime hash sets. Version checks reject registered/unlisted versions, normalize a zero fourth segment, and allow only reviewed per-module major numbers. The form no longer suggests a universal 1.3.0; mismatch errors identify the selected module, prepared version and references. Bookmarks 3.0.1 contains a newer cmdlets-based implementation: do not relabel the 2.2 monolith. Its publication/GitHub release creation is explicitly blocked until reconciliation. 7Zip 2.0.0 reflects removal of automatic runtime downloads and the requirement for an installed native runtime; compatibility changes are documented. No source or package versions are rewritten by this PR.
Owner-authorized new publishing routes: FolderEncoder -> Stadub; Shell-Functions and the distinct MiniModules.Uninstall name -> MiniModules. Legacy Uninstall is untouched; CI keeps Uninstall as its component identity. Source PRs #46–48 and source-plus-out release candidates #49–51 remain open at their recorded SHAs. Root standalone packaging selects only its runtime, manifest, module README and existing license. Preserve FolderEncoder MIT, Shell/Uninstall BSD, Base64String WTFPL, the original five routes, dry-run default, master-only environment, account-scoped keys and verified-only issue completion. All three new routes retain review blocks.
Validation: eleven offline PowerShell suites, three Node contract suites and actionlint 1.7.12 pass. Immutable candidate run 43236263855 passed all 12 jobs (Windows PowerShell 5.1 and Windows/Linux/macOS pwsh per package). All 12 downloaded artifacts match exact candidate name/version/SHA and committed payload hashes: 96 Pester + 72 structure assertions, zero failures/skips. Those source/candidate contents remain unchanged. Encoder/archive roundtrips and actual registry/msiexec removal remain outside packaging validation.
Review head:
bc1137bc41d79551b9870be69f2159e4daa7ac0d. Exact-head push run 43251627418, attempt 2 and PR run 43251638942, attempt 3 now both pass all 24 jobs (48/48). The owner renewed the CI failure report on 2026-11-13; a targeted same-commit retry acquired a macOS runner and passed Currency-Conv. Its downloaded source identity matches maintained SHA 7306a3b and its NUnit report has 15 tests, zero failures/errors/skips. Earlier attempts remain visible with GitHub hosted ARM64 runner-acquisition/capacity annotations and zero executed steps for the cancelled jobs. No code/platform changes or fail-open rules were needed. All visible PR checks pass; source/candidate PRs remain open. Evidence, readiness and owner rollout requirements are in docs/releases/gallery-version-reference.md and docs/releases/new-module-packaging.md.No live upload, GitHub release/tag creation, issue closure, merge, master/release integration, secret or environment change. Reference numbers are plans, not prepared-release claims. Owner approval, exact source/package preparation and required key scopes remain deployment prerequisites; #22/#29 stay open.