Skip to content

chore: bump lycheeverse/lychee-action from 2.7.0 to 2.8.0 in /.github/workflows#154

Merged
lirantal merged 1 commit intomainfrom
dependabot/github_actions/dot-github/workflows/lycheeverse/lychee-action-2.8.0
Mar 1, 2026
Merged

chore: bump lycheeverse/lychee-action from 2.7.0 to 2.8.0 in /.github/workflows#154
lirantal merged 1 commit intomainfrom
dependabot/github_actions/dot-github/workflows/lycheeverse/lychee-action-2.8.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 1, 2026

Bumps lycheeverse/lychee-action from 2.7.0 to 2.8.0.

Release notes

Sourced from lycheeverse/lychee-action's releases.

v2.8.0

What's Changed

New Contributors

Full Changelog: lycheeverse/lychee-action@v2.7.0...v2.8.0

Commits
  • 8646ba3 Add message with Summary report URL (#326)
  • c6e7911 [create-pull-request] automated change
  • 631725a Bump peter-evans/create-pull-request from 7 to 8 (#318)
  • 942f324 Bump actions/cache from 4 to 5 (#319)
  • 79de881 Bump actions/checkout from 5 to 6 (#316)
  • 1ef33e2 Update test to use --root-dir instead of the deprecated --base (#315)
  • 50a631e Update args for lychee-action to use root-dir (#314)
  • See full diff in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 1, 2026
Bumps [lycheeverse/lychee-action](https://github.com/lycheeverse/lychee-action) from 2.7.0 to 2.8.0.
- [Release notes](https://github.com/lycheeverse/lychee-action/releases)
- [Commits](lycheeverse/lychee-action@a8c4c7c...8646ba3)

---
updated-dependencies:
- dependency-name: lycheeverse/lychee-action
  dependency-version: 2.8.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the github_actions Pull requests that update GitHub Actions code label Mar 1, 2026
@dependabot dependabot bot requested a review from lirantal as a code owner March 1, 2026 12:08
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Mar 1, 2026
@github-actions github-actions bot added the build label Mar 1, 2026
@lirantal
Copy link
Owner

lirantal commented Mar 1, 2026

@copilot how do we fix the breaking CI issue with eslint here?

Run npm ci
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: neostandard@0.12.2
npm error Found: eslint@10.0.1
npm error node_modules/eslint
npm error   dev eslint@"^10.0.1" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.9.0
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.7.0" from @typescript-eslint/utils@8.38.0
npm error     node_modules/@stylistic/eslint-plugin/node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"^8.13.0" from @stylistic/eslint-plugin@2.11.0
npm error       node_modules/@stylistic/eslint-plugin
npm error         @stylistic/eslint-plugin@"2.11.0" from neostandard@0.12.2
npm error         node_modules/neostandard
npm error     @eslint-community/eslint-utils@"^4.8.0" from eslint@10.0.1
npm error     4 more (eslint-plugin-es-x, eslint-plugin-n, ...)
npm error   5 more (@stylistic/eslint-plugin, eslint-compat-utils, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^9.0.0" from neostandard@0.12.2
npm error node_modules/neostandard
npm error   dev neostandard@"^0.12.1" from the root project
npm error
npm error Conflicting peer dependency: eslint@9.39.3
npm error node_modules/eslint
npm error   peer eslint@"^9.0.0" from neostandard@0.12.2
npm error   node_modules/neostandard
npm error     dev neostandard@"^0.12.1" 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 /home/runner/.npm/_logs/2026-03-01T12_08_11_546Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-03-01T12_08_11_546Z-debug-0.log
Error: Process completed with exit code 1.

Copy link
Contributor

Copilot AI commented Mar 1, 2026

@lirantal I've opened a new pull request, #155, to work on those changes. Once the pull request is ready, I'll request review from you.

@lirantal lirantal merged commit dfcd4c0 into main Mar 1, 2026
9 of 11 checks passed
@dependabot dependabot bot deleted the dependabot/github_actions/dot-github/workflows/lycheeverse/lychee-action-2.8.0 branch March 1, 2026 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants