Change pricing Pro max to 5B #7717
No breaking changes
Found 102 changes
Safe: 102
Safe changes
- Description for argument includeAll on field AccessToken.resolvedResourcePermissionGroups changed from If true, include all permissions and resource groups in the result, even those not currently granted. to If true, include all permissions and resource groups in the result,
even those not currently granted. - Input field ActiveAppDeploymentsFilter.lastUsedBefore description changed from Returns deployments that were last used before the given timestamp. Useful for identifying stale or inactive deployments that have been used at least once but not recently. to Returns deployments that were last used before the given timestamp.
Useful for identifying stale or inactive deployments that have been used
at least once but not recently. - Input field ActiveAppDeploymentsFilter.name description changed from Filter by app deployment name. Case-insensitive partial match. Applied with AND semantics to narrow down results. to Filter by app deployment name. Case-insensitive partial match.
Applied with AND semantics to narrow down results. - Input field ActiveAppDeploymentsFilter.neverUsedAndCreatedBefore description changed from Returns deployments that have never been used and were created before the given timestamp. Useful for identifying old, unused deployments that may be candidates for cleanup. to Returns deployments that have never been used and were created before
the given timestamp. Useful for identifying old, unused deployments
that may be candidates for cleanup. - Description Filter options for querying active app deployments. The date filters (lastUsedBefore, neverUsedAndCreatedBefore) use OR semantics: a deployment is included if it matches either date condition. If no date filters are provided, all active deployments are returned. on type ActiveAppDeploymentsFilter has changed to Filter options for querying active app deployments.
The date filters (lastUsedBefore, neverUsedAndCreatedBefore) use OR semantics:
a deployment is included if it matches either date condition.
If no date filters are provided, all active deployments are returned. - Description Input for updating app deployment protection configuration. Fields not provided (omitted) will retain the previous value. on type AppDeploymentProtectionConfigurationInput has changed to Input for updating app deployment protection configuration.
Fields not provided (omitted) will retain the previous value. - Input field ApproveFailedSchemaCheckInput.comment description changed from Optional comment visible in the schema check. Give a reason why the schema check was approved. to Optional comment visible in the schema check.
Give a reason why the schema check was approved. - Field ConditionalBreakingChangeConfiguration.breakingChangeFormula description changed from Determines which formula is used to determine if a change is considered breaking or not. Only one formula can be used at a time. to Determines which formula is used to determine if a change is considered breaking
or not. Only one formula can be used at a time. - Field ConditionalBreakingChangeConfiguration.percentage description changed from If TargetValidationSettings.breakingChangeFormula is PERCENTAGE, then this is the percent of the total operations over the TargetValidationSettings.period required for a change to be considered breaking. to If TargetValidationSettings.breakingChangeFormula is PERCENTAGE, then this
is the percent of the total operations over the TargetValidationSettings.period
required for a change to be considered breaking. - Field ConditionalBreakingChangeConfiguration.requestCount description changed from If TargetValidationSettings.breakingChangeFormula is REQUEST_COUNT, then this is the total number of operations over the TargetValidationSettings.period required for a change to be considered breaking. to If TargetValidationSettings.breakingChangeFormula is REQUEST_COUNT, then this
is the total number of operations over the TargetValidationSettings.period
required for a change to be considered breaking. - Input field ConditionalBreakingChangeConfigurationInput.period description changed from The period in days. Operations of the last x days will be used for the conditional breaking change detection. The maximum value depends on the organizations data retention limits. to The period in days. Operations of the last x days will be used for the conditional breaking change detection.
The maximum value depends on the organizations data retention limits. - Input field CreateOrganizationAccessTokenInput.permissions description changed from List of permissions assigned to the access token. Available permissions can be retrieved via the *Organization.availableOrganizationAccessTokenPermissionGroups* field. to List of permissions assigned to the access token.
Available permissions can be retrieved via the
*Organization.availableOrganizationAccessTokenPermissionGroups* field. - Input field CreateOrganizationAccessTokenInput.resources description changed from Resources on which the permissions should be granted (e.g., project, target, service, or app deployments). Permissions are inherited by sub-resources. to Resources on which the permissions should be granted (e.g., project, target, service, or app deployments).
Permissions are inherited by sub-resources. - Field CreateOrganizationAccessTokenResultOk.privateAccessKey description changed from The private access key corresponding to the new token. This value is only returned once at creation time and cannot be retrieved later. to The private access key corresponding to the new token.
This value is only returned once at creation time and cannot be retrieved later. - Input field CreatePersonalAccessTokenInput.permissions description changed from List of permissions assigned to the access token. A list of available permissions can be retrieved via the *Member.availablePersonalAccessTokenPermissionGroups* field. to List of permissions assigned to the access token.
A list of available permissions can be retrieved via the
*Member.availablePersonalAccessTokenPermissionGroups* field. - Input field CreatePersonalAccessTokenInput.resources description changed from Resources on which the permissions should be granted (e.g., project, target, service, or app deployments). Permissions are inherited by sub-resources. to Resources on which the permissions should be granted (e.g., project, target, service, or app deployments).
Permissions are inherited by sub-resources. - Field CreatePersonalAccessTokenResultOk.privateAccessKey description changed from The private access key corresponding to the new token. This value is only returned once at creation time and cannot be retrieved later. to The private access key corresponding to the new token.
This value is only returned once at creation time and cannot be retrieved later. - Input field CreateProjectAccessTokenInput.permissions description changed from List of permissions assigned to the access token. Available permissions can be retrieved via the *Project.availableProjectAccessTokenPermissionGroups* field. to List of permissions assigned to the access token.
Available permissions can be retrieved via the
*Project.availableProjectAccessTokenPermissionGroups* field. - Input field CreateProjectAccessTokenInput.resources description changed from Resources on which the permissions should be granted (e.g., target, service, or app deployments). Permissions are inherited by sub-resources. to Resources on which the permissions should be granted (e.g., target, service, or app deployments).
Permissions are inherited by sub-resources. - Description Top-level result object for creating a project access token. @OneOf on type CreateProjectAccessTokenResult has changed to **Top-level result object for creating a project access token.
@OneOf**
- Field CreateProjectAccessTokenResultOk.privateAccessKey description changed from The private access key corresponding to the new token. This value is only returned once at creation time and cannot be retrieved later. to The private access key corresponding to the new token.
This value is only returned once at creation time and cannot be retrieved later. - Input field CreateSchemaProposalInput.isDraft description changed from The default initial stage is OPEN. Set this to true to create this as proposal as a DRAFT instead. to The default initial stage is OPEN. Set this to true to create this as proposal
as a DRAFT instead. - Description **A date-time string at UTC, such as *2007-12-03T10:15:30Z*, is compliant with the date-time format outlined in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar. This scalar is a description of an exact instant on the timeline such as the instant that a user account was created. This scalar ignores leap seconds (thereby assuming that a minute constitutes 59 seconds). In this respect, it diverges from the RFC 3339 profile. Where an RFC 3339 compliant date-time string has a time-zone other than UTC, it is shifted to UTC. For example, the date-time string *2016-01-01T14:10:20+01:00* is shifted to *2016-01-01T13:10:20Z*. ** on type DateTime has changed to **A date-time string at UTC, such as *2007-12-03T10:15:30Z*, is compliant with the date-time format outlined
in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.
This scalar is a description of an exact instant on the timeline such as the instant that a user account was created.
This scalar ignores leap seconds (thereby assuming that a minute constitutes 59 seconds). In this respect, it diverges from the RFC 3339 profile.
Where an RFC 3339 compliant date-time string has a time-zone other than UTC, it is shifted to UTC. For example, the date-time string *2016-01-01T14:10:20+01:00* is shifted to *2016-01-01T13:10:20Z*.**
- Description **A date-time string at UTC with nano-second precision, such as *2007-12-03T10:15:30.123456Z*, is compliant with the extended date-time format outlined in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar. The fractional part of the seconds can range up to nanosecond precision. This scalar represents an exact instant on the timeline, such as the precise moment a user account was created, including fractional seconds. This scalar ignores leap seconds (thereby assuming that a minute constitutes 59 seconds). In this respect, it diverges from the RFC 3339 profile. Where an RFC 3339 compliant date-time string has a time-zone other than UTC, it is shifted to UTC. For example, the date-time string *2016-01-01T14:10:20.500+01:00* is shifted to *2016-01-01T13:10:20.500Z*. ** on type DateTime64 has changed to **A date-time string at UTC with nano-second precision, such as *2007-12-03T10:15:30.123456Z*, is compliant with the extended date-time format outlined in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar. The fractional part of the seconds can range up to nanosecond precision.
This scalar represents an exact instant on the timeline, such as the precise moment a user account was created, including fractional seconds.
This scalar ignores leap seconds (thereby assuming that a minute constitutes 59 seconds). In this respect, it diverges from the RFC 3339 profile.
Where an RFC 3339 compliant date-time string has a time-zone other than UTC, it is shifted to UTC. For example, the date-time string *2016-01-01T14:10:20.500+01:00* is shifted to *2016-01-01T13:10:20.500Z*.**
- Field DeprecatedSchemaExplorer.types description changed from The affected types whose fields/values/members are deprecated. The types within the result only contain deprecated fields/values/members, all other entities are excluded, they are not a representation of the full GraphQL schema. to **The affected types whose fields/values/members are deprecated.
The types within the result only contain deprecated fields/values/members, all other entities are excluded,
they are not a representation of the full GraphQL schema.**
- Field FailedSchemaCheck.schemaProposalChanges description changed from If the check is associated with a schema proposal, then this contains an unfiltered list of changes to the SDL. to If the check is associated with a schema proposal, then this contains an unfiltered list of changes
to the SDL. - Field FailedSchemaCheck.schemaVersion description changed from The schema version against this check was performed. Is null if there is no schema version published yet. to The schema version against this check was performed.
Is null if there is no schema version published yet. - Field GraphQLEnumType.supergraphMetadata description changed from Metadata specific to Apollo Federation Projects. Is null if no meta information is available. to Metadata specific to Apollo Federation Projects.
Is null if no meta information is available. - Field GraphQLEnumValue.supergraphMetadata description changed from Metadata specific to Apollo Federation Projects. Is null if no meta information is available. to Metadata specific to Apollo Federation Projects.
Is null if no meta information is available. - Field GraphQLField.supergraphMetadata description changed from Metadata specific to Apollo Federation Projects. Is null if no meta information is available. to Metadata specific to Apollo Federation Projects.
Is null if no meta information is available. - Field GraphQLInputField.supergraphMetadata description changed from Metadata specific to Apollo Federation Projects. Is null if no meta information is available (e.g. this is not an apollo federation project). to Metadata specific to Apollo Federation Projects.
Is null if no meta information is available (e.g. this is not an apollo federation project). - Field GraphQLInputObjectType.supergraphMetadata description changed from Metadata specific to Apollo Federation Projects. Is null if no meta information is available (e.g. this is not an apollo federation project). to Metadata specific to Apollo Federation Projects.
Is null if no meta information is available (e.g. this is not an apollo federation project). - Field GraphQLInterfaceType.supergraphMetadata description changed from Metadata specific to Apollo Federation Projects. Is null if no meta information is available. to Metadata specific to Apollo Federation Projects.
Is null if no meta information is available. - Field GraphQLNamedType.supergraphMetadata description changed from Metadata specific to Apollo Federation Projects. Is null if no meta information is available (e.g. this is not an apollo federation project). to Metadata specific to Apollo Federation Projects.
Is null if no meta information is available (e.g. this is not an apollo federation project). - Field GraphQLObjectType.supergraphMetadata description changed from Metadata specific to Apollo Federation Projects. Is null if no meta information is available (e.g. this is not an apollo federation project). to Metadata specific to Apollo Federation Projects.
Is null if no meta information is available (e.g. this is not an apollo federation project). - Field GraphQLScalarType.supergraphMetadata description changed from Metadata specific to Apollo Federation Projects. Is null if no meta information is available (e.g. this is not an apollo federation project). to Metadata specific to Apollo Federation Projects.
Is null if no meta information is available (e.g. this is not an apollo federation project). - Field GraphQLUnionType.supergraphMetadata description changed from Metadata specific to Apollo Federation Projects. Is null if no meta information is available (e.g. this is not an apollo federation project). to Metadata specific to Apollo Federation Projects.
Is null if no meta information is available (e.g. this is not an apollo federation project). - Field GraphQLUnionTypeMember.supergraphMetadata description changed from Metadata specific to Apollo Federation Projects. Is null if no meta information is available (e.g. this is not an apollo federation project). to Metadata specific to Apollo Federation Projects.
Is null if no meta information is available (e.g. this is not an apollo federation project). - Input field MembersFilter.searchTerm description changed from *Part of a user*s email or username that is used to filter the list of members. to *Part of a user*s email or username that is used to filter the list of
members. - Field Mutation.experimental__updateTargetSchemaComposition description changed from **Overwrites project*s schema composition library. Works only for Federation projects with native composition enabled. This mutation is temporary and will be removed once no longer needed. It*s part of a feature flag called forceLegacyCompositionInTargets. to **Overwrites project*s schema composition library.
Works only for Federation projects with native composition enabled.
This mutation is temporary and will be removed once no longer needed.
It*s part of a feature flag called forceLegacyCompositionInTargets. - Field Mutation.updateTargetDangerousChangeClassification description changed from Update the targets dangerous change classification settings. This allows dangerous changes fail schema checks. to Update the targets dangerous change classification settings.
This allows dangerous changes fail schema checks. - Field Organization.allAccessTokens description changed from Retrieve a list of all access tokens within the organization. This includes organization, project and personal scoped access tokens. to Retrieve a list of all access tokens within the organization.
This includes organization, project and personal scoped access tokens. - Field Organization.isMonthlyOperationsLimitExceeded description changed from Whether or not the monthly operations limit is currently exceeded. For hobby and pro plans, once the limit is exceeded, operation usage data received from the organization will be ignored. Enterprise plans will continue to have their usage data ingested. to Whether or not the monthly operations limit is currently exceeded.
For hobby and pro plans, once the limit is exceeded, operation usage data received from the organization will be ignored.
Enterprise plans will continue to have their usage data ingested. - Field Organization.monthlyOperationsLimit description changed from The monthly limit for number of operations ingested. For hobby and pro plans, once this limit is exceeded, operation usage data received from the organization will be ignored. Enterprise plans will continue to have their usage data ingested. to The monthly limit for number of operations ingested.
For hobby and pro plans, once this limit is exceeded, operation usage data received from the organization will be ignored.
Enterprise plans will continue to have their usage data ingested. - Field Organization.projectForResourceSelector description changed from Retrieves a single project and its associated targets for resource selection by its unique identifier. The result can be filtered by intent to adjust access based on context. to **Retrieves a single project and its associated targets for resource selection
by its unique identifier.
The result can be filtered by intent to adjust access based on context.**
- Field Organization.projectsForResourceSelector description changed from Retrieves a list of all projects and their targets available for resource selection within the organization. The result can be filtered by intent, which defines the context of selection (e.g., administrative vs. user-level operations). to **Retrieves a list of all projects and their targets available for resource selection
within the organization.
The result can be filtered by intent, which defines the context of selection
(e.g., administrative vs. user-level operations).**
- Field Organization.usageEstimation description changed from An approximation of the current monthly operation usage. This is based on how many operations have been successfully ingested by Hive, which is an asynchronous process. to An approximation of the current monthly operation usage. This is based on how many operations have
been successfully ingested by Hive, which is an asynchronous process. - Description for argument includeAll on field OrganizationAccessToken.resolvedResourcePermissionGroups changed from If true, include all permissions and resource groups in the result, even those not currently granted. to If true, include all permissions and resource groups in the result,
even those not currently granted. - Description for argument includeAll on field PersonalAccessToken.resolvedResourcePermissionGroups changed from If true, include all permissions and resource groups in the result, even those not currently granted. to If true, include all permissions and resource groups in the result,
even those not currently granted. - Field Query.whoAmI description changed from Returns information about the currently authorized actor, including permission details. to Returns information about the currently authorized actor,
including permission details. - Field ResolvedResourcePermissionGroup.resolvedResourceIds description changed from The resource identifiers that are currently valid for this permission group. Some examples: - Organization. the-guild - Project the-guild/graphql-hive - Target the-guild/graphql-hive/production - Service the-guild/graphql-hive/production/service/users - App Deployment the-guild/graphql-hive/production/appDeployment/production These ids can also contain wildcards, e.g. the-guild/graphql-hive/, to reference all targets in a project.* to **The resource identifiers that are currently valid for this permission group.
Some examples: - Organization. the-guild
- Project the-guild/graphql-hive
- Target the-guild/graphql-hive/production
- Service the-guild/graphql-hive/production/service/users
- App Deployment the-guild/graphql-hive/production/appDeployment/production
These ids can also contain wildcards, e.g. the-guild/graphql-hive/, to reference all targets in a project.*
- Description Represents a group of permissions associated with a specific resource level (e.g., organization, project, or item). on type ResolvedResourcePermissionGroup has changed to Represents a group of permissions associated with a specific resource level
(e.g., organization, project, or item). - Field RetireAppDeploymentError.protectionDetails description changed from Details about why protection prevented retirement. Only present when retirement was blocked due to protection rules. to Details about why protection prevented retirement.
Only present when retirement was blocked due to protection rules. - Input field RetireAppDeploymentInput.target description changed from *If using an organization access token, then a target must be provided. If using a target*s access token, then this should be null. to *If using an organization access token, then a target must be provided.
If using a target*s access token, then this should be null. - Input field ReviewSchemaProposalInput.coordinate description changed from The schema coordinate being referenced. E.g. Type.field. If null, then this review is for the entire proposal. to The schema coordinate being referenced. E.g. Type.field.
If null, then this review is for the entire proposal. - Input field ReviewSchemaProposalInput.serviceName description changed from The service this review applies to. If the target is a monorepo, then use an empty string. to The service this review applies to. If the target is a monorepo, then use
an empty string. - Field SchemaChange.affectedAppDeployments description changed from List of active app deployments that would be affected by this breaking change. Only populated for breaking changes when app deployments are enabled. to List of active app deployments that would be affected by this breaking change.
Only populated for breaking changes when app deployments are enabled. - Field SchemaChange.approval description changed from Approval metadata for this schema change. This field is populated in case the breaking change was manually approved. to Approval metadata for this schema change.
This field is populated in case the breaking change was manually approved. - Field SchemaChange.severityLevel description changed from The severity level of this schema change. Note: A schema change with the impact *SeverityLevelType.BREAKING* can still be safe based on the usage (*SchemaChange.isSafeBasedOnUsage*). to The severity level of this schema change.
Note: A schema change with the impact *SeverityLevelType.BREAKING* can still be safe based on the usage (*SchemaChange.isSafeBasedOnUsage*). - Field SchemaChange.usageStatistics description changed from Usage statistics about the schema change if it is not safe based on usage. The statistics are determined based on the breaking change configuration. The usage statistics are only available for breaking changes and only represent a snapshot of the usage data at the time of the schema check/schema publish. to Usage statistics about the schema change if it is not safe based on usage.
The statistics are determined based on the breaking change configuration.
The usage statistics are only available for breaking changes and only represent a snapshot of the usage data at the time of the schema check/schema publish. - Field SchemaChangeUsageStatisticsAffectedOperation.operation description changed from Get the associated operation. The field is nullable as this data is only stored for the duration of the usage retention period. to Get the associated operation.
The field is nullable as this data is only stored for the duration of the usage retention period. - Field SchemaCheck.schemaProposalChanges description changed from If the check is associated with a schema proposal, then this contains an unfiltered list of changes to the SDL. to If the check is associated with a schema proposal, then this contains an unfiltered list of changes
to the SDL. - Field SchemaCheck.schemaVersion description changed from The schema version against this check was performed. Is null if there is no schema version published yet. to The schema version against this check was performed.
Is null if there is no schema version published yet. - Field SchemaCheckError.schemaProposalChanges description changed from If the check is associated with a schema proposal, then this contains an unfiltered list of changes to the SDL. to If the check is associated with a schema proposal, then this contains an unfiltered list of changes
to the SDL. - Input field SchemaCheckInput.contextId description changed from Optional context ID to group schema checks together. Manually approved breaking changes will be memorized for schema checks with the same context id. to Optional context ID to group schema checks together.
Manually approved breaking changes will be memorized for schema checks with the same context id. - Field SchemaCheckSuccess.schemaProposalChanges description changed from If the check is associated with a schema proposal, then this contains an unfiltered list of changes to the SDL. to If the check is associated with a schema proposal, then this contains an unfiltered list of changes
to the SDL. - Input field SchemaComposeInput.useLatestComposableVersion description changed from *Whether to use the latest composable version or just latest schema version for the composition. Latest schema version may or may not be composable. It*s true by default, which means the latest composable schema version is used. to *Whether to use the latest composable version or just latest schema version for the composition.
Latest schema version may or may not be composable.
It*s true by default, which means the latest composable schema version is used. - Field SchemaCoordinateUsage.usedByClients description changed from A list of clients that use this schema coordinate within GraphQL operation documents. Is null if used by none clients. to A list of clients that use this schema coordinate within GraphQL operation documents.
Is null if used by none clients. - Field SchemaProposal.author description changed from The author of the proposal. If no author has been assigned, then this returns an empty string. The author is taken from the author of the oldest check ran for this proposal. to The author of the proposal. If no author has been assigned, then this returns an empty string.
The author is taken from the author of the oldest check ran for this proposal. - Field SchemaProposal.checks description changed from The checks associated with this proposal. Each proposed change triggers a check for the set of changes. And each service is checked separately. This is a limitation of the schema check API at this time. The check cursor can be considered the proposal version. to **The checks associated with this proposal. Each proposed change triggers a check
for the set of changes. And each service is checked separately. This is a limitation
of the schema check API at this time.
The check cursor can be considered the proposal version.**
- Description for argument after on field SchemaProposal.rebasedSchemaSDL changed from A schema check cursor. This indicates from where in the list of schema checks to start applying the changes. The check cursor can be considered the proposal version. to A schema check cursor. This indicates from where in the list of schema checks to start applying
the changes. The check cursor can be considered the proposal version. - Description for argument fromCursor on field SchemaProposal.rebasedSupergraphSDL changed from A schema check cursor. This indicates from where in the list of schema checks to start applying the changes. to A schema check cursor. This indicates from where in the list of schema checks to start applying
the changes. - Field SchemaProposal.stage description changed from The current stage of the proposal. Proposals should be transitioned through the course of the review from DRAFT, OPEN, APPROVED, IMPLEMENTED, but may be CLOSED at any point in its lifecycle prior to being IMPLEMENTED. DRAFT, OPEN, APPROVED, and CLOSED may be triggered by user action. But IMPLEMENTED can only happen if the target schema contains the proposed changes while the proposal is in the APPROVED state. to The current stage of the proposal. Proposals should be transitioned through the
course of the review from DRAFT, OPEN, APPROVED, IMPLEMENTED, but may be CLOSED
at any point in its lifecycle prior to being IMPLEMENTED. DRAFT, OPEN, APPROVED,
and CLOSED may be triggered by user action. But IMPLEMENTED can only happen if
the target schema contains the proposed changes while the proposal is in the
APPROVED state. - Field SchemaProposal.title description changed from A short title of this proposal. Meant to give others an easy way to refer to this set of changes. to A short title of this proposal. Meant to give others an easy way to refer to this
set of changes. - Field SchemaProposalReview.createdAt description changed from *When the review was first made. Only a review*s comments are mutable, so there is no updatedAt on the review. to *When the review was first made. Only a review*s comments are mutable, so there is no
updatedAt on the review. - Field SchemaProposalReview.lineText description changed from *The text on the line at the time of being reviewed. This should be displayed if that coordinate*s text has been modified If the lineText is null then this review references the entire SchemaProposalVersion and not any specific line within the proposal. to **The text on the line at the time of being reviewed. This should be displayed if that
coordinate**s text has been modified
If the lineText is null then this review references the entire SchemaProposalVersion
and not any specific line within the proposal.**
- Field SchemaProposalReview.schemaCoordinate description changed from The coordinate being referenced by this review. This is the most accurate location and should be used prior to falling back to the lineNumber. Only if this coordinate does not exist in the comparing schema, should the line number be used. to The coordinate being referenced by this review. This is the most accurate location and should be used prior
to falling back to the lineNumber. Only if this coordinate does not exist in the comparing schema, should the line number be used. - Field SchemaProposalReview.serviceName description changed from *Name of the service if reviewing a specific service*s schema. Else an empty string. to *Name of the service if reviewing a specific service*s schema.
Else an empty string. - Field SchemaProposalReview.stageTransition description changed from If null then this review is just a comment. Otherwise, the reviewer changed the state of the proposal as part of their review. E.g. The reviewer can approve a version with a comment. to If null then this review is just a comment. Otherwise, the reviewer changed the state of the
proposal as part of their review. E.g. The reviewer can approve a version with a comment. - Description for argument period on field SchemaVersion.deprecatedSchema changed from The period for which the usage data should be included within the result. Defaults to the last 30 days by default. to **The period for which the usage data should be included within the result.
Defaults to the last 30 days by default.**
- Field SchemaVersion.log description changed from The log that initiated this schema version. For a federation schema this is the published or removed subgraph/service. to The log that initiated this schema version.
For a federation schema this is the published or removed subgraph/service. - Field SchemaVersion.schemas description changed from The schemas that are composed within this schema version. For federation these are the subgraphs/services. to The schemas that are composed within this schema version.
For federation these are the subgraphs/services. - Field SchemaVersion.tags description changed from List of tags in the schema version. E.g. when using Federation. Tags can be used for filtering the schema via contracts. to List of tags in the schema version. E.g. when using Federation.
Tags can be used for filtering the schema via contracts. - Description for argument period on field SchemaVersion.unusedSchema changed from The period to use in order to determind whether a field is unused. A field is unused if it has not been requested within the specified period. Defaults to the last 30 days by default. to **The period to use in order to determind whether a field is unused.
A field is unused if it has not been requested within the specified period.
Defaults to the last 30 days by default.**
- Description for enum value SeverityLevelType.DANGEROUS changed from The change might break existing clients that do not follow best-practises such as future-proof enums or future-proof interface/union type usages. to The change might break existing clients that do not follow
best-practises such as future-proof enums or future-proof interface/union type usages. - Field Subscription.oidcIntegrationLog description changed from Subscribe to logs from the OIDC provider integration. Helpful for debugging failing logins. to Subscribe to logs from the OIDC provider integration.
Helpful for debugging failing logins. - Field SuccessfulSchemaCheck.schemaProposalChanges description changed from If the check is associated with a schema proposal, then this contains an unfiltered list of changes to the SDL. to If the check is associated with a schema proposal, then this contains an unfiltered list of changes
to the SDL. - Field SuccessfulSchemaCheck.schemaVersion description changed from The schema version against this check was performed. Is null if there is no schema version published yet. to The schema version against this check was performed.
Is null if there is no schema version published yet. - Field SupergraphMetadata.ownedByServiceNames description changed from List of service names that own the field/type. Resolves to null if the entity (field, type, scalar) does not belong to any service. to List of service names that own the field/type.
Resolves to null if the entity (field, type, scalar) does not belong to any service. - Field Target.activeAppDeployments description changed from Find active app deployments matching specific criteria. Date filter conditions (lastUsedBefore, neverUsedAndCreatedBefore) use OR semantics. If no date filters are provided, all active deployments are returned. The name filter uses AND semantics to narrow results. Only active deployments are returned (not pending or retired). to Find active app deployments matching specific criteria.
Date filter conditions (lastUsedBefore, neverUsedAndCreatedBefore) use OR semantics.
If no date filters are provided, all active deployments are returned.
The name filter uses AND semantics to narrow results.
Only active deployments are returned (not pending or retired). - Field Target.graphqlEndpointUrl description changed from **The endpoint url of the target*s explorer/laboratory instance. This is the public endpoint configured in target*s settings. to **The endpoint url of the target*s explorer/laboratory instance.
This is the public endpoint configured in target*s settings. - Field Trace.clientName description changed from The client name. Usually this is the *x-graphql-client-name* or *graphql-client-name* header sent to the gateway. to The client name.
Usually this is the *x-graphql-client-name* or *graphql-client-name* header sent to the gateway. - Field Trace.clientVersion description changed from The client version. Usually this is the *x-graphql-client-version* or *graphql-client-version* header sent to the gateway. to The client version.
Usually this is the *x-graphql-client-version* or *graphql-client-version* header sent to the gateway. - Field Trace.success description changed from Wether the trace is successful. A trace is a success if no GraphQL errors occured and the HTTP status code is in the 2XX to 3XX range. to Wether the trace is successful.
A trace is a success if no GraphQL errors occured and the HTTP status code is in the 2XX to 3XX range. - Input field TracesFilterInput.operationTypes description changed from Filter based on the operation type. A value of *null* value indicates a unknown operation type. to **Filter based on the operation type.
A value of *null* value indicates a unknown operation type.**
- Input field TracesFilterInput.success description changed from Filter based on whether the operation is a success. A operation is successful if no GraphQL error has occured and the result is within the 2XX or 3XX range. to Filter based on whether the operation is a success.
A operation is successful if no GraphQL error has occured and the result is within the 2XX or 3XX range. - Field UnusedSchemaExplorer.types description changed from The affected unused types and their fields/values/members etc. The types within the result only contain unused fields/values/members, all other entities are excluded, they are not a representation of the full GraphQL schema. to **The affected unused types and their fields/values/members etc.
The types within the result only contain unused fields/values/members, all other entities are excluded,
they are not a representation of the full GraphQL schema.**
- Input field UpdateOIDCRestrictionsInput.oidcUserJoinOnly description changed from Applies only to newly invited members. Existing members are not affected. to Applies only to newly invited members.
Existing members are not affected. - Field WhoAmI.resolvedPermissions description changed from A structured view of permissions that the authorized actor can perform, optionally including all possible permissions for context. to A structured view of permissions that the authorized actor can perform,
optionally including all possible permissions for context. - Description for argument includeAll on field WhoAmI.resolvedPermissions changed from If true, include all known permissions in the response, even those not currently granted. to If true, include all known permissions in the response,
even those not currently granted. - Field WhoAmI.title description changed from Human-readable title identifying the type of actor (e.g., User, Access Token). to Human-readable title identifying the type of actor
(e.g., User, Access Token). - Description Represents the currently authorized actor (user, service, etc.) and its associated permissions. on type WhoAmI has changed to Represents the currently authorized actor (user, service, etc.)
and its associated permissions.