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.

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

chore(deps): update all non-major dependencies #451

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 21, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@apollo/client (source) 3.10.5 -> 3.11.8 age adoption passing confidence devDependencies minor
@changesets/cli (source) 2.27.5 -> 2.27.8 age adoption passing confidence devDependencies patch
@graphql-codegen/client-preset (source) 4.3.0 -> 4.3.3 age adoption passing confidence devDependencies patch
@types/jest (source) 29.5.12 -> 29.5.13 age adoption passing confidence devDependencies patch
@types/node (source) 16.18.98 -> 16.18.108 age adoption passing confidence devDependencies patch
eslint (source) 8.57.0 -> 8.57.1 age adoption passing confidence devDependencies patch
graphql 16.8.2 -> 16.9.0 age adoption passing confidence devDependencies minor
loglevel 1.9.1 -> 1.9.2 age adoption passing confidence devDependencies patch
node (source) 20.14.0 -> 20.17.0 age adoption passing confidence volta minor
npm (source) 10.8.1 -> 10.8.3 age adoption passing confidence volta patch
prettier (source) 3.3.2 -> 3.3.3 age adoption passing confidence devDependencies patch
ts-jest (source) 29.1.5 -> 29.2.5 age adoption passing confidence devDependencies minor
typescript (source) 5.4.5 -> 5.6.2 age adoption passing confidence devDependencies minor
winston 3.13.0 -> 3.14.2 age adoption passing confidence devDependencies minor
winston-transport 4.7.0 -> 4.7.1 age adoption passing confidence devDependencies patch

Release Notes

apollographql/apollo-client (@​apollo/client)

v3.11.8

Compare Source

Patch Changes

v3.11.7

Compare Source

Patch Changes
  • #​12052 e471cef Thanks @​jerelmiller! - Fixes a regression from where passing an invalid identifier to from in useFragment would result in the warning TypeError: Cannot read properties of undefined (reading '__typename').

v3.11.6

Compare Source

Patch Changes

v3.11.5

Compare Source

Patch Changes

v3.11.4

Compare Source

Patch Changes
  • #​11994 41b17e5 Thanks @​jerelmiller! - Update the Modifier function type to allow cache.modify to return deeply partial data.

  • #​11989 e609156 Thanks @​phryneas! - Fix a potential crash when calling clearStore while a query was running.

    Previously, calling client.clearStore() while a query was running had one of these results:

    • useQuery would stay in a loading: true state.
    • useLazyQuery would stay in a loading: true state, but also crash with a "Cannot read property 'data' of undefined" error.

    Now, in both cases, the hook will enter an error state with a networkError, and the promise returned by the useLazyQuery execute function will return a result in an error state.

  • #​11994 41b17e5 Thanks @​jerelmiller! - Prevent accidental distribution on cache.modify field modifiers when a field is a union type array.

v3.11.3

Compare Source

Patch Changes
Potentially disruptive change

When calling fetchMore with a query that has a no-cache fetch policy, fetchMore will now throw if an updateQuery function is not provided. This provides a mechanism to merge the results from the fetchMore call with the query's previous result.

v3.11.2

Compare Source

Patch Changes

v3.11.1

Compare Source

Patch Changes
  • #​11969 061cab6 Thanks @​jerelmiller! - Remove check for window.__APOLLO_CLIENT__ when determining whether to connect to Apollo Client Devtools when connectToDevtools or devtools.enabled is not specified. This now simply checks to see if the application is in development mode.

  • #​11971 ecf77f6 Thanks @​jerelmiller! - Prevent the setTimeout for suggesting devtools from running in non-browser environments.

v3.11.0

Compare Source

