Skip to content
This repository was archived by the owner on Aug 22, 2024. It is now read-only.

chore(deps): update external major (major)#28

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate-major-external-major
Open

chore(deps): update external major (major)#28
renovate[bot] wants to merge 1 commit intomainfrom
renovate-major-external-major

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jul 24, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@semantic-release/npm 9.0.2 -> 12.0.1 age adoption passing confidence devDependencies major
actions/checkout v3 -> v4 age adoption passing confidence action major
actions/setup-node v3 -> v4 age adoption passing confidence action major
aws-sdk-client-mock ^3.0.0 -> ^4.0.0 age adoption passing confidence devDependencies major
c8 7.14.0 -> 10.1.2 age adoption passing confidence devDependencies major
codecov 3.3.0 -> 4.1.0 age adoption passing confidence orb major
eslint (source) 8.57.0 -> 9.9.0 age adoption passing confidence devDependencies major
github/codeql-action v2 -> v3 age adoption passing confidence action major
husky 8.0.3 -> 9.1.4 age adoption passing confidence devDependencies major
lint-staged 13.3.0 -> 15.2.9 age adoption passing confidence devDependencies major
node-fetch ^2.6.11 -> ^3.0.0 age adoption passing confidence dependencies major
semantic-release ^19.0.2 -> ^24.0.0 age adoption passing confidence devDependencies major
semantic-release-monorepo 7.0.8 -> 8.0.2 age adoption passing confidence devDependencies major
sinon (source) ^15.2.0 -> ^18.0.0 age adoption passing confidence devDependencies major

Release Notes

semantic-release/npm (@​semantic-release/npm)

v12.0.1

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (9ac5ed0)

v12.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (9e193c2)
  • node-versions: dropped support for node v18 and v19 (2df962b)
BREAKING CHANGES
  • exports: exports has been defined, which prevents access to private apis (which arent
    intended for consumption anyway)
  • node-versions: node v18 and v19 are no longer supported

v11.0.3

Compare Source

Bug Fixes

even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully

v11.0.2

Compare Source

Bug Fixes
  • deps: update dependency npm to v10.2.5 (42b5dec)

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

Bug Fixes
  • deps: update dependency npm to v10 (819f257)
Features
  • node-versions: raised the minimum required node version to v18.17 and dropped v19 support (6413130)
BREAKING CHANGES
  • node-versions: node v18.17 is now the minimum required version and support for v19 has been dropped

v10.0.6

Compare Source

Bug Fixes

v10.0.5

Compare Source

Bug Fixes

v10.0.4

Compare Source

Bug Fixes

v10.0.3

Compare Source

Bug Fixes

v10.0.2

Compare Source

Bug Fixes

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Bug Fixes
  • aggregate-error: upgraded to the latest version (7285e05)
  • deps: upgraded npm to v9 (2a79f80)
  • execa: upgraded to the latest version (7c74660)
  • normalize-url: upgraded to the latest version (b55bb01)
  • remove support for legacy auth (51ab3c8)
  • tempy: upgraded to the latest version of tempy (f1992a5)
Code Refactoring
  • esm: converted the package to esm (2d8ff15)
Features
  • node-versions: dropped support for node versions below v18 (aff3574)
  • semantic-release-peer: raised the minimum peer requirement to the first version that supports loading esm plugins (22e70ad)
BREAKING CHANGES
  • deps: the direct dependency on npm has been upgraded to v9. details of breaking changes
    can be found at https://github.com/npm/cli/releases/tag/v9.0.0
  • semantic-release-peer: the required version of semantic-release has been
    raised to v20.1.0 in order to support loading of ESM plugins
  • aggregate-error: due to the aggregate-error upgrade, thrown errors are no longer iterable, but instead list the errors under an errors property
  • legacy authentication using NPM_USERNAME and NPM_PASSWORD is no longer supported. Use NPM_TOKEN instead.
  • node-versions: node v18 is now the minimum required node version
  • esm: @semantic-release/npm is now a native ES Module. It
    has named exports for each plugin hook (verifyConditions, prepare,
    publish, addChannel)
actions/checkout (actions/checkout)

v4

Compare Source

actions/setup-node (actions/setup-node)

v4

Compare Source

m-radzikowski/aws-sdk-client-mock (aws-sdk-client-mock)

v4.0.1

Compare Source

v4.0.0

Compare Source

bcoe/c8 (c8)

v10.1.2

Compare Source

Bug Fixes
  • deps: make monocart-coverage-reports an optional with meta defined (3b91fda)

v10.1.1

Compare Source

Bug Fixes

v10.1.0

Compare Source

Features

v10.0.0

Compare Source

⚠ BREAKING CHANGES
  • deps: Node 18 is now the minimum supported Node.js version
Bug Fixes
  • deps: update test-exclude with new glob / minimatch (#​531) (e33cf30)

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)

v8.0.1

Compare Source

Bug Fixes

v8.0.0

Compare Source

⚠ BREAKING CHANGES
  • dropped Node 10 support (#​475)
Miscellaneous Chores
eslint/eslint (eslint)

v9.9.0

Compare Source

Features

  • 41d0206 feat: Add support for TS config files (#​18134) (Arya Emami)
  • 3a4eaf9 feat: add suggestion to require-await to remove async keyword (#​18716) (Dave)

Documentation

  • 9fe068c docs: how to author plugins with configs that extend other configs (#​18753) (Alec Gibson)
  • 48117b2 docs: add version support page in the side navbar (#​18738) (Amaresh S M)
  • fec2951 docs: add version support page to the dropdown (#​18730) (Amaresh S M)
  • 38a0661 docs: Fix typo (#​18735) (Zaina Al Habash)
  • 3c32a9e docs: Update yarn command for creating ESLint config (#​18739) (Temitope Ogunleye)
  • f9ac978 docs: Update README (GitHub Actions Bot)

Chores

v9.8.0

Compare Source

v9.7.0

Compare Source

Features

  • 7bd9839 feat: add support for es2025 duplicate named capturing groups (#​18630) (Yosuke Ota)
  • 1381394 feat: add regex option in no-restricted-imports (#​18622) (Nitin Kumar)

Bug Fixes

  • 14e9f81 fix: destructuring in catch clause in no-unused-vars (#​18636) (Francesco Trotta)

Documentation

  • 9f416db docs: Add Powered by Algolia label to the search. (#​18633) (Amaresh S M)
  • c8d26cb docs: Open JS Foundation -> OpenJS Foundation (#​18649) (Milos Djermanovic)
  • 6e79ac7 docs: loadESLint does not support option cwd (#​18641) (Francesco Trotta)

Chores

v9.6.0

Compare Source

v9.5.0

Compare Source

v9.4.0

Compare Source

v9.3.0

Compare Source

v9.2.0

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

v9.0.0

Compare Source

github/codeql-action (github/codeql-action)

v3

Compare Source

typicode/husky (husky)

v9.1.4

Compare Source

v9.1.3

Compare Source

  • fix: better handle space in PATH

v9.1.2

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

Super saiyan god dog! It's over 9.0.0!

There's a bug with this release which prevents the deprecation notice to appear and requires to remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" (which are deprecated by the way). I'll publish a new version to fix that. Sorry about any inconvenience.

What's new

You can now run package commands directly, no need for npx or equivalents.
It makes writing hooks more intuitive and is also slightly faster 🐺⚡️

### .husky/pre-commit
- npx jest
+ jest # ~0.2s faster

A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.

### .husky/pre-commit
prettier $(git diff --cached --name-only --diff-filter=ACMR | sed 's| |\\ |g') --write --ignore-unknown
git update-index --again

For more advanced use cases, see lint-staged.

Fixes

  • bunx husky init command
  • Workaround for some hooks implementation on Windows 🤷

Deprecations

  • Remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" from your hooks
  • Move your code from ~/.huskyrc to .config/husky/init.sh

Support for these will be removed in v10, notices have been added.

Friendly reminder

If Git hooks don't fit your workflow, you can disable Husky globally. Just add export HUSKY=0 to .config/husky/init.sh.

I've seen some confusion about this on X, so just a heads-up!

Sponsoring

Husky is downloaded over 45M times per month and used by ~1.5M projects. If your company wants to sponsor, you can do so here: GitHub Sponsors.

Have a nice summer ☀️ I'm open to new opportunities/consulting so feel free to drop me a message 😉

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
lint-staged/lint-staged (lint-staged)

v15.2.9

Compare Source

Patch Changes
  • #​1463 b69ce2d Thanks @​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning MaxListenersExceededWarning: Possible EventEmitter memory leak detected.

v15.2.8

Compare Source

Patch Changes

  • f0480f0 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version switched the --show-toplevel flag with --show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js child_process. The new flag returns a path relative to the working directory, avoiding the issue.

    The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.

v15.2.7

Compare Source

Patch Changes
  • #​1440 a51be80 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.

v15.2.6

Compare Source

Patch Changes
  • #​1433 119adb2 Thanks @​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.

v15.2.5

Compare Source

Patch Changes

  • #​1424 31a1f95 Thanks @​iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.

  • #​1423 91abea0 Thanks @​iiroj! - Improve error logging when failing to read or parse a configuration file

  • #​1424 ee43f15 Thanks @​iiroj! - Upgrade micromatch@4.0.7

v15.2.4

Compare Source

Patch Changes
  • 4f4537a Thanks @​iiroj! - Fix release issue with previous version; update dependencies

v15.2.2

Compare Source

Patch Changes
  • #​1391 fdcdad4 Thanks @​iiroj! - Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.

v15.2.1

Compare Source

Patch Changes
  • #​1387 e4023f6 Thanks @​iiroj! - Ignore stdin of spawned commands so that they don't get stuck waiting. Until now, lint-staged has used the default settings to spawn linter commands. This means the stdin of the spawned commands has accepted input, and essentially gotten stuck waiting. Now the stdin is ignored and commands will no longer get stuck. If you relied on this behavior, please open a new issue and describe how; the behavior has not been intended.

v15.2.0

Compare Source

Minor Changes
  • #​1371 f3378be Thanks @​iiroj! - Using the --no-stash flag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag --no-hide-partially-staged that is automatically enabled when --no-stash is used.
Patch Changes

  • #​1362 17bc480 Thanks @​antonk52! - update lilconfig@3.0.0

  • #​1368 7c55ca9 Thanks @​iiroj! - Update most dependencies

  • #​1368 777d4e9 Thanks @​iiroj! - To improve performance, only use lilconfig when searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.

  • #​1373 85eb0dd Thanks @​iiroj! - When determining git directory, use fs.realpath() only for symlinks. It looks like fs.realpath() changes some Windows mapped network filepaths unexpectedly, causing issues.

v15.1.0

Compare Source

Minor Changes
Patch Changes

v15.0.2

Compare Source

Patch Changes
  • #​1339 8e82364 Thanks @​iiroj! - Update dependencies, including listr2@​7.0.2 to fix an upstream issue affecting lint-staged.

v15.0.1

Compare Source

Patch Changes
  • #​1217 d2e6f8b Thanks @​louneskmt! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead.

v15.0.0

Compare Source

Major Changes

  • #​1322 66b93aa Thanks @​iiroj! - Require at least Node.js 18.12.0

    This release drops support for Node.js 16, which is EOL after 2023-09-11.
    Please upgrade your Node.js to the latest version.

    Additionally, all dependencies have been updated to their latest versions.

v14.0.1

Compare Source

Bug Fixes
  • fix reading config from stdin, introduced in v14.0.0 (#​1317) (fc3bfea)

v14.0.0

Compare Source

Features
BREAKING CHANGES
  • Please upgrade your Node.js version to at least 16.14.0.
node-fetch/node-fetch (node-fetch)

v3.3.2

Compare Source

Bug Fixes

v3.3.1

Compare Source

Bug Fixes

v3.3.0

Compare Source

Features

v3.2.10

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - "after 2pm on Monday" in timezone Europe/Zurich, 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.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jul 24, 2023

This PR will trigger no release when merged.

@codecov
Copy link
Copy Markdown

codecov Bot commented Jul 24, 2023 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (5748959) to head (883c060).

❗ Current head 883c060 differs from pull request most recent head 173f0b0

Please upload reports for the commit 173f0b0 to get more accurate results.

Additional details and impacted files 
@@            Coverage Diff            @@
##              main       #28   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            9         9           
  Lines         1330      1330           
=========================================
  Hits          1330      1330

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate Bot force-pushed the renovate-major-external-major branch 7 times, most recently from f3589d2 to c87c846 Compare July 31, 2023 20:07
@renovate renovate Bot force-pushed the renovate-major-external-major branch 7 times, most recently from 05c3cab to 7c21d55 Compare August 12, 2023 15:22
@renovate renovate Bot force-pushed the renovate-major-external-major branch 9 times, most recently from e9ae41a to 7556ee6 Compare August 19, 2023 16:45
@renovate renovate Bot force-pushed the renovate-major-external-major branch 2 times, most recently from 4b9ffd3 to 6aa0784 Compare August 26, 2023 16:32
@renovate renovate Bot force-pushed the renovate-major-external-major branch 3 times, most recently from f8ebe30 to 584d210 Compare September 6, 2023 20:40
@renovate renovate Bot force-pushed the renovate-major-external-major branch 2 times, most recently from c5fbd74 to d83f126 Compare October 28, 2023 16:13
@renovate renovate Bot force-pushed the renovate-major-external-major branch 2 times, most recently from b4393b7 to 86afb28 Compare November 4, 2023 18:39
@renovate renovate Bot force-pushed the renovate-major-external-major branch 2 times, most recently from 985bea0 to 628bdb5 Compare November 11, 2023 18:41
@renovate renovate Bot force-pushed the renovate-major-external-major branch from 628bdb5 to fa9a23f Compare November 18, 2023 15:57
@renovate renovate Bot force-pushed the renovate-major-external-major branch 2 times, most recently from 6417b00 to aeb2265 Compare December 2, 2023 16:07
@renovate renovate Bot force-pushed the renovate-major-external-major branch 3 times, most recently from bf5fd84 to ef46ca0 Compare December 9, 2023 19:16
@renovate renovate Bot force-pushed the renovate-major-external-major branch 2 times, most recently from 3adb091 to 6ba4ed1 Compare December 16, 2023 16:12
@renovate renovate Bot force-pushed the renovate-major-external-major branch 2 times, most recently from 0962605 to bc6e6cd Compare December 30, 2023 15:18
@renovate renovate Bot force-pushed the renovate-major-external-major branch 2 times, most recently from d324737 to 6e37f86 Compare January 6, 2024 19:29
@renovate renovate Bot force-pushed the renovate-major-external-major branch 4 times, most recently from 6586f23 to b107251 Compare January 17, 2024 17:15
@renovate renovate Bot force-pushed the renovate-major-external-major branch 5 times, most recently from 96147ff to b063b23 Compare January 25, 2024 14:24
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 5, 2024 •
edited
Loading

⚠ 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @adobe/eslint-config-helix@2.0.2
npm error Found: eslint@9.2.0
npm error node_modules/eslint
npm error   dev eslint@"9.2.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from eslint@9.2.0
npm error   2 more (eslint-import-resolver-exports, eslint-plugin-header)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.0.0" from @adobe/eslint-config-helix@2.0.2
npm error node_modules/@adobe/eslint-config-helix
npm error   dev @adobe/eslint-config-helix@"2.0.2" from the root project
npm error
npm error Conflicting peer dependency: eslint@8.57.0
npm error node_modules/eslint
npm error   peer eslint@"^8.0.0" from @adobe/eslint-config-helix@2.0.2
npm error   node_modules/@adobe/eslint-config-helix
npm error     dev @adobe/eslint-config-helix@"2.0.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-03T21_56_28_596Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-03T21_56_28_596Z-debug-0.log

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 9, 2024 •
edited
Loading

⚠️ 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @adobe/eslint-config-helix@2.0.2
npm error Found: eslint@9.9.0
npm error node_modules/eslint
npm error   dev eslint@"9.9.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from eslint@9.9.0
npm error   2 more (eslint-import-resolver-exports, eslint-plugin-header)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.0.0" from @adobe/eslint-config-helix@2.0.2
npm error node_modules/@adobe/eslint-config-helix
npm error   dev @adobe/eslint-config-helix@"2.0.2" from the root project
npm error
npm error Conflicting peer dependency: eslint@8.57.0
npm error node_modules/eslint
npm error   peer eslint@"^8.0.0" from @adobe/eslint-config-helix@2.0.2
npm error   node_modules/@adobe/eslint-config-helix
npm error     dev @adobe/eslint-config-helix@"2.0.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-08-13T09_04_38_191Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-08-13T09_04_38_191Z-debug-0.log

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

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.

0 participants