[email protected]

Minor Changes

• #6449
  0504530
  Thanks @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
  4d3d6fc
  Thanks @n1ru4l! - Improve the usage reporting endpoint error
  responses to include all the errors for invalid JSON bodies.

• #6455
  6924a1a
  Thanks @jasonkuhrt! - A minor defect in Laboratory has been fixed
  that previously caused the application to crash when local storage was in a particular state.

@graphql-hive/[email protected]

Patch Changes

• #6473
  bba81de
  Thanks @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.

@graphql-hive/[email protected]

Minor Changes

• #6449
  0504530
  Thanks @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

  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

  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.

[email protected]

Major Changes

• #6231
  b7e4052
  Thanks @n1ru4l! - New permission system for organization member
  roles.

  The existing scopes assigned to organization members have been replaced with a permissions-based
  system, enabling more granular access control and role-based access control (RBAC) in Hive.

  Breaking Changes

  • Viewer Role Adjustments – Members with the default Viewer role can no longer create targets
    or projects.
  • Restricted Role Management – Permissions for inviting, removing, and assigning roles have
    been revoked. An admin must manually reassign these permissions where needed.
  • Expanded Role Assignment Capabilities – Members with permissions to manage invites, remove
    members, or modify roles can now grant additional permissions without restrictions. Caution is
    advised when assigning these rights, as they should be reserved for "Admin" roles.

  These changes enhance security and provide greater flexibility in managing user permissions across
  organizations.

Minor Changes

• #6378
  f14daa8
  Thanks @jasonkuhrt! - You can now set HTTP headers in your
  Laboratory Preflight Script.
  Every time you run a request from Laboratory, your preflight headers, if any, will be merged into
  the request before it is sent.

  You achieve this by interacting with the
  Headers instance newly available at
  lab.request.headers. For example, this script would would add a foo header with the value
  bar to every Laboratory request.

  lab.request.headers.set('foo', 'bar')

  A few notes about how headers are merged:

  1. Unlike static headers, preflight headers do not receive environment variable substitutions on
     their values.
  2. Preflight headers take precedence, overwriting any same-named headers already in the Laboratory
     request.

  Documentation for this new feature is available at
  https://the-guild.dev/graphql/hive/docs/dashboard/laboratory/preflight-scripts#http-headers.

• #6123
  abfd1b1
  Thanks @Intellicode! - encode postgres variables and introduce
  optional password

• #6412
  f352bba
  Thanks @Intellicode! - Added a new environment variable
  PROMETHEUS_METRICS_PORT to control the promethus port of the policy service. The default value
  is 10254 (no action needed).

Patch Changes

• #6398
  0e4be14
  Thanks @kamilkisiela! - Remove the db leftovers related to
  activities (no longer a thing)

• #6433
  a902d8b
  Thanks @kamilkisiela! - Improves validation for operation
  durations and error totals. Prevents processing of invalid usage report data.

• #6374
  393ece7
  Thanks @kamilkisiela! - Adjust the Kafka message size
  estimation only when Kafka gives back MESSAGE_TOO_LARGE error

• #6358
  ab06518
  Thanks @jdolle! - Use sum instead of max of top request counts for
  breaking changes calculation

[email protected]

Minor Changes

• #6400
  d2a4387
  Thanks @kamilkisiela! - Display logs from the Preflight Script
  in Laboratory

• #6348
  e754700
  Thanks @kamilkisiela! - Adds ability to select a default role
  for new OIDC users

• #6351
  ba20748
  Thanks @dotansimha! - Added a new environment variable
  OPENTELEMETRY_TRACE_USAGE_REQUESTS for rate-limit and tokens services.

  Self-hosters who wish to report telemetry information for usage service, can opt-in and set
  OPENTELEMETRY_TRACE_USAGE_REQUESTS=1 to these services. This will skip sampling and will always
  trace requests originating from the usage service.

• #6388
  a8ff443
  Thanks @kamilkisiela! - Add multi-column sort to Insights >
  Operations table

• #6389
  781b140
  Thanks @kamilkisiela! - Show Impact metric in the Operations
  list on the Insights page. Impact equals to the total time spent on this operation in the selected
  period in seconds. It helps assess which operations contribute the most to overall latency.

  Impact = Requests * avg/1000
  

• #6393
  84fd770
  Thanks @kamilkisiela! - Add type definitions of global.lab to
  Preflight Script editor

• #6351
  ba20748
  Thanks @dotansimha! - Added OpenTelemetry traces to Usage service
  using a new OPENTELEMETRY_COLLECTOR_ENDPOINT env var.

  This option is disabled by default for self-hosting, you can opt-in by setting
  OPENTELEMETRY_COLLECTOR_ENDPOINT.

Patch Changes

• #6386
  d19229f
  Thanks @kamilkisiela! - Remove the code leftovers related to
  activities (no longer a thing)

• #6380
  40213fb
  Thanks @kamilkisiela! - Update
  @theguild/federation-composition to
  v0.14.3

• #6399
  607192e
  Thanks @kamilkisiela! - Disable "select organization" dropdown
  for OIDC accounts

[email protected]

Patch Changes

• #6383
  ec356a7
  Thanks @kamilkisiela! - Collect custom scalars from arguments
  and input object fields

@graphql-hive/[email protected]

Patch Changes

• #6383
  ec356a7
  Thanks @kamilkisiela! - Collect custom scalars from arguments
  and input object fields

• Updated dependencies
  [ec356a7]:

  • @graphql-hive/[email protected]

@graphql-hive/[email protected]

Patch Changes

• #6383
  ec356a7
  Thanks @kamilkisiela! - Collect custom scalars from arguments
  and input object fields

• Updated dependencies
  [ec356a7]:

  • @graphql-hive/[email protected]

@graphql-hive/[email protected]

Patch Changes

• #6383
  ec356a7
  Thanks @kamilkisiela! - Collect custom scalars from arguments
  and input object fields

@graphql-hive/[email protected]

Patch Changes

• #6380
  40213fb
  Thanks @kamilkisiela! - Update
  @theguild/federation-composition to
  v0.14.3

• Updated dependencies
  [ec356a7]:

  • @graphql-hive/[email protected]