Fix CI lockfile error by removing @objectstack/spec dependency #121
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.
Fixes the CI pipeline failure caused by a mismatch between
pnpm-lock.yamlandpackages/types/package.json.Problem
The CI was failing with:
The lockfile expected
@objectstack/specto be a workspace package, butpackage.jsonspecified it as an external npm dependency (^0.1.1). Additionally, the npm package@objectstack/spec@0.1.1doesn't export theUIComponentinterface that was being imported.Changes Made
@objectstack/specfrompackages/types/package.jsonpackages/types/src/base.tsto its original definition whereBaseSchemadefinestypeandidproperties directly instead of extendingUIComponentpnpm-lock.yamlto reflect the removed dependencyTesting
@object-ui/typespackage builds successfullyThe changes restore the types package to its original state, removing the incorrect dependency on an external package that was causing the CI failure.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.