chore: remove the data-layer packages (orm/schema/adapters)#74
Merged
Conversation
These were a frozen spike copy from PR #65 for the planned graduation to @gemstack/*. That graduation is cancelled (#66): the universal engines stay @universal-orm, outside the GemStack umbrella. vike-data / @universal-orm is the single source of truth, so the gemstack copies only add fork and accidental-publish risk. They are private/unpublished with no dependents, so removal breaks nothing.
This was referenced Jun 28, 2026
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.
Removes the four data-layer packages from this repo:
@gemstack/orm,@gemstack/orm-memory,@gemstack/orm-drizzle,@gemstack/schema.Why
These were a frozen spike copy (PR #65) staged for the planned graduation to
@gemstack/*. That graduation is cancelled per #66: the universal engines are infrastructure (not user-facing), so they stay@universal-orm, outside the GemStack umbrella. GemStack remains the user-facing brand (AI family + MCP).vike-data /
@universal-ormis the single source of truth for these engines, so the gemstack copies only add fork and accidental-publish risk with no upside.Safe to remove
private: trueand unpublished.pnpm install --frozen-lockfilepasses.Related
@universal-orm