fix(registry): bump pinned @constructive-io/data and command-palette ranges - #33
Merged
Merged
Conversation
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
Review complete. No issues found — approved ✅. This PR updates the registry compiler and the three emitted registry.json files to a consistent, contract-enforced version bump. All changed files were reviewed across correctness, API/data, domain, holistic, and sweep passes; no defects were found.
Reviewed commit: d8875e5 |
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.
Summary
mainis red: the registry smoke install fails withERR_PNPM_NO_MATCHING_VERSION No matching version found for @constructive-io/data@^0.7.0. The registry items pin the exact published range of the workspace packages they depend on, and yesterday's publish moved@constructive-io/datato0.8.0and@constructive-io/command-paletteto0.6.0, so the pins no longer match what the smoke registry serves.Bumps the two pins to the published versions and regenerates the source registries (
pnpm build:registry, which also enforces the pin viaassertRegistryDistributionContract):Verified locally with
pnpm --filter @constructive-io/registry smoke:install(clean package-free install passes).Link to Devin session: https://app.devin.ai/sessions/027937d092794c92a31c6ee49c513f59
Requested by: @pyramation