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

fix(deps): update all (major) #1128

Merged
merged 8 commits into from
Apr 5, 2024
Merged

fix(deps): update all (major) #1128

merged 8 commits into from
Apr 5, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 30, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@adyen/api-library 15.1.0 -> 16.2.0 age adoption passing confidence
c8 8.0.1 -> 9.1.0 age adoption passing confidence
chai (source) 4.4.1 -> 5.1.0 age adoption passing confidence
husky 8.0.3 -> 9.0.11 age adoption passing confidence
ip 1.1.9 -> 2.0.1 age adoption passing confidence
puppeteer (source) 21.11.0 -> 22.6.2 age adoption passing confidence

Release Notes

Adyen/adyen-node-api-library (@​adyen/api-library)

v16.2.0: Adyen Node API Library v16.2.0

Compare Source

What's Changed

New Features 💎
Fixes ⛑️
Other Changes 🖇️

Full Changelog: Adyen/adyen-node-api-library@v16.1.0...v16.2.0

v16.1.0: Adyen Node API Library v16.1.0

Compare Source

What's Changed

New Features 💎
Other Changes 🖇️
Classname change and some field name changes ⚠️
  • Changed from PINFunctionalityApi to ManageCardPINApi

Full Changelog: Adyen/adyen-node-api-library@v16.0.2...v16.1.0

v16.0.2: Adyen Node API Library v16.0.2

Compare Source

What's Changed

Other Changes 🖇️

Full Changelog: Adyen/adyen-node-api-library@v16.0.1...v16.0.2

v16.0.1: Adyen Node API Library v16.0.1

Compare Source

What's Changed

Other Changes 🖇️

New Contributors

Full Changelog: Adyen/adyen-node-api-library@v16.0.0...v16.0.1

v16.0.0: Adyen Node API Library v16.0.0

Compare Source

What's Changed

Breaking Changes 🛠
Donations has moved

The Checkout Donations endpoint, which was previously on the PaymentsApi, has been moved to its own service called DonationsApi.

add query parameters to function arguments

Previously these had to be sent through the requestOptions argument. We now have added function arguments, which is less prone to mistakes, and clearly indicates all the options.
This does mean that current implementations using requestOptions for query parameters have to be adjusted slightly to accommodate for these new function parameters.

Other Changes 🖇️

Full Changelog: Adyen/adyen-node-api-library@v15.1.0...v16.0.0

bcoe/c8 (c8)

v9.1.0

Compare Source

Features
Bug Fixes
  • refactor: remove stale check for createDynamicModule (5e18365)

v9.0.0

Compare Source

⚠ BREAKING CHANGES
  • build: minimum Node.js version is now 14.14.0
