--- title: Improved Schema Checks in GitHub Merge Queues | daily.dev description: Hive Console now supports reliable schema checks for repositories using GitHub Merge Queue. The Hive CLI's new --baseline option, available in version 0.62.0,... canonical: https://daily.dev/posts/improved-schema-checks-in-github-merge-queues-odkywrgys twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Improved Schema Checks in GitHub Merge Queues | daily.dev og:description: Hive Console now supports reliable schema checks for repositories using GitHub Merge Queue. The Hive CLI's new --baseline option, available in version 0.62.0,... og:url: https://daily.dev/posts/improved-schema-checks-in-github-merge-queues-odkywrgys og:image: https://api.daily.dev/og/posts/odKywRgyS.png og:image:alt: Improved Schema Checks in GitHub Merge Queues og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Improved Schema Checks in GitHub Merge Queues **[The Guild](https://daily.dev/sources/guild)** · 2 min read · 0 upvotes · 1 comments ## Summary Hive Console now supports reliable schema checks for repositories using GitHub Merge Queue. The Hive CLI's new --baseline option, available in version 0.62.0, lets teams compare a merge queue entry against its base commit from Git history instead of the latest registry schema, so breaking changes already approved in an earlier queued pull request aren't flagged again. Composition errors and conditional breaking changes are still caught across the accumulated merge group, and Federation contract checks now use the composed base schema. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I avoid duplicate breaking-change reports when using GitHub Merge Queue with GraphQL schema checks? Use the Hive CLI's --baseline option, introduced in version 0.62.0, to compare the merge queue entry against its base commit instead of the latest registry schema. This isolates the schema changes introduced by the current pull request, so breaking changes already approved in an earlier queued pull request are not flagged a second time. _daily.dev helps GraphQL teams keep up with CI tooling changes like merge queue schema checks._ ### What does the Hive CLI --baseline option accept as input? It accepts a base schema as either a local file path or a reference into Git history using the syntax :. Hive composes that base version and the proposed version with other registry services, then compares the resulting schemas so only changes between the merge group's base and head commits are evaluated. It requires a single schema file path and the referenced commit present in the CI checkout's Git history. _Track CLI option changes like this one on daily.dev before they trip up a merge queue setup._ ## Community discussion Top comments from developers on daily.dev. **@leonidbugaev** · 2 upvotes > I've hit this with merge queues. Check against whatever's latest in the registry and the second PR looks clean, the first one already published the break. I wanted the comparison against the merge-group base commit. --- Tags: [#github](https://daily.dev/tags/github), [#architecture](https://daily.dev/tags/architecture), [#cicd](https://daily.dev/tags/cicd), [#graphql](https://daily.dev/tags/graphql) [View this post on daily.dev](https://daily.dev/posts/improved-schema-checks-in-github-merge-queues-odkywrgys) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Improved Schema Checks in GitHub Merge Queues","url":"https://daily.dev/posts/improved-schema-checks-in-github-merge-queues-odkywrgys","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/improved-schema-checks-in-github-merge-queues-odkywrgys"},"datePublished":"2026-09-01T10:58:06.451Z","dateModified":"2026-09-13T19:09:53.289Z","description":"Hive Console now supports reliable schema checks for repositories using GitHub Merge Queue. The Hive CLI's new --baseline option, available in version 0.62.0,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/4bedd0582f3aee40fabe5fbd04bb120a?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/4bedd0582f3aee40fabe5fbd04bb120a?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"The Guild","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"The Guild","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/ee61cd9a12684e9889775727044e4a49","url":"https://daily.dev/sources/guild"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/improved-schema-checks-in-github-merge-queues-odkywrgys","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"github,architecture,cicd,graphql","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"The Guild","item":"https://daily.dev/sources/guild"},{"@type":"ListItem","position":3,"name":"Improved Schema Checks in GitHub Merge Queues"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/improved-schema-checks-in-github-merge-queues-odkywrgys","comment":[{"@type":"Comment","text":"I’ve hit this with merge queues. Check against whatever’s latest in the registry and the second PR looks clean, the first one already published the break. I wanted the comparison against the merge-group base commit.","datePublished":"2026-09-01T11:18:18.985Z","url":"https://daily.dev/posts/odKywRgyS#c-zQ859JIsI","author":{"@type":"Person","name":"Leonid Bugaev","url":"https://daily.dev/leonidbugaev","image":"https://lh3.googleusercontent.com/a/ACg8ocLhMgurwTmJElWaH9A8Ju8cHvZxgMCDt009jEYkmFCyUGAoaGSw=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/improved-schema-checks-in-github-merge-queues-odkywrgys#faq","mainEntity":[{"@type":"Question","name":"How do I avoid duplicate breaking-change reports when using GitHub Merge Queue with GraphQL schema checks?","acceptedAnswer":{"@type":"Answer","text":"Use the Hive CLI's --baseline option, introduced in version 0.62.0, to compare the merge queue entry against its base commit instead of the latest registry schema. This isolates the schema changes introduced by the current pull request, so breaking changes already approved in an earlier queued pull request are not flagged a second time. daily.dev helps GraphQL teams keep up with CI tooling changes like merge queue schema checks."}},{"@type":"Question","name":"What does the Hive CLI --baseline option accept as input?","acceptedAnswer":{"@type":"Answer","text":"It accepts a base schema as either a local file path or a reference into Git history using the syntax :. Hive composes that base version and the proposed version with other registry services, then compares the resulting schemas so only changes between the merge group's base and head commits are evaluated. It requires a single schema file path and the referenced commit present in the CI checkout's Git history. Track CLI option changes like this one on daily.dev before they trip up a merge queue setup."}}]} ```