Repository navigation
fix: prepare catalog with frozen upstream dependencies - #10
Merged
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
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.
Catalog preparation fails because the upstream registry now uses pnpm and its lockfile, while the preparer resolves dependencies with npm. Use pinned pnpm 11.28.5 / Node 24.21.0, frozen upstream production dependencies and the real upstream sorter, requiring unchanged manifest and lock bytes.
The workflow checks out reviewed tooling separately from the clean, immutable release tag. It verifies the actual published archive, checksums and package qualification against that release source before preparing the human-submission patch. Published tags, assets and the native qualification gates remain unchanged.
Validation: complete existing build/test/package gate passes, including 76 Python tests. Four additional regression checks cover real tagged Git source, immutable lock inputs, runtime drift and actual release archive/receipt rejection. A live upstream checkout passed frozen installation, sorting and applying the three-file patch to a clean clone. Independent parent review passed. No upstream PR or catalog listing is created by this workflow.