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

Merged
merged 1 commit into from
Mar 9, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 5, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) ^18.14.2 -> ^18.14.6 age adoption passing confidence
changelogen ^0.4.1 -> ^0.5.1 age adoption passing confidence
jiti ^1.17.1 -> ^1.17.2 age adoption passing confidence
pnpm (source) 7.28.0 -> 7.29.1 age adoption passing confidence

Release Notes

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
unjs/jiti

v1.17.2

Compare Source

compare changes

🩹 Fixes
  • Add support to emit decorator metadata (#​119)
  • Use inline require cache to avoid circular dependencies (#​125)
  • Workaround for pnpm and TMPDIR (#​123)
🏡 Chore
✅ Tests
  • Add typescript satisfies fixture (#​107)
🎨 Styles
❤️ Contributors
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
        [email protected][email protected]
        [email protected]
    project1
      node_modules
        webpack -> ../../node_modules/.pnpm/[email protected]/node_modules/webpack
    project2
      node_modules
        webpack -> ../../node_modules/.pnpm/[email protected][email protected]/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
        [email protected][email protected]
    project1
      node_modules
        webpack -> ../../node_modules/.pnpm/[email protected][email protected]/node_modules/webpack
    project2
      node_modules
        webpack -> ../../node_modules/.pnpm/[email protected][email protected]/node_modules/webpack
        esbuild
    

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

    node_modules
      .pnpm
        [email protected][email protected][email protected]
        [email protected][email protected]
    project1
      node_modules
        webpack -> ../../node_modules/.pnpm/[email protected]/node_modules/webpack
        react (v17)
    project2
      node_modules
        webpack -> ../../node_modules/.pnpm/[email protected][email protected]/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
Copy link

codecov bot commented Mar 5, 2023

Codecov Report

Merging #220 (1eb04b0) into main (65921a1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #220   +/-   ##
=======================================
  Coverage   86.26%   86.26%           
=======================================
  Files           5        5           
  Lines         415      415           
  Branches       68       68           
=======================================
  Hits          358      358           
  Misses         57       57           

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

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from ac6abc5 to b252d1a Compare March 8, 2023 03:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b252d1a to 1eb04b0 Compare March 8, 2023 15:00
@renovate renovate bot merged commit fd3efd5 into main Mar 9, 2023
@renovate renovate bot deleted the renovate/all-minor-patch branch March 9, 2023 01:32
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