Potentially Breaking Fixes
  • #​11789 5793301 Thanks @​phryneas! - Changes usages of the GraphQLError type to GraphQLFormattedError.

    This was a type bug - these errors were never GraphQLError instances
    to begin with, and the GraphQLError class has additional properties that can
    never be correctly rehydrated from a GraphQL result.
    The correct type to use here is GraphQLFormattedError.

    Similarly, please ensure to use the type FormattedExecutionResult
    instead of ExecutionResult - the non-"Formatted" versions of these types
    are for use on the server only, but don't get transported over the network.

  • #​11626 228429a Thanks @​phryneas! - Call nextFetchPolicy with "variables-changed" even if there is a fetchPolicy specified.

    Previously this would only be called when the current fetchPolicy was equal to the fetchPolicy option or the option was not specified. If you use nextFetchPolicy as a function, expect to see this function called more often.

    Due to this bug, this also meant that the fetchPolicy might be reset to the initial fetchPolicy, even when you specified a nextFetchPolicy function. If you previously relied on this behavior, you will need to update your nextFetchPolicy callback function to implement this resetting behavior.

    As an example, if your code looked like the following:

    useQuery(QUERY, {
      nextFetchPolicy(currentFetchPolicy, info) {
        // your logic here
      }
    );

    Update your function to the following to reimplement the resetting behavior:

    useQuery(QUERY, {
      nextFetchPolicy(currentFetchPolicy, info) {
        if (info.reason === 'variables-changed') {
          return info.initialFetchPolicy;
        }
        // your logic here
      }
    );
Minor Changes
Patch Changes

v3.10.8

Compare Source

Patch Changes

v3.10.7

Compare Source

Patch Changes

v3.10.6

Compare Source

Patch Changes
changesets/changesets (@​changesets/cli)

v2.27.8

Compare Source

v2.27.7

Compare Source

Patch Changes

v2.27.6

Compare Source

Patch Changes
dotansimha/graphql-code-generator (@​graphql-codegen/client-preset)

v4.3.3

Compare Source

Patch Changes

v4.3.2

Compare Source

Patch Changes

v4.3.1

Compare Source

Patch Changes
eslint/eslint (eslint)

v8.57.1

Compare Source

graphql/graphql-js (graphql)

v16.9.0

Compare Source

v16.9.0 (2024-06-21)

New Feature 🚀
  • #​4119 backport[v16]: Introduce "recommended" validation rules (@​benjie)
  • #​4122 backport[v16]: Enable passing values configuration to GraphQLEnumType as a thunk (@​benjie)
  • #​4124 backport[v16]: Implement OneOf Input Objects via @oneOf directive (@​benjie)
Committers: 1
pimterry/loglevel (loglevel)

v1.9.2

Compare Source

nodejs/node (node)

v20.17.0

Compare Source

v20.16.0

Compare Source

v20.15.1

Compare Source

v20.15.0: 2024-06-20, Version 20.15.0 'Iron' (LTS), @​marco-ippolito

Compare Source

test_runner: support test plans

It is now possible to count the number of assertions and subtests that are expected to run within a test. If the number of assertions and subtests that run does not match the expected count, the test will fail.

test('top level test', (t) => {
  t.plan(2);
  t.assert.ok('some relevant assertion here');
  t.subtest('subtest', () => {});
});

Contributed by Colin Ihrig in #​52860

inspector: introduce the --inspect-wait flag

This release introduces the --inspect-wait flag, which allows debugger to wait for attachement. This flag is useful when you want to debug the code from the beginning. Unlike --inspect-brk, which breaks on the first line, this flag waits for debugger to be connected and then runs the code as soon as a session is established.

Contributed by Kohei Ueno in #​52734

zlib: expose zlib.crc32()

This release exposes the crc32() function from zlib to user-land.

It computes a 32-bit Cyclic Redundancy Check checksum of data. If
value is specified, it is used as the starting value of the checksum,
otherwise, 0 is used as the starting value.

The CRC algorithm is designed to compute checksums and to detect error
in data transmission. It's not suitable for cryptographic authentication.

const zlib = require('node:zlib');
const { Buffer } = require('node:buffer');

let crc = zlib.crc32('hello');  // 907060870
crc = zlib.crc32('world', crc);  // 4192936109

crc = zlib.crc32(Buffer.from('hello', 'utf16le'));  // 1427272415
crc = zlib.crc32(Buffer.from('world', 'utf16le'), crc);  // 4150509955

Contributed by Joyee Cheung in #​52692

cli: allow running wasm in limited vmem with --disable-wasm-trap-handler

By default, Node.js enables trap-handler-based WebAssembly bound
checks. As a result, V8 does not need to insert inline bound checks
int the code compiled from WebAssembly which may speedup WebAssembly
execution significantly, but this optimization requires allocating
a big virtual memory cage (currently 10GB). If the Node.js process
does not have access to a large enough virtual memory address space
due to system configurations or hardware limitations, users won't
be able to run any WebAssembly that involves allocation in this
virtual memory cage and will see an out-of-memory error.

$ ulimit -v 5000000
$ node -p "new WebAssembly.Memory({ initial: 10, maximum: 100 });"
[eval]:1
new WebAssembly.Memory({ initial: 10, maximum: 100 });
^

RangeError: WebAssembly.Memory(): could not allocate memory
    at [eval]:1:1
    at runScriptInThisContext (node:internal/vm:209:10)
    at node:internal/process/execution:118:14
    at [eval]-wrapper:6:24
    at runScript (node:internal/process/execution:101:62)
    at evalScript (node:internal/process/execution:136:3)
    at node:internal/main/eval_string:49:3

--disable-wasm-trap-handler disables this optimization so that
users can at least run WebAssembly (with a less optimial performance)
when the virtual memory address space available to their Node.js
process is lower than what the V8 WebAssembly memory cage needs.

Contributed by Joyee Cheung in #​52766

Other Notable Changes
Commits

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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner June 21, 2024 18:32
Copy link

changeset-bot bot commented Jun 21, 2024

⚠️ No Changeset found

Latest commit: 0915870

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

Copy link

codesandbox-ci bot commented Jun 21, 2024

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 08fc129 to e8806bd Compare July 1, 2024 10:26
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 4ba69c8 to d5a57fe Compare July 8, 2024 19:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 237ecb7 to 0d6d8cb Compare July 16, 2024 23:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from b8d122f to da0808e Compare July 24, 2024 13:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 8fcd1c9 to 30c0f20 Compare August 2, 2024 19:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from a9731a6 to d6513e9 Compare August 9, 2024 19:18
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d6513e9 to 43bb123 Compare August 14, 2024 18:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from e9c84d1 to cf8658e Compare August 26, 2024 11:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 84bf153 to b418c2e Compare September 4, 2024 19:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 83a2536 to 4e7e227 Compare September 9, 2024 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants