Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update apollo graphql packages #59

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update apollo graphql packages #59

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 13, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@apollo/gateway (source) 2.6.2 -> 2.8.3 age adoption passing confidence dependencies minor
@apollo/server (source) 4.10.0 -> 4.10.4 age adoption passing confidence dependencies patch
@apollo/subgraph (source) 2.6.2 -> 2.8.3 age adoption passing confidence dependencies minor
ghcr.io/apollographql/router v1.39.0 -> v1.51.0 age adoption passing confidence final minor
ghcr.io/apollographql/router v1.39.0 -> v1.51.0 age adoption passing confidence minor

Release Notes

apollographql/federation (@​apollo/gateway)

v2.8.3

Compare Source

Patch Changes

v2.8.2

Compare Source

Patch Changes

v2.8.1

Compare Source

Patch Changes

v2.8.0

Compare Source

Minor Changes

  • Implement new directives to allow getting and setting context. This allows resolvers to reference and access data referenced by entities that exist in the GraphPath that was used to access the field. The following example demonstrates the ability to access the prop field within the Child resolver. (#​2988)

    type Query {
  p: Parent!
}
type Parent @​key(fields: "id") @​context(name: "context") {
  id: ID!
  child: Child!
  prop: String!
}
type Child @​key(fields: "id") {
  id: ID!
  b: String!
  field(a: String @​fromContext(field: "$context { prop }")): Int!
}
Patch Changes

v2.7.8

Compare Source

Patch Changes

v2.7.7

Compare Source

Patch Changes

v2.7.6

Compare Source

Patch Changes

v2.7.5

Compare Source

Patch Changes

v2.7.4

Compare Source

Patch Changes

v2.7.3

Compare Source

Patch Changes

v2.7.2

Compare Source

Patch Changes

v2.7.1

Compare Source

Patch Changes

v2.7.0

Compare Source

Minor Changes

  • Implement progressive @override functionality (#​2911)

    The progressive @override feature brings a new argument to the @override directive: label: String. When a label is added to an @override application, the override becomes conditional, depending on parameters provided to the query planner (a set of which labels should be overridden). Note that this feature will be supported in router for enterprise users only.

    Out-of-the-box, the router will support a percentage-based use case for progressive @override. For example:

    type Query {
  hello: String @​override(from: "original", label: "percent(5)")
}

    The above example will override the root hello field from the "original" subgraph 5% of the time.

    More complex use cases will be supported by the router via the use of coprocessors/rhai to resolve arbitrary labels to true/false values (i.e. via a feature flag service).

Patch Changes

v2.6.3

Compare Source

Patch Changes
apollographql/apollo-server (@​apollo/server)

v4.10.4

Compare Source

Patch Changes
  • #​7871 18a3827 Thanks @​tninesling! - Subscription heartbeats are initialized prior to awaiting subscribe(). This allows long-running setup to happen in the returned Promise without the subscription being terminated prior to resolution.

v4.10.3

Compare Source

Patch Changes
  • #​7866 5f335a5 Thanks @​tninesling! - Catch errors thrown by subscription generators, and gracefully clean up the subscription instead of crashing.

v4.10.2

Compare Source

Patch Changes
  • #​7849 c7e514c Thanks @​TylerBloom! - In the subscription callback server plugin, terminating a subscription now immediately closes the internal async generator. This avoids that generator existing after termination and until the next message is received.

v4.10.1

Compare Source

Patch Changes
  • #​7843 72f568e Thanks @​bscherlein! - Improves timing of the willResolveField end hook on fields which return Promises resolving to Arrays. This makes the use of the setCacheHint method more reliable.
apollographql/federation (@​apollo/subgraph)

v2.8.3

Compare Source

Patch Changes

v2.8.2

Compare Source

Patch Changes

v2.8.1

Compare Source

Patch Changes

v2.8.0

Compare Source

Patch Changes

v2.7.8

Compare Source

Patch Changes

v2.7.7

Compare Source

Patch Changes

v2.7.6

Compare Source

Patch Changes

v2.7.5

Compare Source

Patch Changes

v2.7.4

Compare Source

Patch Changes

v2.7.3

Compare Source

Patch Changes

v2.7.2

Compare Source

Patch Changes

v2.7.1

Compare Source

Patch Changes

v2.7.0

Compare Source

Minor Changes

  • Implement progressive @override functionality (#​2911)

    The progressive @override feature brings a new argument to the @override directive: label: String. When a label is added to an @override application, the override becomes conditional, depending on parameters provided to the query planner (a set of which labels should be overridden). Note that this feature will be supported in router for enterprise users only.

    Out-of-the-box, the router will support a percentage-based use case for progressive @override. For example:

    type Query {
  hello: String @​override(from: "original", label: "percent(5)")
}

    The above example will override the root hello field from the "original" subgraph 5% of the time.

    More complex use cases will be supported by the router via the use of coprocessors/rhai to resolve arbitrary labels to true/false values (i.e. via a feature flag service).

Patch Changes

v2.6.3

Compare Source

Patch Changes
apollographql/router (ghcr.io/apollographql/router)

v1.51.0

Compare Source

🚀 Features
Support conditional coprocessor execution per stage of request lifecycle (PR #​5557)

The router now supports conditional execution of the coprocessor for each stage of the request lifecycle (except for the Execution stage).

To configure, define conditions for a specific stage by using selectors based on headers or context entries. For example, based on a supergraph response you can configure the coprocessor not to execute for any subscription:

coprocessor:
  url: http://127.0.0.1:3000 # mandatory URL which is the address of the coprocessor
  timeout: 2s # optional timeout (2 seconds in this example). If not set, defaults to 1 second
  supergraph:
    response: 
      condition:
        not:
          eq:
          - subscription
          - operation_kind: string
      body: true

To learn more, see the documentation about coprocessor conditions.

By @​bnjjj in https://github.com/apollographql/router/pull/5557

Add option to deactivate introspection response caching (PR #​5583)

The router now supports an option to deactivate introspection response caching. Because the router caches responses as introspection happens in the query planner, cached introspection responses may consume too much of the distributed cache or fill it up. Setting this option prevents introspection responses from filling up the router's distributed cache.

To deactivate introspection caching, set supergraph.query_planning.legacy_introspection_caching to false:

supergraph:
  query_planning:
    legacy_introspection_caching: false

By @​Geal in https://github.com/apollographql/router/pull/5583

Add 'subgraph_on_graphql_error' selector for subgraph (PR #​5622)

The router now supports the subgraph_on_graphql_error selector for the subgraph service, which it already supported for the router and supergraph services. Subgraph service support enables easier detection of GraphQL errors in response bodies of subgraph requests.

An example configuration with subgraph_on_graphql_error configured:

telemetry:
  instrumentation:
    instruments:
      subgraph:
        http.client.request.duration:
          attributes:
            subgraph.graphql.errors: # attribute containing a boolean set to true if response.errors is not empty
              subgraph_on_graphql_error: true

By @​bnjjj in https://github.com/apollographql/router/pull/5622

🐛 Fixes
Add response_context in event selector for event_* instruments (PR #​5565)

The router now supports creating custom instruments with a value set to event_* and using both a condition executed on an event and the response_context selector in attributes. Previous releases didn't support the response_context selector in attributes.

An example configuration:

telemetry:
  instrumentation:
    instruments:
      supergraph:
        sf.graphql_router.errors:
          value: event_unit
          type: counter
          unit: count
          description: "graphql errors handled by the apollo router"
          condition:
            eq:
            - true
            - on_graphql_error: true
          attributes:
            "operation":
              response_context: "operation_name" # This was not working before

By @​bnjjj in https://github.com/apollographql/router/pull/5565

Provide valid trace IDs for unsampled traces in Rhai scripts (PR #​5606)

The traceid() function in a Rhai script for the router now returns a valid trace ID for all traces.

Previously, traceid() didn't return a trace ID if the trace wasn't selected for sampling.

By @​bnjjj in https://github.com/apollographql/router/pull/5606

Allow query batching and entity caching to work together (PR #​5598)

The router now supports entity caching and subgraph batching to run simultaneously. Specifically, this change updates entity caching to ignore a subgraph request if the request is part of a batch.

By @​garypen in https://github.com/apollographql/router/pull/5598

Gracefully handle subgraph response with -1 values inside error locations (PR #​5633)

This router now gracefully handles responses that contain invalid "-1" positional values for error locations in queries by ignoring those invalid locations.

This change resolves the problem of GraphQL Java and GraphQL Kotlin using { "line": -1, "column": -1 } values if they can't determine an error's location in a query, but the GraphQL specification requires both line and column to be positive numbers.

As an example, a subgraph can respond with invalid error locations:

{
    "data": { "topProducts": null },
    "errors": [{
        "message":"Some error on subgraph",
        "locations": [
            { "line": -1, "column": -1 },
        ],
        "path":["topProducts"]
    }]
}

With this change, the router returns a response that ignores the invalid locations:

{
    "data": { "topProducts": null },
    "errors": [{
        "message":"Some error on subgraph",
        "path":["topProducts"]
    }]
}

By @​IvanGoncharov in https://github.com/apollographql/router/pull/5633

Return request timeout and rate limited error responses as structured errors (PR #​5578)

The router now returns request timeout errors (408 Request Timeout) and request rate limited errors (429 Too Many Requests) as structured GraphQL errors (for example, {"errors": [...]}). Previously, the router returned these as plaintext errors to clients.

Both types of errors are properly tracked in telemetry, including the apollo_router_graphql_error_total metric.

By @​IvanGoncharov in https://github.com/apollographql/router/pull/5578

Fix span names and resource mapping for Datadog trace exporter (Issue #​5282)

[!NOTE]
This is an incremental improvement, but we expect more improvements in Router v1.52.0 after https://github.com/apollographql/router/pull/5609/ lands.

The router now uses static span names by default. This change fixes the user experience of the Datadog trace exporter when sending traces with Datadog native configuration.

The router has two ways of sending traces to Datadog:

  1. The OpenTelemetry for Datadog approach (which is the recommended method). This is identified by otlp in YAML configuration, and it is not impacted by this fix.
  2. The "Datadog native" configuration. This is identified by the use of a datadog: key in YAML configuration.

This change fixes a bug in the latter approach that broke some Datadog experiences, such as the "Resources" section of the Datadog APM Service Catalog page.

We now use static span names by default, with resource mappings providing additional context when requested, which enables the desired behavior which was not possible before.

If for some reason you wish to maintain the existing behavior, you must either update your spans and resource mappings, or keep your spans and instead configure the router to use dynamic span names and disable resource mapping.

Enabling resource mapping and fixed span names is configured by the enable_span_mapping and fixed_span_names options:

telemetry:
  exporters:
    tracing:
      datadog:
        enabled: true

##### Enables resource mapping, previously disabled by default, but now enabled.
        enable_span_mapping: true

##### Enables fixed span names, defaults to true.
        fixed_span_names: true

  instrumentation:
    spans:
      mode: spec_compliant

With enable_span_mapping set to true (now default), the following resource mappings are applied:

OpenTelemetry Span Name Datadog Span Operation Name
request http.route
router http.route
supergraph graphql.operation.name
query_planning graphql.operation.name
subgraph subgraph.name
subgraph_request graphql.operation.name
http_request http.route

You can override the default resource mappings by specifying the resource_mapping configuration:

telemetry:
  exporters:
    tracing:
      datadog:
        enabled: true
        resource_mapping:

##### Use `my.span.attribute` as the resource name for the `router` span
          router: "my.span.attribute"

To learn more, see the Datadog trace exporter documentation.

By @​bnjjj and @​bryncooke in https://github.com/apollographql/router/pull/5386

📚 Documentation
Update documentation for ignore_other_prefixes (PR #​5592)

Update JWT authentication documentation to clarify the behavior of the ignore_other_prefixes configuration option.

By @​andrewmcgivery in https://github.com/apollographql/router/pull/5592

v1.50.0

Compare Source

🚀 Features
Support local persisted query manifests for use with offline licenses (Issue #​4587)

Adds experimental support for passing persisted query manifests to use instead of the hosted Uplink version.

For example:

persisted_queries:
  enabled: true
  log_unknown: true
  experimental_local_manifests: 
    - ./persisted-query-manifest.json
  safelist:
    enabled: true
    require_id: false

By @​lleadbet in https://github.com/apollographql/router/pull/5310

Support conditions on standard telemetry events (Issue #​5475)

Enables setting conditions on standard events.
For example:

telemetry:
  instrumentation:
    events:
      router:
        request:
          level: info
          condition: # Only log the router request if you sent `x-log-request` with the value `enabled`
            eq:
            - request_header: x-log-request
            - "enabled"
        response: off
        error: error

##### ...

Not supported for batched requests.
By @​bnjjj in https://github.com/apollographql/router/pull/5476

Make status_code available for router_service responses in Rhai scripts (Issue #​5357)

Adds response.status_code on Rhai router_service responses. Previously, status_code was only available on subgraph_service responses.

For example:

fn router_service(service) {
    let f = |response| {
        if response.is_primary() {
            print(response.status_code);
        }
    };

    service.map_response(f);
}

By @​IvanGoncharov in https://github.com/apollographql/router/pull/5358

Add new values for the supergraph query selector (PR #​5433)

Adds support for four new values for the supergraph query selector:

  • aliases: the number of aliases in the query
  • depth: the depth of the query
  • height: the height of the query
  • root_fields: the number of root fields in the query

You can use this data to understand how your graph is used and to help determine where to set limits.

For example:

telemetry:
  instrumentation:
    instruments:
      supergraph:
        'query.depth':
          description: 'The depth of the query'
          value:
            query: depth
          unit: unit
          type: histogram

By @​garypen in https://github.com/apollographql/router/pull/5433

Add the ability to drop metrics using otel views (PR #​5531)

You can drop specific metrics if you don't want these metrics to be sent to your APM using otel views.

telemetry:
  exporters:
    metrics:
      common:
        service_name: apollo-router
        views:
          - name: apollo_router_http_request_duration_seconds # Instrument name you want to edit. You can use wildcard in names. If you want to target all instruments just use '*'
            aggregation: drop

By @​bnjjj in https://github.com/apollographql/router/pull/5531

Add operation_name selector for router service in custom telemetry (PR #​5392)

Adds an operation_name selector for the router service.
Previously, accessing operation_name was only possible through the response_context router service selector.

For example:

telemetry:
  instrumentation:
    instruments:
      router:
        http.server.request.duration:
          attributes:
            graphql.operation.name:
              operation_name: string

By @​bnjjj in https://github.com/apollographql/router/pull/5392

🐛 Fixes
Fix Cache-Control aggregation and age calculation in entity caching (PR #​5463)

Enhances the reliability of caching behaviors in the entity cache feature by:

  • Ensuring the proper calculation of max-age and s-max-age fields in the Cache-Control header sent to clients.
  • Setting appropriate default values if a subgraph does not provide a Cache-Control header.
  • Guaranteeing that the Cache-Control header is aggregated consistently, even if the plugins is disabled entirely or on specific subgraphs.

By @​Geal in https://github.com/apollographql/router/pull/5463

Fix telemetry events when trace isn't sampled and preserve attribute types (PR #​5464)

Improves accuracy and performance of event telemetry by:

  • Displaying custom event attributes even if the trace is not sampled
  • Preserving original attribute type instead of converting it to string
  • Ensuring http.response.body.size and http.request.body.size attributes are treated as numbers, not strings

⚠️ Exercise caution if you have monitoring enabled on your logs, as attribute types may have changed. For example, attributes like http.response.status_code are now numbers (200) instead of strings ("200").

By @​bnjjj in https://github.com/apollographql/router/pull/5464

Enable coprocessors for subscriptions (PR #​5542)

Ensures that coprocessors correctly handle subscriptions by preventing skipped data from being overwritten.

By @​bnjjj in https://github.com/apollographql/router/pull/5542

Improve accuracy of query_planning.plan.duration (PR #​5)

Previously, the apollo.router.query_planning.plan.duration metric inaccurately included additional processing time beyond query planning. The additional time included pooling time, which is already accounted for in the metric. After this update, apollo.router.query_planning.plan.duration now accurately reflects only the query planning duration without additional processing time.

For example, before the change, metrics reported:

2024-06-21T13:37:27.744592Z WARN  apollo.router.query_planning.plan.duration 0.002475708
2024-06-21T13:37:27.744651Z WARN  apollo.router.query_planning.total.duration 0.002553958

2024-06-21T13:37:27.748831Z WARN  apollo.router.query_planning.plan.duration 0.001635833
2024-06-21T13:37:27.748860Z WARN  apollo.router.query_planning.total.duration 0.001677167

Post-change metrics now accurately reflect:

2024-06-21T13:37:27.743465Z WARN  apollo.router.query_planning.plan.duration 0.00107725
2024-06-21T13:37:27.744651Z WARN  apollo.router.query_planning.total.duration 0.002553958

2024-06-21T13:37:27.748299Z WARN  apollo.router.query_planning.plan.duration 0.000827
2024-06-21T13:37:27.748860Z WARN  apollo.router.query_planning.total.duration 0.001677167

By @​xuorig and @​lrlna in https://github.com/apollographql/router/pull/5530

Remove deno_crypto package due to security vulnerability (Issue #​5484)

Removes deno_crypto due to the vulnerability reported in curve25519-dalek.
Since the router exclusively used deno_crypto for generating UUIDs using the package's random number generator, this vulnerability had no impact on the router.

By @​Geal in https://github.com/apollographql/router/pull/5483

Add content-type header to failed auth checks (Issue #​5496)

Adds content-type header when returning AUTH_ERROR from authentication service.

By @​andrewmcgivery in https://github.com/apollographql/router/pull/5497

Implement manual caching for AWS Security Token Service credentials (PR #​5508)

In the AWS Security Token Service (STS), the CredentialsProvider chain includes caching, but this functionality was missing for AssumeRoleProvider.
This change introduces a custom CredentialsProvider that functions as a caching layer with these rules:

  • Cache Expiry: Credentials retrieved are stored in the cache based on their credentials.expiry() time if specified, or indefinitely (ever) if not.
  • Automatic Refresh: Five minutes before cached credentials expire, an attempt is made to fetch updated credentials.
  • Retry Mechanism: If credential retrieval fails, another attempt is scheduled after a one-minute interval.
  • (Coming soon, not included in this change) Manual Refresh: The CredentialsProvider will expose a refresh_credentials() function. This can be manually invoked, for instance, upon receiving a 401 error during a subgraph call.

By @​o0Ignition0o in https://github.com/apollographql/router/pull/5508

📃 Configuration
Align entity caching configuration structure for subgraph overrides (PR #​5474)

Aligns the entity cache configuration structure to the same all/subgraphs override pattern found in other parts of the router configuration. For example, see the header propagation configuration.
An automated configuration migration is provided so existing usage is unaffected.

By @​Geal in https://github.com/apollographql/router/pull/5474

Restrict custom instrument values to relevant stages (PR #​5472)

Previously, custom instruments at each request lifecycle stage could specify unrelated values, like using event_unit for a router instrument. Now, only relevant values for each stage are allowed.

Additionally, GraphQL instruments no longer need to specify field_event. There is no automatic migration for this change since GraphQL instruments are still experimental.

telemetry:
  instrumentation:
    instruments:
      graphql:

##### OLD definition of a custom instrument that measures the number of fields
        my.unit.instrument:
          value: field_unit # Changes to unit

##### NEW definition
        my.unit.instrument:
          value: unit 

##### OLD  
        my.custom.instrument:
          value: # Changes to not require `field_custom`
            field_custom:
              list_length: value

##### NEW
        my.custom.instrument:
          value: 
            list_length: value

The following misconfiguration is now not possible:

router_instrument:
  value:
    event_custom:
      request_header: foo

By @​BrynCooke in https://github.com/apollographql/router/pull/5472

🛠 Maintenance
Add cost information to protobuf traces (PR #​5430)

Exports query cost information on Apollo protobuf traces if experimental_demand_control is enabled. Also displays exported information in GraphOS Studio.

By @​BrynCooke in https://github.com/apollographql/router/pull/5430

Improve xtask release process (PR #​5275)

Introduces a new xtask command to automate the release process by:

  • Following the commands defined in our `RE

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@grafbase Grafbase
Copy link

grafbase bot commented Feb 13, 2024 •
edited
Loading

Graph was successfully deployed.

View Deployment

@nx-cloud Nx Cloud
Copy link

nx-cloud bot commented Feb 13, 2024 •
edited
Loading

☁️ Nx Cloud Report

CI is running/has finished running commands for commit eb8e1ae. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

✅ Successfully ran 2 targets

Sent with 💌 from NxCloud.

@renovate renovate bot changed the title fix(deps): update apollo graphql packages fix(deps): update apollo graphql packages to v2.7.1 Feb 13, 2024
@renovate renovate bot changed the title fix(deps): update apollo graphql packages to v2.7.1 fix(deps): update apollo graphql packages Feb 14, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 9 times, most recently from 69452e2 to 4967a64 Compare February 18, 2024 20:35
@renovate renovate bot changed the title fix(deps): update apollo graphql packages fix(deps): update apollo graphql packages to v2.7.1 Feb 20, 2024
@renovate renovate bot changed the title fix(deps): update apollo graphql packages to v2.7.1 fix(deps): update apollo graphql packages Feb 20, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 4967a64 to f77aa1d Compare February 20, 2024 10:29
@renovate renovate bot changed the title fix(deps): update apollo graphql packages fix(deps): update apollo graphql packages to v2.7.1 Feb 22, 2024
@renovate renovate bot changed the title fix(deps): update apollo graphql packages to v2.7.1 fix(deps): update apollo graphql packages Feb 22, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from f77aa1d to c1a6eb3 Compare February 25, 2024 11:11
@renovate renovate bot changed the title fix(deps): update apollo graphql packages fix(deps): update apollo graphql packages to v2.7.1 Feb 26, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from c1a6eb3 to c8352b7 Compare February 26, 2024 10:57
@renovate renovate bot changed the title fix(deps): update apollo graphql packages to v2.7.1 fix(deps): update apollo graphql packages Feb 26, 2024
@renovate renovate bot changed the title fix(deps): update apollo graphql packages fix(deps): update apollo graphql packages to v2.7.1 Mar 2, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from c8352b7 to cd980fb Compare March 2, 2024 16:25
@renovate renovate bot changed the title fix(deps): update apollo graphql packages to v2.7.1 fix(deps): update apollo graphql packages Mar 2, 2024
@renovate renovate bot changed the title fix(deps): update apollo graphql packages fix(deps): update apollo graphql packages to v2.7.1 Mar 2, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from cd980fb to 41827e9 Compare March 3, 2024 06:30
@renovate renovate bot changed the title fix(deps): update apollo graphql packages to v2.7.1 fix(deps): update apollo graphql packages Mar 3, 2024
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from d2fea7d to 100f9c6 Compare March 6, 2024 16:21
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from 02c1f4c to 2867808 Compare May 23, 2024 06:22
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 7a8bc46 to 753fa47 Compare May 29, 2024 03:33
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 7 times, most recently from 546b8e0 to 25b8e96 Compare June 10, 2024 19:38
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 5 times, most recently from aa00d35 to 97f7e35 Compare June 18, 2024 18:16
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 4 times, most recently from c027b42 to 670a5f1 Compare June 22, 2024 01:10
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from a07bb1a to 957da66 Compare July 2, 2024 21:23
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from 439d7c4 to 1a97ec0 Compare July 13, 2024 00:45
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 1a97ec0 to f6c45a0 Compare July 14, 2024 09:07
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from f6c45a0 to eb8e1ae Compare July 16, 2024 22:40
@sonarcloud SonarCloud
Copy link

sonarcloud bot commented Jul 16, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants