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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 9, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@commitlint/cli (source) 17.7.0 -> 17.8.1 age adoption passing confidence devDependencies minor
@commitlint/config-conventional (source) 17.7.0 -> 17.8.1 age adoption passing confidence devDependencies minor
cimg/node 20.5 -> 20.18 age adoption passing confidence docker minor
node (source) 18.17.0 -> 18.20.4 age adoption passing confidence minor
orb-tools 10.0.3 -> 10.1.0 age adoption passing confidence orb minor
semantic-release 21.0.7 -> 21.1.2 age adoption passing confidence devDependencies minor

Release Notes

conventional-changelog/commitlint (@​commitlint/cli)

v17.8.1

Compare Source

Note: Version bump only for package @​commitlint/cli

v17.8.0

Compare Source

Note: Version bump only for package @​commitlint/cli

17.7.2 (2023-09-28)

Note: Version bump only for package @​commitlint/cli

17.7.1 (2023-08-10)

Note: Version bump only for package @​commitlint/cli

v17.7.2

Compare Source

Note: Version bump only for package @​commitlint/cli

v17.7.1

Compare Source

Note: Version bump only for package @​commitlint/cli

conventional-changelog/commitlint (@​commitlint/config-conventional)

v17.8.1

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

v17.8.0

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

nodejs/node (node)

v18.20.4

Compare Source

v18.20.3: 2024-05-21, Version 18.20.3 'Hydrogen' (LTS), @​richardlau

Compare Source

Notable Changes

This release fixes a regression introduced in Node.js 18.19.0 where http.server.close() was incorrectly closing idle connections.

A fix has also been included for compiling Node.js from source with newer versions of Clang.

The list of keys used to sign releases has been synchronized with the current list from the main branch.

Updated dependencies
  • acorn updated to 8.11.3.
  • acorn-walk updated to 8.3.2.
  • ada updated to 2.7.8.
  • c-ares updated to 1.28.1.
  • corepack updated to 0.28.0.
  • nghttp2 updated to 1.61.0.
  • ngtcp2 updated to 1.3.0.
  • npm updated to 10.7.0. Includes a fix from [email protected] to limit the number of open connections npm/cli#7324.
  • simdutf updated to 5.2.4.
  • zlib updated to 1.3.0.1-motley-7d77fb7.
Commits

v18.20.2: 2024-04-10, Version 18.20.2 'Hydrogen' (LTS), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes
  • CVE-2024-27980 - Command injection via args parameter of child_process.spawn without shell option enabled on Windows
Commits

v18.20.1

Compare Source

v18.20.0

Compare Source

v18.19.1

Compare Source

v18.19.0

Compare Source

v18.18.2

Compare Source

v18.18.1: 2023-10-10, Version 18.18.1 'Hydrogen' (LTS), @​richardlau

Compare Source

Notable Changes

This release addresses some regressions that appeared in Node.js 18.18.0:

  • (Windows) FS can not handle certain characters in file name #​48673
  • 18 and 20 node images give error - Text file busy (after re-build images) nodejs/docker-node#1968
  • libuv update in 18.18.0 breaks webpack's thread-loader #​49911

The libuv 1.45.0 and 1.46.0 updates that were released in Node.js 18.18.0 have been temporarily reverted.

Commits

v18.18.0: 2023-09-18, Version 18.18.0 'Hydrogen' (LTS), @​ruyadorno

Compare Source

Notable Changes
Commits

Configuration

📅 Schedule: Branch creation - "after 3am and before 10pm" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Updating dependencies label Aug 9, 2023
@renovate renovate bot changed the title chore(deps): update dependency node to v18.17.1 chore(deps): update all non-major dependencies Aug 10, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c5f9418 to 8cd3ab3 Compare August 10, 2023 06:42
@renovate
Copy link
Contributor Author

renovate bot commented Aug 10, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @outreach/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"21.1.2" from the root project
npm ERR!   peer semantic-release@">=18.0.0" from @semantic-release/[email protected]
npm ERR!   node_modules/@semantic-release/changelog
npm ERR!     dev @semantic-release/changelog@"6.0.3" from the root project
npm ERR!   5 more (@semantic-release/commit-analyzer, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=19.0.0 <20.0.0" from @outreach/[email protected]
npm ERR! node_modules/@outreach/semantic-release-circleci-orb
npm ERR!   dev @outreach/semantic-release-circleci-orb@"^1.1.9" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   peer semantic-release@">=19.0.0 <20.0.0" from @outreach/[email protected]
npm ERR!   node_modules/@outreach/semantic-release-circleci-orb
npm ERR!     dev @outreach/semantic-release-circleci-orb@"^1.1.9" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-07T21_32_11_727Z-debug-0.log

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 95bf265 to 63dd974 Compare August 24, 2023 20:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 63dd974 to a93f393 Compare September 5, 2023 12:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from c6d7ec0 to f4f4cb9 Compare September 19, 2023 19:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 77c96c3 to 9b70099 Compare October 5, 2023 19:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 360eeb9 to 5c77c6e Compare October 14, 2023 16:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from ff3e49f to b45afbf Compare October 26, 2023 21:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 0bd0e8c to 98ff8e8 Compare November 29, 2023 19:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 98ff8e8 to a64944f Compare January 10, 2024 21:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a64944f to 8240fc2 Compare February 14, 2024 19:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from fa7e25b to df55952 Compare March 27, 2024 21:21
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from df55952 to 915e0bd Compare April 3, 2024 15:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 915e0bd to 311a936 Compare April 10, 2024 17:10
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 311a936 to c961930 Compare May 7, 2024 21:32
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c961930 to 11802a0 Compare May 21, 2024 18:55
Copy link
Contributor Author

renovate bot commented May 21, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @outreach/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"21.1.2" from the root project
npm ERR!   peer semantic-release@">=18.0.0" from @semantic-release/[email protected]
npm ERR!   node_modules/@semantic-release/changelog
npm ERR!     dev @semantic-release/changelog@"6.0.3" from the root project
npm ERR!   5 more (@semantic-release/commit-analyzer, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=19.0.0 <20.0.0" from @outreach/[email protected]
npm ERR! node_modules/@outreach/semantic-release-circleci-orb
npm ERR!   dev @outreach/semantic-release-circleci-orb@"^1.1.9" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   peer semantic-release@">=19.0.0 <20.0.0" from @outreach/[email protected]
npm ERR!   node_modules/@outreach/semantic-release-circleci-orb
npm ERR!     dev @outreach/semantic-release-circleci-orb@"^1.1.9" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-10-04T13_56_08_709Z-debug-0.log

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 11802a0 to 87d30b2 Compare May 29, 2024 13:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 87d30b2 to f95cfd5 Compare June 21, 2024 18:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f95cfd5 to 92bb8b0 Compare July 9, 2024 18:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 92bb8b0 to 26eba96 Compare July 24, 2024 17:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 26eba96 to 449152d Compare August 22, 2024 17:18
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 449152d to b0c1c0a Compare September 11, 2024 16:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b0c1c0a to 267c4f2 Compare October 4, 2024 13:56
Copy link
Contributor Author

renovate bot commented Oct 16, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Updating dependencies
Development

Successfully merging this pull request may close these issues.

0 participants