Hive announces summer update and new schema registry model

Hive has released its summer update, introducing several new features and a modernized schema registry model. The update includes persistent schema checks displayed on the Hive Target page, with automatic linking to GitHub check runs for integrated projects. Users can now manually approve schema checks to update GitHub status and view schema diffs, policy errors, and supergraphs.

On the Explorer page, Hive now identifies which clients use specific schema coordinates and provides subgraph information for GraphQL Federation projects. The Operations view has been enhanced with client-based filtering, and the Laboratory now allows users to save and organize GraphQL Operations into shared collections. Additionally, Hive now supports Google Cloud Storage as a backend for self-hosted instances.

Alongside these features, Hive is transitioning to a new schema registry model designed for an optimized workflow. This modern model includes superior defaults, follows industry best practices, and introduces a previously unavailable delete feature for schemas. Access to the legacy registry model is expected to be discontinued in several months, and users are encouraged to migrate via their project settings.