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 #290

Closed
wants to merge 2 commits into from

Conversation

cu-infra-svc-git
Copy link
Contributor

@cu-infra-svc-git cu-infra-svc-git commented Sep 2, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-import-resolver-typescript ^3.6.1 -> ^3.6.3 age adoption passing confidence
eslint-plugin-import ^2.29.1 -> ^2.30.0 age adoption passing confidence
eslint-plugin-prettier ^5.1.3 -> ^5.2.1 age adoption passing confidence
jsii-diff (source) ^1.100.0 -> ^1.103.1 age adoption passing confidence
jsii-pacmak (source) ^1.100.0 -> ^1.103.1 age adoption passing confidence
pnpm (source) 9.1.2 -> 9.9.0 age adoption passing confidence
prettier (source) ^3.3.2 -> ^3.3.3 age adoption passing confidence
semver ^7.6.2 -> ^7.6.3 age adoption passing confidence
ts-jest (source) ^29.1.5 -> ^29.2.5 age adoption passing confidence
typescript (source) ^5.5.2 -> ^5.5.4 age adoption passing confidence

Release Notes

import-js/eslint-import-resolver-typescript (eslint-import-resolver-typescript)

v3.6.3

Compare Source

Patch Changes
import-js/eslint-plugin-import (eslint-plugin-import)

v2.30.0

Compare Source

