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

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

Merged
merged 1 commit into from
Mar 6, 2023
Merged

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

merged 1 commit into from
Mar 6, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 24, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@babel/core (source) ^7.20.12 -> ^7.21.0 age adoption passing confidence
@babel/plugin-proposal-decorators (source) ^7.20.13 -> ^7.21.0 age adoption passing confidence
@babel/plugin-proposal-optional-chaining (source) ^7.20.7 -> ^7.21.0 age adoption passing confidence
@babel/plugin-transform-modules-commonjs (source) ^7.20.11 -> ^7.21.2 age adoption passing confidence
@babel/plugin-transform-typescript (source) ^7.20.13 -> ^7.21.0 age adoption passing confidence
@babel/preset-typescript (source) ^7.18.6 -> ^7.21.0 age adoption passing confidence
@babel/types (source) ^7.20.7 -> ^7.21.2 age adoption passing confidence
@types/node (source) ^18.13.0 -> ^18.14.6 age adoption passing confidence
@vitest/coverage-c8 ^0.28.5 -> ^0.29.2 age adoption passing confidence
changelogen ^0.4.1 -> ^0.5.1 age adoption passing confidence
eslint (source) ^8.34.0 -> ^8.35.0 age adoption passing confidence
pnpm (source) 7.27.0 -> 7.29.0 age adoption passing confidence
vite (source) ^4.1.2 -> ^4.1.4 age adoption passing confidence
vitest ^0.28.5 -> ^0.29.2 age adoption passing confidence

Release Notes

babel/babel

v7.21.0

Compare Source

🚀 New Feature
  • babel-core, babel-helper-create-class-features-plugin, babel-plugin-proposal-class-properties, babel-plugin-proposal-private-methods, babel-plugin-proposal-private-property-in-object
  • babel-helper-create-regexp-features-plugin, babel-plugin-proposal-regexp-modifiers, babel-standalone
  • babel-cli, babel-core, babel-generator, babel-plugin-transform-destructuring, babel-plugin-transform-modules-commonjs, babel-plugin-transform-react-jsx, babel-traverse
  • babel-parser, babel-types
  • babel-generator, babel-helpers, babel-parser, babel-plugin-proposal-decorators, babel-plugin-syntax-decorators, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • babel-parser
  • babel-core
  • babel-generator, babel-parser, babel-plugin-transform-typescript
🐛 Bug Fix
  • babel-plugin-transform-typescript
  • babel-core
  • babel-helper-create-class-features-plugin, babel-plugin-proposal-class-properties, babel-plugin-proposal-class-static-block, babel-plugin-proposal-private-methods, babel-plugin-transform-classes, babel-plugin-transform-new-target
  • babel-parser, babel-plugin-transform-flow-comments, babel-plugin-transform-flow-strip-types, babel-types
💅 Polish
🏠 Internal
🔬 Output optimization
vitest-dev/vitest

v0.29.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.29.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.29.0

Compare Source

This release makes some significant changes to how tests are running. If you were using --no-threads before, you might consider enabling --single-thread instead (because your tests are now running in child_process instead of a worker thread) or try our new performance optimization feature (discussed later). If you were relying on API that was not available inside a worker (like process.chdir(), you can now use this option.

One of the potential breaking bug fixes is that environments do not share the same global scope anymore if you run them with --no-isolate, --no-threads or --single-thread - you might need to update your setup files if you were relying on a global variable before.

If you had performance issues on large code bases before, try the new deps.experimentalOptimizer option instead of disabling threads. Feedback is welcome!

One of the breaking changes includes adding a link to snapshots inside snapshot files, meaning you will need to update all your snapshots.

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
unjs/changelogen

v0.5.1

Compare Source

compare changes

🩹 Fixes
  • Allow providing no versions (ac84c39)
  • Use parsed release body (aec2341)
  • Strip title line from release (319f7ce)
🏡 Chore
  • Simplify release command (225fa64)
❤️ Contributors

v0.5.0

Compare Source

compare changes

🚀 Enhancements
  • Update execa to v7 (e61e2f6)
  • ⚠️ Support different repository providers (#​55)
  • Github release integration (#​67)
  • Support explicit bumping as major, minor, or patch via cli (c8afa86)
  • Automatically resolve github token from gh cli (231a3ec)
  • Default gh release to latest version (44788f5)
🩹 Fixes
  • Stage CHANGELOG.md and package.json when releasing (69d375c)
  • Add correct output file to git (#​64)
  • Update ungh link (a5ab510)
  • Only access latest tag accessible from current branch (#​69)
  • cli: Don't eat up first -* arg (77b483b)
🏡 Chore
  • Fix lint issue and update snapshots (e162ab8)
  • Mention gh cli login (7f4a05f)
⚠️ Breaking Changes
  • ⚠️ Support different repository providers (#​55)
❤️ Contributors
eslint/eslint

v8.35.0

Compare Source

Features
  • 8e34a04 feat: add afterHashbangComment option to lines-around-comment rule (#​16920) (SUZUKI Sosuke)
  • c8c0c71 feat: Move all and recommended configs into package. (#​16844) (Nicholas C. Zakas)
  • 71f6f0d feat: report more cases with ?? in no-constant-binary-expression (#​16826) (Daiki Nishikawa)
Bug Fixes
Documentation
Chores
pnpm/pnpm

v7.29.0

Compare Source

Minor Changes

  • A new setting is now supported: dedupe-peer-dependents.

    When this setting is set to true, packages with peer dependencies will be deduplicated after peers resolution.

    For instance, let's say we have a workspace with two projects and both of them have webpack in their dependencies. webpack has esbuild in its optional peer dependencies, and one of the projects has esbuild in its dependencies. In this case, pnpm will link two instances of webpack to the node_modules/.pnpm directory: one with esbuild and another one without it:

    node_modules
  .pnpm
    webpack@1.0.0_esbuild@1.0.0
    webpack@1.0.0
project1
  node_modules
    webpack -> ../../node_modules/.pnpm/webpack@1.0.0/node_modules/webpack
project2
  node_modules
    webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
    esbuild

    This makes sense because webpack is used in two projects, and one of the projects doesn't have esbuild, so the two projects cannot share the same instance of webpack. However, this is not what most developers expect, especially since in a hoisted node_modules, there would only be one instance of webpack. Therefore, you may now use the dedupe-peer-dependents setting to deduplicate webpack when it has no conflicting peer dependencies (explanation at the end). In this case, if we set dedupe-peer-dependents to true, both projects will use the same webpack instance, which is the one that has esbuild resolved:

    node_modules
  .pnpm
    webpack@1.0.0_esbuild@1.0.0
project1
  node_modules
    webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
project2
  node_modules
    webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
    esbuild

    What are conflicting peer dependencies? By conflicting peer dependencies we mean a scenario like the following one:

    node_modules
  .pnpm
    webpack@1.0.0_react@16.0.0_esbuild@1.0.0
    webpack@1.0.0_react@17.0.0
project1
  node_modules
    webpack -> ../../node_modules/.pnpm/webpack@1.0.0/node_modules/webpack
    react (v17)
project2
  node_modules
    webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
    esbuild
    react (v16)

    In this case, we cannot dedupe webpack as webpack has react in its peer dependencies and react is resolved from two different versions in the context of the two projects.

Patch Changes

  • The configuration added by pnpm setup should check if the pnpm home directory is already in the PATH before adding to the PATH.

    Before this change, this code was added to the shell:

    export PNPM_HOME="$HOME/Library/pnpm"
export PATH="$PNPM_HOME:$PATH"

    Now this will be added:

    export PNPM_HOME="$HOME/Library/pnpm"
case ":$PATH:" in
  *":$PNPM_HOME:"*) ;;
  *) export PATH="$PNPM_HOME:$PATH" ;;
esac

  • Add skipped status in exec report summary when script is missing #​6139.

  • pnpm env -g should fail with a meaningful error message if pnpm cannot find the pnpm home directory, which is the directory into which Node.js is installed.

  • Should not throw an error when local dependency use file protocol #​6115.

  • Fix the incorrect error block when subproject has been patched #​6183

Our Gold Sponsors

Our Silver Sponsors

v7.28.0

Compare Source

Minor Changes

  • Add --report-summary for pnpm exec and pnpm run #​6008.
  • Show path info for pnpm why --json or --long #​6103.
  • Extend the pnpm.peerDependencyRules.allowedVersions package.json option to support the parent>child selector syntax. This syntax allows for extending specific peerDependencies #​6108.

Patch Changes

  • Update the lockfile if a workspace has a new project with no dependencies.
  • Fix a case of installs not being deterministic and causing lockfile changes between repeat installs. When a dependency only declares peerDependenciesMeta and not peerDependencies, dependencies, or optionalDependencies, the dependency's peers were not considered deterministically before.
  • patch-commit should auto apply patches in workspaces #​6048
  • Automatically fix conflicts in v6 lockfile.
  • pnpm config set should write to the global config file by default #​5877.

Our Gold Sponsors

Our Silver Sponsors

v7.27.1

Compare Source

Patch Changes

  • Add store path description to the pnpm cli help.
  • Print a hint that suggests to run pnpm store prune, when a tarball integrity error happens.
  • Don't retry installation if the integrity checksum of a package failed and no lockfile was present.
  • Fail with a meaningful error message when cannot parse a proxy URL.
  • The strict-ssl, ca, key, and cert settings should work with HTTPS proxy servers #​4689.

Our Gold Sponsors

Our Silver Sponsors
vitejs/vite

v4.1.4

Compare Source

v4.1.3

Compare Source

Configuration

📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).

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

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 7284b5b to 5fee5be Compare March 4, 2023 03:18
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5fee5be to b3e0053 Compare March 6, 2023 05:15
@pi0 pi0 merged commit 72510e7 into main Mar 6, 2023
@renovate renovate bot deleted the renovate/all-minor-patch branch March 6, 2023 20:17
@pi0 pi0 mentioned this pull request Mar 15, 2023
Merged
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.
1 participant
@pi0