Consolidate graphql-orm companion crates into one workspace - #10
Merged
Conversation
…estore sink - Optional orm feature: OrmBackupAdapter bridges GraphqlOrmBackupRuntime to the GraphqlOrmBackupAdapter contract (schema snapshots, consistent full export, empty-target detection, full restore, replace-existing clearing) - OrmBackupObjectIndex derives a BackupObjectIndex from one object metadata table plus the application's primary BlobStore - BlobStoreRestoreObjectSink rehydrates a blob store at original storage keys - delete_snapshot removes one snapshot under the writer lock with object GC - BackupError::Database carries adapter failures with operation context - Verification and object writes iterate owned pairs so futures stay Send - Reference sibling crates by git URL so the crate resolves from GitHub Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Hosts can exclude or redact columns whose database types the graphql-orm export cannot round-trip yet (for example PostGIS geometry) without editing entity metadata, which would change migration-planning inputs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Release graphql-orm-backup 0.3.1 with exact reviewed graphql-orm and graphql-orm-storage revisions.
- Add `agql-auth` and `graphql-orm-macros` skill guidance - Add the `rust-skills` rule set and supporting docs
Merge the reviewed graphql-orm 0.15 integration and bump graphql-orm-backup from 0.4.0 to 0.5.0.
Merge the reviewed graphql-orm 0.16 and agql-auth 0.12 dependency alignment, including the graphql-orm-backup 0.6.0 version bump.
Dastari
marked this pull request as ready for review
July 29, 2026 04:47
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.
What changed
graphql-orm-storage,graphql-orm-backup, andgraphql-orm-aihistories beneathcrates/using history-preserving pathrewrites.
agql-authexternal and pinned to its exact reviewed revision.graphql-ormfeature gates.release-policy/SemVer gates, and consumer migration guidance.
graphql-orm-backupfrom 0.6.0 to 0.7.0 andgraphql-orm-aifrom0.57.0 to 0.58.0 for the pre-1.0 dependency identity boundary. Storage
remains 0.6.0, ORM/macros remain 0.16.0, and AI schema remains 0.51.0.
Why
The companion crates depend on one another and on
graphql-orm. Separaterepositories forced agents and consumers to coordinate exact Git revisions and
could create duplicate public type universes. The workspace makes cross-crate
changes atomic while preserving independently selectable crates and an acyclic
dependency graph.
Consumer impact
Git consumers should move the selected packages to
https://github.com/Dastari/graphql-orm.git, pin every selected package to thesame full revision, remove old internal repository patches, and regenerate
Cargo.lock. No database or AI schema migration is required for the repositorymove.
Validation
before integration.
review, warnings-denied Clippy and Rustdoc, package/default tests, AI
provider/local-harness and PascalCase tests, alternate SQLite/PostgreSQL/
MSSQL/storage feature lanes, AI test-owned PostgreSQL parity, and the managed
real-Samba lifecycle/reconnect suite.
cargo-semver-checksagainst the imported backup 0.6.0 and AI 0.57.0baselines.
The original repositories remain intact, clean, and synchronized;
archival/redirect work should happen only after this candidate is accepted.