Upcoming Release Changes (#6463)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Author: theguild-bot

.changeset/hungry-files-sneeze.md

@@ -1,5 +1,27 @@
 # hive
 
+## 5.1.0
+
+### Minor Changes
+
+- [#6449](https://github.com/graphql-hive/console/pull/6449)
+  [`0504530`](https://github.com/graphql-hive/console/commit/05045306b789e97ec39cbd2c8ee2b4f1b721dc9e)
+  Thanks [@n1ru4l](https://github.com/n1ru4l)! - Modify GraphQL fields used by CLI to accept an
+  optional specified target that is used for identifying the affected target instead of resolving
+  the target from the access token.
+
+### Patch Changes
+
+- [#6472](https://github.com/graphql-hive/console/pull/6472)
+  [`4d3d6fc`](https://github.com/graphql-hive/console/commit/4d3d6fcdc2d7f65e6366fd76a058c3f687c4da4c)
+  Thanks [@n1ru4l](https://github.com/n1ru4l)! - Improve the usage reporting endpoint error
+  responses to include all the errors for invalid JSON bodies.
+
+- [#6455](https://github.com/graphql-hive/console/pull/6455)
+  [`6924a1a`](https://github.com/graphql-hive/console/commit/6924a1abf91c1c663d752949031e0a5c4078392a)
+  Thanks [@jasonkuhrt](https://github.com/jasonkuhrt)! - A minor defect in Laboratory has been fixed
+  that previously caused the application to crash when local storage was in a particular state.
+
 ## 5.0.0
 
 ### Major Changes

.changeset/small-readers-melt.md

@@ -1,6 +1,6 @@
 {
   "name": "hive",
-  "version": "5.0.0",
+  "version": "5.1.0",
   "private": true,
   "scripts": {
     "generate": "tsx generate.ts",

.changeset/tall-lies-raise.md

@@ -1,5 +1,39 @@
 # @graphql-hive/cli
 
+## 0.47.0
+
+### Minor Changes
+
+- [#6449](https://github.com/graphql-hive/console/pull/6449)
+  [`0504530`](https://github.com/graphql-hive/console/commit/05045306b789e97ec39cbd2c8ee2b4f1b721dc9e)
+  Thanks [@n1ru4l](https://github.com/n1ru4l)! - Add `--target` flag for commands `app:create`,
+  `app:publish`, `operations:check`, `schema:check`, `schema:delete`, `schema:fetch`,
+  `schema:publish` and `dev`.
+
+  The `--target` flag can be used to specify the target on which the operation should be performed.
+  Either a slug or ID of the target can be provided.
+
+  A provided slug must follow the format `$organizationSlug/$projectSlug/$targetSlug` (e.g.
+  `the-guild/graphql-hive/staging`).
+
+  **Example using target slug**
+
+  ```bash
+  hive schema:publish --target the-guild/graphql-hive/production ./my-schema.graphql
+  ```
+
+  A target id, must be a valid target UUID.
+
+  **Example using target id**
+
+  ```bash
+  hive schema:publish --target a0f4c605-6541-4350-8cfe-b31f21a4bf80 ./my-schema.graphql
+  ```
+
+  **Note:** We encourage starting to use the `--target` flag today. In the future the flag will
+  become mandatory as we are moving to a more flexible approach of access tokens that can be granted
+  access to multiple targets.
+
 ## 0.46.1
 
 ### Patch Changes

.changeset/three-stingrays-do.md

@@ -1,6 +1,6 @@
 {
   "name": "@graphql-hive/cli",
-  "version": "0.46.1",
+  "version": "0.47.0",
   "description": "A CLI util to manage and control your GraphQL Hive",
   "repository": {
     "type": "git",

.changeset/wet-eggs-rule.md

@@ -1,5 +1,17 @@
 # @graphql-hive/yoga
 
+## 0.39.4
+
+### Patch Changes
+
+- [#6473](https://github.com/graphql-hive/console/pull/6473)
+  [`bba81de`](https://github.com/graphql-hive/console/commit/bba81def2962ddcda5dcec389f70dca1356f2815)
+  Thanks [@n1ru4l](https://github.com/n1ru4l)! - Correctly extract client information when using the
+  response cache plugin.
+
+  The client information was not reported for GraphQL responses served from the response cache
+  plugin.
+
 ## 0.39.3
 
 ### Patch Changes