Added
Fixed
Changed
  • [Docs] no-extraneous-dependencies: Make glob pattern description more explicit ([#​2944], thanks [@​mulztob])
  • [no-unused-modules]: add console message to help debug [#​2866]
  • [Refactor] ExportMap: make procedures static instead of monkeypatching exportmap ([#​2982], thanks [@​soryy708])
  • [Refactor] ExportMap: separate ExportMap instance from its builder logic ([#​2985], thanks [@​soryy708])
  • [Docs] order: Add a quick note on how unbound imports and --fix ([#​2640], thanks [@​minervabot])
  • [Tests] appveyor -> GHA (run tests on Windows in both pwsh and WSL + Ubuntu) ([#​2987], thanks [@​joeyguerra])
  • [actions] migrate OSX tests to GHA ([ljharb#37], thanks [@​aks-])
  • [Refactor] exportMapBuilder: avoid hoisting ([#​2989], thanks [@​soryy708])
  • [Refactor] ExportMap: extract "builder" logic to separate files ([#​2991], thanks [@​soryy708])
  • [Docs] [order]: update the description of the pathGroupsExcludedImportTypes option ([#​3036], thanks [@​liby])
  • [readme] Clarify how to install the plugin ([#​2993], thanks [@​jwbth])
prettier/eslint-plugin-prettier (eslint-plugin-prettier)

v5.2.1

Compare Source

Patch Changes
aws/jsii (jsii-diff)

v1.103.1

Compare Source

Bug Fixes
  • python: user defined __jsii_proxy_class attributes are not preserved (#​4625) (d3ec911)

v1.103.0

Compare Source

Features
Bug Fixes

v1.102.0

Compare Source

v1.101.0

Compare Source

Bug Fixes
pnpm/pnpm (pnpm)

v9.9.0: pnpm 9.9

Compare Source

Minor Changes

  • Minor breaking change. This change might result in resolving your peer dependencies slightly differently but we don't expect it to introduce issues.

    We had to optimize how we resolve peer dependencies in order to fix some infinite loops and out-of-memory errors during peer dependencies resolution.

    When a peer dependency is a prod dependency somewhere in the dependency graph (with the same version), pnpm will resolve the peers of that peer dependency in the same way across the subgraph.

    For example, we have react-dom in the peer deps of the form and button packages. card has react-dom and react as regular dependencies and card is a dependency of form.

    These are the direct dependencies of our example project:

    form
    react@16
    react-dom@16
    

    These are the dependencies of card:

    button
    react@17
    react-dom@16
    

    When resolving peers, pnpm will not re-resolve react-dom for card, even though card shadows react@16 from the root with react@17. So, all 3 packages (form, card, and button) will use react-dom@16, which in turn uses react@16. form will use react@16, while card and button will use react@17.

    Before this optimization react-dom@16 was duplicated for the card, so that card and button would use a react-dom@16 instance that uses react@17.

    Before the change:

    form
    -> react-dom@16(react@16)
    -> react@16
    card
    -> react-dom@16(react@17)
    -> react@17
    button
    -> react-dom@16(react@17)
    -> react@17
    

    After the change

    form
    -> react-dom@16(react@16)
    -> react@16
    card
    -> react-dom@16(react@16)
    -> react@17
    button
    -> react-dom@16(react@16)
    -> react@17
    

Patch Changes

  • pnpm deploy should write the node_modules/.modules.yaml to the node_modules directory within the deploy directory #​7731.
  • Don't override a symlink in node_modules if it already points to the right location pnpm/symlink-dir#54.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.8.0: pnpm 9.8

Compare Source

Minor Changes

  • Added a new command for upgrading pnpm itself when it isn't managed by Corepack: pnpm self-update. This command will work, when pnpm was installed via the standalone script from the pnpm installation page #​8424.

    When executed in a project that has a packageManager field in its package.json file, pnpm will update its version in the packageManager field.

Patch Changes

  • CLI tools installed in the root of the workspace should be added to the PATH, when running scripts and use-node-version is set.

  • pnpm setup should never switch to another version of pnpm.

    This fixes installation with the standalone script from a directory that has a package.json with the packageManager field. pnpm was installing the version of pnpm specified in the packageManager field due to this issue.

  • Ignore non-string value in the os, cpu, libc fields, which checking optional dependencies #​8431.

  • Remember the state of edit dir, allow running pnpm patch-commit the second time without having to re-run pnpm patch.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.7.1: pnpm 9.7.1

Compare Source

Patch Changes

  • Fixed passing public-hoist-pattern and hoist-pattern via env variables #​8339.
  • pnpm setup no longer creates Batch/Powershell scripts on Linux and macOS #​8418.
  • When dlx uses cache, use the real directory path not the symlink to the cache #​8421.
  • pnpm exec now supports executionEnv #​8356.
  • Remove warnings for non-root pnpm field, add warnings for non-root pnpm subfields that aren't executionEnv #​8143.
  • Replace semver in "peerDependency" with workspace protocol #​8355.
  • Fix a bug in patch-commit in which relative path is rejected #​8405.
  • Update Node.js in @pnpm/exe to v20.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.7.0: pnpm 9.7

Compare Source

Minor Changes

  • Added pnpm version management. If the manage-package-manager-versions setting is set to true, pnpm will switch to the version specified in the packageManager field of package.json #​8363. This is the same field used by Corepack. Example:

    {
      "packageManager": "[email protected]"
    }
  • Added the ability to apply patch to all versions #​8337.

    If the key of pnpm.patchedDependencies is a package name without a version (e.g. pkg), pnpm will attempt to apply the patch to all versions of the package. Failures will be skipped. If there's only one version of pkg installed, pnpm patch pkg and subsequent pnpm patch-commit $edit_dir will create an entry named pkg in pnpm.patchedDependencies. And pnpm will attempt to apply this patch to other versions of pkg in the future.

  • Change the default edit dir location when running pnpm patch from a temporary directory to node_modules/.pnpm_patches/pkg[@​version] to allow the code editor to open the edit dir in the same file tree as the main project #​8379.

  • Substitute environment variables in config keys #​6679.

Patch Changes

  • pnpm install should run node-gyp rebuild if the project has a binding.gyp file even if the project doesn't have an install script #​8293.
  • Print warnings to stderr #​8342.
  • Peer dependencies of optional peer dependencies should be automatically installed #​8323.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.6.0: pnpm 9.6

Compare Source

Minor Changes

  • Support specifying node version (via pnpm.executionEnv.nodeVersion in package.json) for running lifecycle scripts per each package in a workspace #​6720.
  • Overrides now support the catalogs: protocol #​8303.

Patch Changes

  • The pnpm deploy command now supports the catalog: protocol #​8298.
  • The pnpm outdated command now supports the catalog: protocol #​8304.
  • Correct the error message when trying to run pnpm patch without node_modules/.modules.yaml #​8257.
  • Silent reporting fixed with the pnpm exec command #​7608.
  • Add registries information to the calculation of dlx cache hash #​8299.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

config help if that's undesired.


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

This PR has been generated by Renovate Bot.

Copy link

codecov bot commented Sep 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.38%. Comparing base (e5e3fc5) to head (e2c8fec).
Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #290   +/-   ##
=======================================
  Coverage   99.38%   99.38%           
=======================================
  Files          17       17           
  Lines        2272     2272           
  Branches      138      138           
=======================================
  Hits         2258     2258           
  Misses         14       14           

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e5e3fc5...e2c8fec. Read the comment docs.

Signed-off-by: github-actions <[email protected]>
@cu-infra-svc-git
Copy link
Contributor Author

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.

Copy link

This pull request is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. If you wish to exclude this issue from being marked as stale, add the "backlog" label.

@github-actions github-actions bot added the stale label Sep 19, 2024
Copy link

Closing this pull request as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. If you wish to exclude this issue from being marked as stale, add the "backlog" label.

@github-actions github-actions bot closed this Sep 22, 2024
auto-merge was automatically disabled September 22, 2024 01:32

Pull request was closed

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.

1 participant