fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
aws-sdk	2.1400.0 -> 2.1402.0
graphql	16.6.0 -> 16.7.0
newrelic	9.8.1 -> 9.15.0
socket.io	4.6.2 -> 4.7.0
socket.io-client	4.6.2 -> 4.7.0

---

Release Notes

aws/aws-sdk-js

v2.1402.0

Compare Source

• feature: EMR: This release introduces a new Amazon EMR EPI called ListSupportedInstanceTypes that returns a list of all instance types supported by a given EMR release.
• feature: Inspector2: This release adds support for Software Bill of Materials (SBOM) export and the general availability of code scanning for AWS Lambda functions.
• feature: MQ: The Cross Region Disaster Recovery feature allows to replicate a brokers state from one region to another in order to provide customers with multi-region resiliency in the event of a regional outage.
• feature: MediaConvert: This release introduces the bandwidth reduction filter for the HEVC encoder, increases the limits of outputs per job, and updates support for the Nagra SDK to version 1.14.7.
• feature: SageMaker: This release provides support in SageMaker for output files in training jobs to be uploaded without compression and enable customer to deploy uncompressed model from S3 to real-time inference Endpoints. In addition, ml.trn1n.32xlarge is added to supported instance type list in training job.
• feature: Transfer: This release adds a new parameter StructuredLogDestinations to CreateServer, UpdateServer APIs.

v2.1401.0

Compare Source

• feature: Appflow: This release adds new API to reset connector metadata cache
• feature: ConfigService: Updated ResourceType enum with new resource types onboarded by AWS Config in May 2023.
• feature: EC2: Adds support for targeting Dedicated Host allocations by assetIds in AWS Outposts
• feature: Lambda: This release adds RecursiveInvocationException to the Invoke API and InvokeWithResponseStream API.
• feature: Redshift: Added support for custom domain names for Redshift Provisioned clusters. This feature enables customers to create a custom domain name and use ACM to generate fully secure connections to it.

graphql/graphql-js

v16.7.0

Compare Source

v16.7.0 (2023-06-21)

New Feature 🚀

• #​3887 check "globalThis.process" before accessing it (@​kettanaito)

Bug Fix 🐞

• #​3707 Fix crash in node when mixing sync/async resolvers (backport of #​3706) (@​chrskrchr)
• #​3838 Fix/invalid error propagation custom scalars (backport for 16.x.x) (@​stenreijers)

Committers: 3

• Artem Zakharchenko(@​kettanaito)
• Chris Karcher(@​chrskrchr)
• Sten Reijers(@​stenreijers)

newrelic/node-newrelic

v9.15.0

Compare Source

• Added a new configuration option heroku.use_dyno_names to specify whether or not to use process.env.DYNO for naming the host name and display host. This option defaults to true. If you are on heroku and do not want this functionality set heroku.use_dyno_names to false. You can also control this configuration options with the environment variable of NEW_RELIC_HEROKU_USE_DYNO_NAMES. Thanks @​benney-au-le for your contribution 🚀

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

v9.14.1

Compare Source

• Restored assigning loaded version of agent to require.cache as __NR_cache instead of a symbol to properly detect attempts at loading agent twice.

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

v9.14.0

Compare Source

• Added new API function called setErrorGroupCallback, which provides a way for you to customize the error.group.name attribute of errors that are captured by the agent. This attribute controls how the Errors Inbox functionality groups similar errors together. To learn more about this function, please refer to our example app.

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

v9.13.0

Compare Source

• Updated http instrumentation to no longer remove the x-new-relic-disable-dt header when using AWS SDK v3. This was done to prevent the "The request signature we calculated does not match the signature you provided. Check your key and signing method." error from AWS SDK.

• Added an API method setUserID to provide an ability to associate a unique identifier with a transaction event, transaction trace and errors within transaction. The attribute will be enduser.id.

• Added default configuration for security agent.

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

v9.12.1

Compare Source

v9.12.1 (2023-03-15)

• Added ability to mark errors as expected when using newrelic.noticeError, by adding an optional boolean:

  • newrelic.noticeError(error, {customAttributes}, true|false) when there are custom error attributes.
  • newrelic.noticeError(error, true|false) if there are no custom error attributes.
  • expected errors do not affect error metrics or Apdex.

