Repository navigation
Repair ORM release fixture locks and execute PostgreSQL count authorization - #104
Merged
Merged
Conversation
This was referenced Oct 1, 2026
This was referenced Oct 1, 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.
#103 advances ORM/macros to 0.35.2 but leaves the standalone fixture lockfiles at 0.35.1; their required
--lockedbuilds fail before compilation. Regenerate those five lockfiles without dependency upgrades (also reconcile the already-merged AI package version in the coexistence fixture).Execute the existing eight repository count/exists authorization regressions on individually owned disposable PostgreSQL as well as memory SQLite. Cleanup checks the exact container identity; an unavailable database fails rather than silently skipping. Include that execution in the release workflow's PostgreSQL lane. No runtime source, public API, SDL, package version or database schema behavior changes; these are release validation repairs for the unpublished 0.35.2 set.
Validation:
cargo test --locked -p graphql-orm --no-default-features --features sqlite --test repository_counts: 8 passed, none ignored.--features postgres -- --test-threads=1: 8 passed on disposable PostgreSQL, none ignored.cargo test --locked ... --features sqlite: six executed tests passed; two generated illustrative doctests ignored.policy_projectionsandcomplete_eventsexamples execute successfully (225 event groups); warnings-denied PostgreSQL core/macros Rustdoc and MSSQL library Clippy pass. MSSQL live execution is not claimed.Release coordination: .2 remains immutable. The old .3 run at 73ef09d failed the current-main guard after #103 merged and published nothing. A new .3 run will use the exact reviewed main commit after this follow-up, retaining GitHub's human protected-environment gate. A (#97) and B–D remain outside this release; remaining GEMA queries/views stay open in #91.
Documentation impact
Explanation: changelog and runnable SQLite/PostgreSQL count validation commands.