Features
  • build: minimum Node.js version is now 14.14.0 (2cdc86b)
  • deps: update foreground-child to promise API (#​512) (b46b640)
  • deps: use Node.js built in rm (2cdc86b)
chaijs/chai (chai)

v5.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.0.3...v5.1.0

v5.0.3

Compare Source

Fix bad v5.0.2 publish.

Full Changelog: chaijs/chai@v5.0.2...v5.0.3

v5.0.2

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.0.1...v5.0.2

v5.0.0

Compare Source

BREAKING CHANGES

  • Chai now only supports EcmaScript Modules (ESM). This means your tests will need to either have import {...} from 'chai' or import('chai'). require('chai') will cause failures in nodejs. If you're using ESM and seeing failures, it may be due to a bundler or transpiler which is incorrectly converting import statements into require calls.
  • Dropped support for Internet Explorer.
  • Dropped support for NodeJS < 18.
  • Minimum supported browsers are now Firefox 100, Safari 14.1, Chrome 100, Edge 100. Support for browsers prior to these versions is "best effort" (bug reports on older browsers will be assessed individually and may be marked as wontfix).

What's Changed

New Contributors

Full Changelog: chaijs/chai@4.3.1...v5.0.0

typicode/husky (husky)

v9.0.11

Compare Source

v9.0.10

Compare Source

v9.0.9

Compare Source

v9.0.8

Compare Source

v9.0.7

Compare Source

v9.0.6

Compare Source

v9.0.5

Compare Source

v9.0.4

Compare Source

v9.0.3

Compare Source

v9.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.0.1...v9.0.2

v9.0.1

Compare Source

Kicking off the year with an exciting update!

TLDR;

Improved user experience and a (even) smaller package size while packing in more features!

👋 By the Way

I'm available for remote work (Front-end/Back-end mainly JS/TS but open to other stacks Rails, Go, Elixir). You can contact me at my mail: typicode at gmail 🙂

Introducing husky init

Adding husky to a project is now easier than ever. Although the installation process was straightforward, it often required consulting the documentation.

v8
npm pkg set scripts.prepare="husky install"
npm run prepare
npx husky add .husky/pre-commit "npm test"
v9
npx husky init

Adding a New Hook

Adding a hook is now as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic echo command.

v8
npx husky add  .husky/pre-commit "npm test"
git add --chmod=+x .husky/pre-commit # On Windows
v9
echo "npm test" > .husky/pre-commit

Further Size Reduction

v8 was already the most compact Git hooks manager at approximately 6kB.

v9 takes this a step further, reducing the size to just 3kB, likely making it the smallest devDependency in your toolkit.

To give you an idea of how small it is, the biggest file in the project is the MIT license 😄

More to Come

Additional features are in the pipeline for v9. Stay tuned 🙌

Other Changes

  • Enhanced security with CI and npm --provenance for safer publishing.
  • Added $XDG_CONFIG_HOME support. Move ~/.huskyrc to ~/.config/husky/init.sh for centralized configuration.
  • Fixed permission issue for Windows-created hooks; they no longer need to be executable.
  • Removed husky install. Use husky or husky some/dir for the same functionality (deprecation notice to be added).
  • Modified behavior when .git is missing; it now triggers a warning instead of failure.
  • Replaced HUSKY_DEBUG=1 with HUSKY=2 for debugging.
  • Updated the Husky API for module usage.
  • Transitioned to ESM for module usage.
  • Dropped support for Node 14 and 16.
  • Revamped docs.

How to Migrate

v9 is backward compatible with v8, allowing you to freely upgrade and migrate your hooks later.

package.json

{
  "scripts": {
-   "prepare": "husky install"
+   "prepare": "husky"
  }
}

.husky/pre-commit

- #!/usr/bin/env sh
- . "$(dirname -- "$0")/_/husky.sh"
npm test
indutny/node-ip (ip)

v2.0.1

Compare Source

v2.0.0

Compare Source

puppeteer/puppeteer (puppeteer)

v22.6.2: puppeteer-core: v22.6.2

Compare Source

Bug Fixes

v22.6.1

Compare Source

v22.6.0

Compare Source

v22.5.0: puppeteer: v22.5.0

Compare Source

Miscellaneous Chores
  • puppeteer: Synchronize puppeteer versions
Dependencies
  • The following workspace dependencies were updated

v22.4.1: puppeteer: v22.4.1

Compare Source

Miscellaneous Chores
  • puppeteer: Synchronize puppeteer versions
Dependencies
  • The following workspace dependencies were updated
    • dependencies
      • puppeteer-core bumped from 22.4.0 to 22.4.1

v22.4.0: puppeteer-core: v22.4.0

Compare Source

Features
Bug Fixes
  • roll to Chrome 122.0.6261.94 (r1250580) (#​12012) (7ba5529)
  • webdriver: wait for response if the response has not completed once navigation has finished (#​12018) (6d8831a)

v22.3.0: puppeteer: v22.3.0

Compare Source

Miscellaneous Chores
  • puppeteer: Synchronize puppeteer versions
Dependencies
  • The following workspace dependencies were updated
    • dependencies
      • puppeteer-core bumped from 22.2.0 to 22.3.0

v22.2.0: puppeteer: v22.2.0

Compare Source

Features
Dependencies
  • The following workspace dependencies were updated

v22.1.0: puppeteer: v22.1.0

Compare Source

Miscellaneous Chores
  • puppeteer: Synchronize puppeteer versions
Dependencies
  • The following workspace dependencies were updated

v22.0.0: puppeteer: v22.0.0

Compare Source

⚠ BREAKING CHANGES
  • remove PUPPETEER_DOWNLOAD_PATH in favor of PUPPETEER_CACHE_DIR (#​11605)
  • drop support for node16 (#​10912)
Features
Dependencies
  • The following workspace dependencies were updated

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

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

Copy link
Contributor Author

renovate bot commented Dec 30, 2023

⚠ Artifact update problem

Renovate failed to update artifacts 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: notification/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/chai
npm ERR!   dev chai@"5.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer chai@">= 2.1.2 < 5" from [email protected]
npm ERR! node_modules/chai-as-promised
npm ERR!   dev chai-as-promised@"7.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/chai
npm ERR!   peer chai@">= 2.1.2 < 5" from [email protected]
npm ERR!   node_modules/chai-as-promised
npm ERR!     dev chai-as-promised@"7.1.1" 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-04-04T11_40_00_698Z-debug-0.log

File name: extension/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/chai
npm ERR!   dev chai@"5.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer chai@">= 2.1.2 < 5" from [email protected]
npm ERR! node_modules/chai-as-promised
npm ERR!   dev chai-as-promised@"7.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/chai
npm ERR!   peer chai@">= 2.1.2 < 5" from [email protected]
npm ERR!   node_modules/chai-as-promised
npm ERR!     dev chai-as-promised@"7.1.1" 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-04-04T11_40_08_106Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-all branch from 7b72b2f to 18497ab Compare January 3, 2024 19:04
@renovate renovate bot changed the title chore(deps): update dependency chai to v5 chore(deps): update all (major) Jan 3, 2024
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from e39fca9 to 618c441 Compare January 9, 2024 13:32
@renovate renovate bot force-pushed the renovate/major-all branch 4 times, most recently from 3d8c510 to ad84d13 Compare January 17, 2024 07:58
@renovate renovate bot force-pushed the renovate/major-all branch 8 times, most recently from a6e87c5 to cef0c48 Compare January 26, 2024 02:36
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from 588747c to 9db7324 Compare January 31, 2024 12:49
@renovate renovate bot changed the title chore(deps): update all (major) fix(deps): update all (major) Jan 31, 2024
@renovate renovate bot force-pushed the renovate/major-all branch 5 times, most recently from dadfecd to 3930c9e Compare February 8, 2024 13:58
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from 9eb6c3e to c99d8e1 Compare February 17, 2024 13:29
@renovate renovate bot force-pushed the renovate/major-all branch 5 times, most recently from 0f2275c to 6ab6dc0 Compare February 24, 2024 03:32
@renovate renovate bot force-pushed the renovate/major-all branch from 6ab6dc0 to 02ce30c Compare February 26, 2024 10:23
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 1d4c70d to 414a952 Compare March 8, 2024 13:35
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from eb05a2b to 3b64341 Compare March 22, 2024 17:58
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from 4b94802 to 46a785e Compare March 27, 2024 11:57
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 83379af to 3c57f76 Compare April 3, 2024 15:45
@renovate renovate bot force-pushed the renovate/major-all branch from 3c57f76 to 9da443f Compare April 4, 2024 11:40
MarijaIv added 3 commits April 5, 2024 09:38
…e/major-all

# Conflicts:
#	extension/package-lock.json
#	extension/package.json
#	notification/package-lock.json
#	notification/package.json
Copy link
Contributor Author

renovate bot commented Apr 5, 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.

@MarijaIv MarijaIv merged commit 8da0812 into master Apr 5, 2024
5 checks passed
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.

1 participant