• Added ability to disable distributed tracing for aws-sdk >= 3.290.0.

• Updated README header image to latest OSS office required images

• updated @​grpc/grpc-js from 1.8.8 to 1.8.9

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

v9.12.0

Compare Source

v9.11.0

Compare Source

v9.11.0 (2023-03-08)

• Added instrumentation for Prisma(@prisma/client).
  • Miniumum supported version of @prisma/client is 4.0.0.
  • Captures spans for queries.
    • It names them based on the model and action.(i.e. Datastore/statement/Prisma/user/create)
    • For statements and queries using the $queryRaw, $executeRaw, $queryRawUnsafe, and $executeRawUnsafe the names will be aligned with the raw SQL.(i.e. Datastore/statement/Prisma/User/select)
  • Captures database metrics for all statements and queries.
  • Captures SQL Traces.
  • Provides connection between application and database server via service maps.

Huge shoutout to @​osmanmrtacar for the original contribution 🙏🏻

• Updated @grpc/protoloader from 0.7.4 to 0.7.5.
• Updated @grpc/grpc-js from 1.8.7 to 1.8.8.

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

v9.10.2

Compare Source

v9.10.2 (2023-02-21)

• fix: Replaced request.aborted with response.close in HTTP instrumentation.
• Fixed issue where setting NEW_RELIC_GRPC_IGNORE_STATUS_CODES was not properly parsing the codes as integers, thus not ignoring reporting errors of certain status codes.
• Upgraded @grpc/grpc-js from 1.8.4 to 1.8.7.

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

v9.10.1

Compare Source

• Fixed error with Lambda/ALB serverless instrumentation when no response headers were included

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

v9.10.0

Compare Source

v9.10.0 (2023-02-09)

• Exposed a method on API to obfuscate sql: newrelic.obfuscateSql.

• Add support for Multi Value Parameters from API Gateway and ALB events for Lambdas (Thank you @​Engerim for your contribution 🙏🏻)

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

v9.9.0

Compare Source

v9.9.0 (2023-02-06)

• Added support for url obfuscation using regex (Thanks for your contribution @​matewilk)

  • For Distributed Tracing, this means that:
    • Incoming and outgoing requests' path will be obfuscated
    • Transaction's request.url attribute will be obfuscated
    • Span's http.uri path will be obfuscated
  • For transactions, this means that:
    • Transaction trace details url will be obfuscated
  • With the following example configuration, url obfuscation will turn /api/v1/users/12345456/edit to /api/v1/users/**/edit.

    url_obfuscation: {
      enabled: true,
      regex: {
        pattern: /(\/api\/v1\/users\/)([\d]+)(\/.*$)/,
        flags: "i",
        replacement: '$1**$3'
      }
    }

  • You can also use environment variables to configure url obfuscation:

    NEW_RELIC_URL_OBFUSCATION_ENABLED: "true",
    NEW_RELIC_URL_OBFUSCATION_REGEX_PATTERN: '/(\/api\/v1\/users\/)([\d]+)(\/.*$)/',
    NEW_RELIC_URL_OBFUSCATION_REGEX_FLAGS: 'i',
    NEW_RELIC_URL_OBFUSCATION_REGEX_REPLACEMENT: '$1**$3'

• Add a new tracking type of instrumentation. This will be responsible for logging Supportability/Features/Instrumentation/OnResolved/<pkg> and Supportability/Features/Instrumentation/OnResolved/<pkg>/Version/<version> metrics when packages are required.

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

socketio/socket.io

v4.7.0

Compare Source

Bug Fixes

