|
1 | 1 | # hive
|
2 | 2 |
|
| 3 | +## 5.0.0 |
| 4 | + |
| 5 | +### Major Changes |
| 6 | + |
| 7 | +- [#6231](https://github.com/graphql-hive/console/pull/6231) |
| 8 | + [`b7e4052`](https://github.com/graphql-hive/console/commit/b7e4052ecfd8f70fefe39c27886619a24faa7526) |
| 9 | + Thanks [@n1ru4l](https://github.com/n1ru4l)! - Introduce new permission system for organization |
| 10 | + member roles. |
| 11 | + |
| 12 | + The existing scopes assigned to organization member users are now replaced with permissions. Using |
| 13 | + the permissions allows more granular access control to features in Hive. |
| 14 | + |
| 15 | + This introduces the following breaking changes: |
| 16 | + |
| 17 | + - Organization members with the default `Viewer` role, will experience downgraded permissions. |
| 18 | + They will no longer be able to create targets or projects. |
| 19 | + - Organization member roles permissions for inviting, removing or assigning roles have been |
| 20 | + revoked. A organization admin will have to re-apply the permissions to the desired member roles. |
| 21 | + - Organization members with permissions for managing invites, removing members, assigning roles or |
| 22 | + modifying roles are no longer restrained in granting more rights to other users. Please be aware |
| 23 | + when granting these permissions to a user role. We recommend only assigning these to member |
| 24 | + roles that are considered "Admin" user roles. |
| 25 | + |
| 26 | + A future update will introduce resource based access control (based on project, target, service or |
| 27 | + app deployments) for organization members. |
| 28 | + |
| 29 | +### Minor Changes |
| 30 | + |
| 31 | +- [#6378](https://github.com/graphql-hive/console/pull/6378) |
| 32 | + [`f14daa8`](https://github.com/graphql-hive/console/commit/f14daa89760149d6b1eb45d5351d73c4376b7418) |
| 33 | + Thanks [@jasonkuhrt](https://github.com/jasonkuhrt)! - You can now set HTTP headers in your |
| 34 | + [Laboratory Preflight Script](https://the-guild.dev/graphql/hive/docs/dashboard/laboratory/preflight-scripts). |
| 35 | + Every time you run a request from Laboratory, your preflight headers, if any, will be merged into |
| 36 | + the request before it is sent. |
| 37 | + |
| 38 | + You achieve this by interacting with the |
| 39 | + [`Headers`](https://developer.mozilla.org/docs/web/api/headers) instance newly available at |
| 40 | + `lab.request.headers`. For example, this script would would add a `foo` header with the value |
| 41 | + `bar` to every Laboratory request. |
| 42 | + |
| 43 | + ```ts |
| 44 | + lab.request.headers.set('foo', 'bar') |
| 45 | + ``` |
| 46 | + |
| 47 | + A few notes about how headers are merged: |
| 48 | + |
| 49 | + 1. Unlike static headers, preflight headers do not receive environment variable substitutions on |
| 50 | + their values. |
| 51 | + 2. Preflight headers take precedence, overwriting any same-named headers already in the Laboratory |
| 52 | + request. |
| 53 | + |
| 54 | + Documentation for this new feature is available at |
| 55 | + https://the-guild.dev/graphql/hive/docs/dashboard/laboratory/preflight-scripts#http-headers. |
| 56 | + |
| 57 | +- [#6123](https://github.com/graphql-hive/console/pull/6123) |
| 58 | + [`abfd1b1`](https://github.com/graphql-hive/console/commit/abfd1b1ea9b6850683f31c152516d9e0d97d94aa) |
| 59 | + Thanks [@Intellicode](https://github.com/Intellicode)! - encode postgres variables and introduce |
| 60 | + optional password |
| 61 | + |
| 62 | +- [#6412](https://github.com/graphql-hive/console/pull/6412) |
| 63 | + [`f352bba`](https://github.com/graphql-hive/console/commit/f352bbac977902120527fbea2afb0b0b7dd253fb) |
| 64 | + Thanks [@Intellicode](https://github.com/Intellicode)! - Added a new environment variable |
| 65 | + `PROMETHEUS_METRICS_PORT` to control the promethus port of the policy service. The default value |
| 66 | + is `10254` (no action needed). |
| 67 | + |
| 68 | +### Patch Changes |
| 69 | + |
| 70 | +- [#6398](https://github.com/graphql-hive/console/pull/6398) |
| 71 | + [`0e4be14`](https://github.com/graphql-hive/console/commit/0e4be14256937f492efcb4a7dc97b59918274a2a) |
| 72 | + Thanks [@kamilkisiela](https://github.com/kamilkisiela)! - Remove the db leftovers related to |
| 73 | + activities (no longer a thing) |
| 74 | + |
| 75 | +- [#6433](https://github.com/graphql-hive/console/pull/6433) |
| 76 | + [`a902d8b`](https://github.com/graphql-hive/console/commit/a902d8bb974c0ea707a17ff3d921a6cf13972ead) |
| 77 | + Thanks [@kamilkisiela](https://github.com/kamilkisiela)! - Improves validation for operation |
| 78 | + durations and error totals. Prevents processing of invalid usage report data. |
| 79 | + |
| 80 | +- [#6374](https://github.com/graphql-hive/console/pull/6374) |
| 81 | + [`393ece7`](https://github.com/graphql-hive/console/commit/393ece7eab93ed0b7873e4428f78a5c27cf764fa) |
| 82 | + Thanks [@kamilkisiela](https://github.com/kamilkisiela)! - Adjust the Kafka message size |
| 83 | + estimation only when Kafka gives back `MESSAGE_TOO_LARGE` error |
| 84 | + |
| 85 | +- [#6358](https://github.com/graphql-hive/console/pull/6358) |
| 86 | + [`ab06518`](https://github.com/graphql-hive/console/commit/ab065182d89e6d7e4c90469d0bcaadacfa4c3b1e) |
| 87 | + Thanks [@jdolle](https://github.com/jdolle)! - Use sum instead of max of top request counts for |
| 88 | + breaking changes calculation |
| 89 | + |
3 | 90 | ## 4.1.0
|
4 | 91 |
|
5 | 92 | ### Minor Changes
|
|
0 commit comments