fix: align circuit-json override to unblock npm packaging - #4630
Open
l4time wants to merge 1 commit into
Open
Conversation
Contributor
|
This PR has been automatically marked as stale because it has had no recent activity. It will be closed if no further activity occurs. |
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.
The August 27 release created a tag, then npm rejected the
circuit-jsonoverride withEOVERRIDE. Its specification must exactly match the direct dependency. This changes the override to^0.0.479and updates the lockfile without changing any resolved packages.npm pack --dry-run --ignore-scripts --jsonfails before this change and passes afterward, including both built entrypoints. Frozen installation, the full build, typecheck, and formatting also pass. Independently reviewed; prepared with AI assistance.This addresses the packaging failure behind #4628 and is separate from #4629. Existing orphan tags and the stale release version still need maintainer recovery. No registry publication was attempted.