• remove the Partial modifier from the socket.data type (#​4740) (e5c62ca)

Features

Support for WebTransport

The Engine.IO server can now use WebTransport as the underlying transport.

WebTransport is a web API that uses the HTTP/3 protocol as a bidirectional transport. It's intended for two-way communications between a web client and an HTTP/3 server.

References:

• https://w3c.github.io/webtransport/
• https://developer.mozilla.org/en-US/docs/Web/API/WebTransport
• https://developer.chrome.com/articles/webtransport/

Until WebTransport support lands in Node.js, you can use the @fails-components/webtransport package:

import { readFileSync } from "fs";
import { createServer } from "https";
import { Server } from "socket.io";
import { Http3Server } from "@​fails-components/webtransport";

// WARNING: the total length of the validity period MUST NOT exceed two weeks (https://w3c.github.io/webtransport/#custom-certificate-requirements)
const cert = readFileSync("/path/to/my/cert.pem");
const key = readFileSync("/path/to/my/key.pem");

const httpsServer = createServer({
  key,
  cert
});

httpsServer.listen(3000);

const io = new Server(httpsServer, {
  transports: ["polling", "websocket", "webtransport"] // WebTransport is not enabled by default
});

const h3Server = new Http3Server({
  port: 3000,
  host: "0.0.0.0",
  secret: "changeit",
  cert,
  privKey: key,
});

(async () => {
  const stream = await h3Server.sessionStream("/engine.io/");
  const sessionReader = stream.getReader();

  while (true) {
    const { done, value } = await sessionReader.read();
    if (done) {
      break;
    }
    io.engine.onWebTransportSession(value);
  }
})();

h3Server.startServer();

Added in 123b68c.

Client bundles with CORS headers

The bundles will now have the right Access-Control-Allow-xxx headers.

Added in 63f181c.

Dependencies

• engine.io@~6.4.2 (diff)
• ws@~8.11.0 (no change)

socketio/socket.io-client

v4.7.0

Compare Source

Bug Fixes

• properly report timeout error when connecting (5bc94b5)
• use same scope for setTimeout and clearTimeout calls (#​1568) (f2892ab)

Features

Support for WebTransport

The Engine.IO client can now use WebTransport as the underlying transport.

WebTransport is a web API that uses the HTTP/3 protocol as a bidirectional transport. It's intended for two-way communications between a web client and an HTTP/3 server.

References:

• https://w3c.github.io/webtransport/
• https://developer.mozilla.org/en-US/docs/Web/API/WebTransport
• https://developer.chrome.com/articles/webtransport/

For Node.js clients: until WebTransport support lands in Node.js, you can use the @fails-components/webtransport package:

import { WebTransport } from "@​fails-components/webtransport";

global.WebTransport = WebTransport;

Added in 7195c0f.

Cookie management for the Node.js client

When setting the withCredentials option to true, the Node.js client will now include the cookies in the HTTP requests, making it easier to use it with cookie-based sticky sessions.

import { io } from "socket.io-client";

const socket = io("https://example.com", {
  withCredentials: true
});

Added in 5fc88a6.

Conditional import of the ESM build with debug logs

By default, the ESM build does not include the debug package in the browser environments, because it increases the bundle size (see 16b6569).

Which means that, unfortunately, debug logs are not available in the devtools console, even when setting the localStorage.debug = ... attribute.

You can now import the build which includes the debug packages with a conditional import. Example with vite:

import { defineConfig } from 'vite'
import react from '@​vitejs/plugin-react'

export default defineConfig({
  plugins: [react()],
  server: {
    port: 4000
  },
  resolve: {
    conditions: ["development"]
  }
})

Reference: https://v2.vitejs.dev/config/#resolve-conditions

Added in 781d753.

Dependencies

• engine.io-client@~6.5.0 (diff)
• ws@~8.11.0 (no change)

---

Configuration

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

🚦 Automerge: Enabled.

♻ 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.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9848c3c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://ee56e0ad.envelop.pages.dev

[theguild-bot]

✅ Benchmark Results

     ✓ no_errors
     ✓ expected_result

     checks.............................................: 100.00% ✓ 611628      ✗ 0     
     data_received......................................: 2.3 GB  16 MB/s
     data_sent..........................................: 133 MB  886 kB/s
     envelop_total......................................: avg=0s      min=0s       med=0s      max=0s      p(90)=0s      p(95)=0s     
     ✓ { mode:envelop-cache-jit }.......................: avg=0s      min=0s       med=0s      max=0s      p(90)=0s      p(95)=0s     
     ✓ { mode:envelop-just-cache }......................: avg=0s      min=0s       med=0s      max=0s      p(90)=0s      p(95)=0s     
     ✓ { mode:graphql-js }..............................: avg=0s      min=0s       med=0s      max=0s      p(90)=0s      p(95)=0s     
     ✓ { mode:prom-tracing }............................: avg=0s      min=0s       med=0s      max=0s      p(90)=0s      p(95)=0s     
     event_loop_lag.....................................: avg=0s      min=0s       med=0s      max=0s      p(90)=0s      p(95)=0s     
     ✓ { mode:envelop-cache-and-no-internal-tracing }...: avg=0s      min=0s       med=0s      max=0s      p(90)=0s      p(95)=0s     
     ✓ { mode:envelop-cache-jit }.......................: avg=0s      min=0s       med=0s      max=0s      p(90)=0s      p(95)=0s     
     ✓ { mode:envelop-just-cache }......................: avg=0s      min=0s       med=0s      max=0s      p(90)=0s      p(95)=0s     
     ✓ { mode:graphql-js }..............................: avg=0s      min=0s       med=0s      max=0s      p(90)=0s      p(95)=0s     
     ✓ { mode:prom-tracing }............................: avg=0s      min=0s       med=0s      max=0s      p(90)=0s      p(95)=0s     
     http_req_blocked...................................: avg=1.71µs  min=600ns    med=1.1µs   max=17.28ms p(90)=1.7µs   p(95)=2.1µs  
     http_req_connecting................................: avg=89ns    min=0s       med=0s      max=4.7ms   p(90)=0s      p(95)=0s     
     http_req_duration..................................: avg=4.58ms  min=184.99µs med=3.5ms   max=87.84ms p(90)=9.38ms  p(95)=16.06ms
       { expected_response:true }.......................: avg=4.58ms  min=184.99µs med=3.5ms   max=87.84ms p(90)=9.38ms  p(95)=16.06ms
     ✓ { mode:envelop-cache-and-no-internal-tracing }...: avg=4.12ms  min=388.29µs med=3.63ms  max=44.57ms p(90)=6.75ms  p(95)=7.96ms 
     ✓ { mode:envelop-cache-jit }.......................: avg=2.32ms  min=184.99µs med=1.73ms  max=23.32ms p(90)=4.23ms  p(95)=7.53ms 
     ✓ { mode:envelop-just-cache }......................: avg=4.08ms  min=391.79µs med=3.53ms  max=38.29ms p(90)=6.89ms  p(95)=7.98ms 
     ✓ { mode:graphql-js }..............................: avg=6.79ms  min=693.99µs med=5.79ms  max=87.84ms p(90)=10.99ms p(95)=12.55ms
     ✓ { mode:prom-tracing }............................: avg=18.99ms min=3.83ms   med=17ms    max=78.91ms p(90)=32.85ms p(95)=34.14ms
     http_req_failed....................................: 0.00%   ✓ 0           ✗ 305814
     http_req_receiving.................................: avg=41.32µs min=11.2µs   med=18.59µs max=27.35ms p(90)=27.5µs  p(95)=34.79µs
     http_req_sending...................................: avg=31.61µs min=3.9µs    med=6.7µs   max=17.95ms p(90)=12.5µs  p(95)=17.5µs 
     http_req_tls_handshaking...........................: avg=0s      min=0s       med=0s      max=0s      p(90)=0s      p(95)=0s     
     http_req_waiting...................................: avg=4.51ms  min=154.89µs med=3.45ms  max=87.75ms p(90)=9.09ms  p(95)=16ms   
     http_reqs..........................................: 305814  2038.608738/s
     iteration_duration.................................: avg=4.89ms  min=380.69µs med=3.74ms  max=92.97ms p(90)=9.96ms  p(95)=16.36ms
     iterations.........................................: 305814  2038.608738/s
     vus................................................: 1       min=1         max=18  
     vus_max............................................: 20      min=20        max=20  

[github-actions]

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package	Version	Info
@envelop/response-cache-redis	3.1.1-alpha-20230622155047-b5ea321a	npm ↗︎ unpkg ↗︎

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.