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

fix(deps): update all npm non-major packages >= 1.0 #358

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 15, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@apollo/federation-internals (source) 2.9.1 -> 2.9.3 age adoption passing confidence dependencies patch
@apollo/query-planner (source) 2.9.1 -> 2.9.3 age adoption passing confidence dependencies patch
@apollo/usage-reporting-protobuf (source) 4.1.0 -> 4.1.1 age adoption passing confidence dependencies patch
make-dir-cli 3.0.0 -> 3.1.0 age adoption passing confidence devDependencies minor
node (source) 16.20.0 -> 16.20.2 age adoption passing confidence volta patch
npm (source) 9.7.1 -> 9.9.3 age adoption passing confidence volta minor
typescript (source) 5.1.3 -> 5.6.3 age adoption passing confidence devDependencies minor

Release Notes

apollographql/federation (@​apollo/federation-internals)

v2.9.3

Compare Source

Patch Changes
  • fix: normalize field set selection sets (#​3162)

    FieldSet scalar represents a selection set without outer braces. This means that users could potentially specify some selections that could be normalized (i.e. eliminate duplicate field selections, hoist/collapse unnecessary inline fragments, etc). Previously we were using @requires field set selection AS-IS for edge conditions. With this change we will now normalize the FieldSet selections before using them as fetch node conditions.

  • Fixed missing referenced variables in the variableUsages field of fetch operations (#​3166)

    Query variables used in fetch operation should be listed in the variableUsages field. However, there was a bug where variables referenced by query-level directives could be missing in the field.

  • Fix fragment generation recursion logic to apply minification on all subselections. (#​3158)

  • Fixed a bug that __typename with applied directives gets lost in fetch operations. (#​3164)

    The sibling typename optimization used by query planner simplifies operations by folding __typename selections into their sibling selections. However, that optimization does not account for directives or aliases. The bug was applying the optimization even if the __typename has directives on it, which caused the selection to lose its directives. Now, __typename with directives (or aliases) are excluded from the optimization.

v2.9.2

Compare Source

Patch Changes
  • Fixes handling of a __typename selection during query planning process. (#​3156)

    When expanding fragments we were keeping references to the same Fields regardless where those fragments appeared in our original selection set. This was generally fine as in most cases we would have same inline fragment selection sets across whole operation but was causing problems when we were applying another optimization by collapsing those expanded inline fragments creating a new selection set. As a result, if any single field selection (within that fragment) would perform optimization around the usage of __typename, ALL occurrences of that field selection would get that optimization as well.

  • Add validations for demand control directive applications (#​3148)

apollographql/federation (@​apollo/query-planner)

v2.9.3

Compare Source

Patch Changes
  • Fixes edge case where contextual arguments can yield inefficient query plans. Also fixes naming of query plan arguments which can be a problem when using contextual variables in multiple subgraphs (#​3140)

  • Ensure all useless fetch groups are removed (#​3163)

    When removing "useless" fetch nodes/groups we remove them in-place while still iterating over the same list. This leads to potentially skipping processing of some the children fetch nodes, as when we remove nodes we left shift all remaining children but the iterator keeps the old position unchanged effectively skipping next child.

  • fix: normalize field set selection sets (#​3162)

    FieldSet scalar represents a selection set without outer braces. This means that users could potentially specify some selections that could be normalized (i.e. eliminate duplicate field selections, hoist/collapse unnecessary inline fragments, etc). Previously we were using @requires field set selection AS-IS for edge conditions. With this change we will now normalize the FieldSet selections before using them as fetch node conditions.

  • Fixed missing referenced variables in the variableUsages field of fetch operations (#​3166)

    Query variables used in fetch operation should be listed in the variableUsages field. However, there was a bug where variables referenced by query-level directives could be missing in the field.

  • Fixed a bug that __typename with applied directives gets lost in fetch operations. (#​3164)

    The sibling typename optimization used by query planner simplifies operations by folding __typename selections into their sibling selections. However, that optimization does not account for directives or aliases. The bug was applying the optimization even if the __typename has directives on it, which caused the selection to lose its directives. Now, __typename with directives (or aliases) are excluded from the optimization.

  • Updated dependencies [345661c558773e4eb5d5f0b28464a8d1acdc2a2d, e00e1c9892b48ac89823597113989830877966ef, cc4573471696ef78d04fa00c4cf8e5c50314ba9f, 062572b3253e8640b60a0bf58b83945094b76b6f, df5eb3cb0e2b4802fcd425ab9c23714de2707db3, 1c99cb0dcc6c639ac351210932623ab0bd6907e4]:

v2.9.2

Compare Source

Patch Changes
  • Fixes handling of a __typename selection during query planning process. (#​3156)

    When expanding fragments we were keeping references to the same Fields regardless where those fragments appeared in our original selection set. This was generally fine as in most cases we would have same inline fragment selection sets across whole operation but was causing problems when we were applying another optimization by collapsing those expanded inline fragments creating a new selection set. As a result, if any single field selection (within that fragment) would perform optimization around the usage of __typename, ALL occurrences of that field selection would get that optimization as well.

  • Fixes issue where contextual parameters can have naming collisions if used in multiple subgraphs (#​3155)

  • Updated dependencies [2192f355f50db33fe0807d16153f357696b9f190, e1e2605b30efc488b57f62ba43436606a38a3607, 5ac01b534318105e904c1e6598070f753add3bb1]:

apollographql/apollo-server (@​apollo/usage-reporting-protobuf)

v4.1.1

Compare Source

Patch Changes
  • #​7614 4fadf3ddc Thanks @​Cellule! - Publish TypeScript typings for CommonJS modules output.

    This allows TypeScript projects that use CommonJS modules with
    moduleResolution: "node16" or
    moduleResolution: "nodeNext"
    to correctly resolves the typings of apollo's packages as CommonJS instead of ESM.

sindresorhus/make-dir-cli (make-dir-cli)

v3.1.0

Compare Source

nodejs/node (node)

v16.20.2: 2023-08-09, Version 16.20.2 'Gallium' (LTS), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes

The following CVEs are fixed in this release:

More detailed information on each of the vulnerabilities can be found in August 2023 Security Releases blog post.

Commits

v16.20.1: 2023-06-20, Version 16.20.1 'Gallium' (LTS), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes

The following CVEs are fixed in this release:

More detailed information on each of the vulnerabilities can be found in June 2023 Security Releases blog post.

Commits
npm/cli (npm)

v9.9.3

Compare Source

Bug Fixes
Dependencies
Chores

v9.9.2

Compare Source

Bug Fixes
Documentation
Dependencies

v9.9.1

Compare Source

Bug Fixes
Documentation

v9.9.0

Compare Source

Features
Bug Fixes
Documentation
Dependencies

v9.8.1

Compare Source

Bug Fixes
Documentation
Dependencies

v9.8.0

Compare Source

Features
Dependencies

v9.7.2

Compare Source

Bug Fixes
Documentation
Dependencies
microsoft/TypeScript (typescript)

v5.6.3

Compare Source

v5.6.2

Compare Source

v5.5.4: TypeScript 5.5.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.5.3: TypeScript 5.5.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.5.2: TypeScript 5.5

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.4.5: TypeScript 5.4.5

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.4.4: TypeScript 5.4.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.4.3: TypeScript 5.4.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.4.2: TypeScript 5.4

Compare Source

For release notes, check out the [release announcemen


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 force-pushed the renovate/npm-all-non-major-gte-1.0 branch from 0c3d98a to 32982aa Compare June 15, 2023 22:07
@renovate renovate bot changed the title fix(deps): update all npm non-major packages >= 1.0 to v2.4.8 fix(deps): update all npm non-major packages >= 1.0 to v2.4.8 - autoclosed Jun 15, 2023
@renovate renovate bot closed this Jun 15, 2023
@renovate renovate bot deleted the renovate/npm-all-non-major-gte-1.0 branch June 15, 2023 22:45
@renovate renovate bot changed the title fix(deps): update all npm non-major packages >= 1.0 to v2.4.8 - autoclosed fix(deps): update all npm non-major packages >= 1.0 to v2.4.8 Jun 20, 2023
@renovate renovate bot reopened this Jun 20, 2023
@renovate renovate bot changed the title fix(deps): update all npm non-major packages >= 1.0 to v2.4.8 chore(deps): update node.js to v16.20.1 Jun 21, 2023
@renovate renovate bot force-pushed the renovate/npm-all-non-major-gte-1.0 branch from 32982aa to 63b3516 Compare June 21, 2023 01:00
@renovate renovate bot changed the title chore(deps): update node.js to v16.20.1 fix(deps): update all npm non-major packages >= 1.0 Jun 21, 2023
@renovate renovate bot force-pushed the renovate/npm-all-non-major-gte-1.0 branch 11 times, most recently from 7920cfa to c94a717 Compare June 28, 2023 01:38
@renovate renovate bot force-pushed the renovate/npm-all-non-major-gte-1.0 branch 6 times, most recently from 6c1cae8 to e2a0b50 Compare July 5, 2023 08:01
@renovate renovate bot force-pushed the renovate/npm-all-non-major-gte-1.0 branch 4 times, most recently from 2847262 to e4ea0ef Compare July 7, 2023 17:34
@renovate renovate bot force-pushed the renovate/npm-all-non-major-gte-1.0 branch 6 times, most recently from dd73b5c to 29ded3c Compare August 29, 2024 16:34
@renovate renovate bot force-pushed the renovate/npm-all-non-major-gte-1.0 branch 5 times, most recently from d7e64ac to b5118ff Compare September 9, 2024 20:41
@renovate renovate bot force-pushed the renovate/npm-all-non-major-gte-1.0 branch 4 times, most recently from 99ee878 to c44e344 Compare September 18, 2024 13:09
@renovate renovate bot force-pushed the renovate/npm-all-non-major-gte-1.0 branch 7 times, most recently from 931d40e to a94894d Compare September 23, 2024 20:28
@renovate renovate bot force-pushed the renovate/npm-all-non-major-gte-1.0 branch 2 times, most recently from 102a670 to 496149f Compare October 1, 2024 21:00
@renovate renovate bot force-pushed the renovate/npm-all-non-major-gte-1.0 branch from 496149f to 6cb83f3 Compare October 9, 2024 01:03
@renovate renovate bot force-pushed the renovate/npm-all-non-major-gte-1.0 branch 2 times, most recently from 7f3e756 to 33c1ed3 Compare October 21, 2024 18:35
@renovate renovate bot force-pushed the renovate/npm-all-non-major-gte-1.0 branch from 33c1ed3 to d6e053e Compare November 4, 2024 17:17
@renovate renovate bot force-pushed the renovate/npm-all-non-major-gte-1.0 branch from d6e053e to 391836c Compare November 8, 2024 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants