release: prepare gooblin 1.3.2 installer safety patch - #65
Merged
Conversation
21 tasks
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.
What
git diff --checkandnpm pack --dry-runCI gatesWhy
PR #58 made the GitHub-source installer non-destructive, but npm 1.3.1 still contains recursive replacement/removal. This release candidate prepares the immutable patch version needed to finish #57 without claiming it is already published.
Gates
npm run validategit diff --checknpm pack --dry-runCI evidence: Validate run 29234721595 for exact head
4fabc738fdeda7cc700614c57290908bd1449080. All Node lanes passed; Node 24 passed the whitespace and pack gates. The final pack output wasgooblin-1.3.2.tgz, 324.5 kB packed / 437.8 kB unpacked, 88 files, shasumc358ef8bd5bcd6d0651f4c0b333a0d3a76e428b9.Known payload limitation: examples referenced by the README are not installed by the current copy-only installer; ownership-aware payload completion remains in #49 and is not claimed by this safety release.
Part of #57.