Releases: graphql-hive/console
hive@11.0.3
Patch Changes
-
#7993
730771f
Thanks @n1ru4l! - Address vulnerability
GHSA-72c6-fx6q-fr5w. -
#7988
d7e7025
Thanks @n1ru4l! - Address vulnerability
GHSA-247c-9743-5963. -
#7961
40fd27d
Thanks @n1ru4l! - Update
nodemailerto address vulnerability
GHSA-vvjj-xcjg-gr5g. -
#7993
730771f
Thanks @n1ru4l! - Address vulnerability
GHSA-v9ww-2j6r-98q6. -
#7976
ed9ab34
Thanks @n1ru4l! - address vulnerability
GHSA-r4q5-vmmm-2653 -
#7967
9708f71
Thanks @n1ru4l! - Fix schema contract composition applying
@inaccessibleon the federation typesContextArgumentandFieldValueon the supergraph SDL.This mitigates the following error in apollo-router upon processing the supergraph:
could not create router: Api error(s): The supergraph schema failed to produce a valid API schema: The following errors occurred: - Core feature type `join__ContextArgument` cannot use @inaccessible. - Core feature type `join__FieldValue` cannot use @inaccessible. -
#7993
730771f
Thanks @n1ru4l! - Address vulnerability
GHSA-xq3m-2v4x-88gg. -
#7978
9c6989c
Thanks @jdolle! - Add schema linting support for type extensions -
#7993
730771f
Thanks @n1ru4l! - Address vulnerability
CVE-2026-6414. -
#7988
d7e7025
Thanks @n1ru4l! - Address vulnerability
GHSA-39q2-94rc-95cp. -
#7980
c46b2f2
Thanks @n1ru4l! - Address vulnerability
GHSA-fvcv-3m26-pcqx. -
#7993
730771f
Thanks @n1ru4l! - Address vulnerability
CVE-2026-6410. -
#7961
40fd27d
Thanks @n1ru4l! - Update
opentelemetry-goto address vulnerability
CVE-2026-39883.
@graphql-hive/render-laboratory@0.1.5
Patch Changes
- #7989
863f920
Thanks @mskorokhodov! - Enhanced behavior when no collection
exists and the user attempts to save an operation, along with the ability to edit the collection
name. - Updated dependencies
[863f920]:- @graphql-hive/laboratory@0.1.5
@graphql-hive/render-laboratory@0.1.4
Patch Changes
-
#7963
4a8bd4f
Thanks @mskorokhodov! - Implemented functionality that allows
to have multiple queries in same operation while working only with focused one (run button, query
builder) -
#7892
fab4b03
Thanks @mskorokhodov! - Hive Laboratory renders Hive Router
query plan if included in response extensions -
Updated dependencies
[4a8bd4f,
fab4b03]:- @graphql-hive/laboratory@0.1.4
@graphql-hive/laboratory@0.1.5
Patch Changes
- #7989
863f920
Thanks @mskorokhodov! - Enhanced behavior when no collection
exists and the user attempts to save an operation, along with the ability to edit the collection
name.
@graphql-hive/laboratory@0.1.4
Patch Changes
-
#7963
4a8bd4f
Thanks @mskorokhodov! - Implemented functionality that allows
to have multiple queries in same operation while working only with focused one (run button, query
builder) -
#7892
fab4b03
Thanks @mskorokhodov! - Hive Laboratory renders Hive Router
query plan if included in response extensions
hive@11.0.2
Patch Changes
-
#7940
742f50c
Thanks @jdolle! - Fix lint policy block title color; add policy link
to lines and rule id tooltip -
#7936
96bd390
Thanks @jdolle! - Do not cache edge types in graphql eslint. This
fixes an issue where edge types were cached between runs and only the cached edge types would be
referenced for subsequent runs
@graphql-hive/render-laboratory@0.1.3
Patch Changes
- #7888
574a5d8
Thanks @mskorokhodov! - If schema introspection isn't provided
as property to Laboratory, lab will start interval to fetch schema every second. - Updated dependencies
[574a5d8]:- @graphql-hive/laboratory@0.1.3
@graphql-hive/laboratory@0.1.3
Patch Changes
- #7888
574a5d8
Thanks @mskorokhodov! - If schema introspection isn't provided
as property to Laboratory, lab will start interval to fetch schema every second.
hive@11.0.1
hive@11.0.0
Major Changes
-
#7837
c00ea50
Thanks @n1ru4l! - Improved performance when looking up affected app
deployments for breaking change detection.BREAKING CHANGE
This release introduces a breaking change because it depends on a manual database migration
introduced in10.1.0.If you use the app deployments feature for conditional breaking change detection, you should:
- Upgrade to
10.1.0 - Perform the manual database migration steps described in that version
- Then upgrade to this release
Alternative upgrade path
If you want to avoid performing the manual database migration:
- Upgrade to
10.1.0 - Wait until all app deployments created before the rollout of
10.1.0are retired - Then upgrade to this release
- Upgrade to