chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vitest/coverage-c8	^0.29.1 -> ^0.29.2
changelogen	^0.4.1 -> ^0.5.1
eslint (source)	^8.34.0 -> ^8.35.0
pnpm (source)	7.28.0 -> 7.29.1
vitest	^0.29.1 -> ^0.29.2

---

Release Notes

vitest-dev/vitest

v0.29.2

Compare Source

   🐞 Bug Fixes

• Optimize dependencies in setup files  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/2935 (c169f)
• coverage: C8 provider to work when isolate:false  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/2929 (86538)

    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

• Pooya Parsa (@​pi0)

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

• Pooya Parsa (@​pi0)
• Daniel Roe daniel@roe.dev
• Donald Shtjefni (@​dnldsht)

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

• 9698bc5 fix: pin esquery v1.4.0 (fixes #​16896) (#​16897) (唯然)

Documentation

• f9f195e docs: Plugin docs cleanup & expansion (#​16862) (Ben Perlmutter)
• df809fd docs: Custom Formatters page cleanup/expansion (#​16886) (Ben Perlmutter)
• 0700d1b docs: Add PostCSS/Autoprefixer/CSSNano (#​16502) (Nick Schonning)
• 7b9e9bf docs: support unicode anchors (#​16782) (Percy Ma)
• 5fbc0bf docs: Update README (GitHub Actions Bot)
• 67865a0 docs: Remove mention of mailing list (#​16869) (Amaresh S M)
• 43af24a docs: Add explanation of when to use 'warn' severity (#​16882) (Nicholas C. Zakas)
• ed2999b docs: Shareable configs page edits and expansion (#​16824) (Ben Perlmutter)
• 2780635 docs: fix typos (#​16884) (Lioness100)
• 5bdaae2 docs: Ways to Extend ESLint page (#​16861) (Ben Perlmutter)

Chores

• cdcbe12 chore: upgrade @​eslint/js@​8.35.0 (#​16935) (Brandon Mills)
• c954c34 chore: package.json update for @​eslint/js release (ESLint Jenkins)
• 5a517da chore: package.json update for @​eslint/js release (ESLint Jenkins)
• 9f10926 chore: upgrade @​eslint/eslintrc@​2.0.0 (#​16928) (Milos Djermanovic)
• da728fa ci: use LTS node version in workflows (#​16907) (Nitin Kumar)
• c57b4f3 perf: upgrade to esquery@1.4.2 (#​16901) (Milos Djermanovic)
• 9122f07 chore: Update stale bot settings (#​16870) (Nicholas C. Zakas)

pnpm/pnpm

v7.29.1

Compare Source

Patch Changes

• Settings related to authorization should be set/deleted by npm CLI #​6181.

Our Gold Sponsors

Our Silver Sponsors

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

---

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.

[codecov]

Codecov Report

Merging #68 (cf497eb) into main (b8a0868) will not change coverage.
The diff coverage is n/a.

❗ Current head cf497eb differs from pull request most recent head fd228e3. Consider uploading reports for the commit fd228e3 to get more accurate results

@@    Coverage Diff     @@
##   main   #68   +/-   ##
==========================
==========================

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.