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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update all non-major dependencies #3

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

chore(deps): update all non-major dependencies #3

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 2, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@astrojs/image (source) 0.17.2 -> 0.18.0 age adoption passing confidence devDependencies minor
@astrojs/react (source) 2.2.1 -> 2.3.2 age adoption passing confidence devDependencies minor
@floating-ui/dom (source) 1.4.4 -> 1.6.12 age adoption passing confidence dependencies minor
@percy/cli (source) 1.26.2 -> 1.30.2 age adoption passing confidence devDependencies minor
@​types/marked 5.0.0 -> 5.0.2 age adoption passing confidence devDependencies patch
CliWrap 3.6.6 -> 3.6.7 age adoption passing confidence nuget patch
Nuke.Common (source) 8.0.0 -> 8.1.4 age adoption passing confidence nuget minor
astro (source) 2.8.0 -> 2.10.15 age adoption passing confidence devDependencies minor
astro-compress 2.2.28 -> 2.3.5 age adoption passing confidence devDependencies minor
auto-changelog 2.4.0 -> 2.5.0 age adoption passing confidence dependencies minor
broken-link-checker 0.6.7 -> 0.7.8 age adoption passing confidence dependencies minor
concurrently 8.2.0 -> 8.2.2 age adoption passing confidence devDependencies patch
cspell (source) 8.9.1 -> 8.16.0 age adoption passing confidence devDependencies minor
czg (source) 1.9.3 -> 1.11.0 age adoption passing confidence dependencies minor
favicons 7.1.3 -> 7.2.0 age adoption passing confidence devDependencies minor
gregoranders/nodejs-project-info v0.0.20 -> v0.0.21 age adoption passing confidence action patch
husky 9.0.11 -> 9.1.7 age adoption passing confidence devDependencies minor
immer 10.0.2 -> 10.1.1 age adoption passing confidence devDependencies minor
marked (source) 5.1.1 -> 5.1.2 age adoption passing confidence devDependencies patch
nerdbank-gitversioning 3.6.139 -> 3.6.146 age adoption passing confidence dependencies patch
photoswipe (source) 5.3.8 -> 5.4.4 age adoption passing confidence devDependencies minor
postcss (source) 8.4.38 -> 8.4.49 age adoption passing confidence devDependencies patch
prettier-plugin-astro 0.10.0 -> 0.14.1 age adoption passing confidence devDependencies minor
prettier-plugin-tailwindcss 0.3.0 -> 0.6.8 age adoption passing confidence devDependencies minor
puppeteer (source) 22.11.2 -> 22.15.0 age adoption passing confidence devDependencies minor
reedyuk/npm-version 1.2.1 -> 1.2.2 age adoption passing confidence action patch
rollup-plugin-visualizer 5.9.2 -> 5.12.0 age adoption passing confidence devDependencies minor
tailwindcss (source) 3.3.2 -> 3.4.15 age adoption passing confidence devDependencies minor
ts-node (source) 10.9.1 -> 10.9.2 age adoption passing confidence devDependencies patch
type-fest 3.13.0 -> 3.13.1 age adoption passing confidence devDependencies patch
typescript (source) 5.1.6 -> 5.6.3 age adoption passing confidence devDependencies minor

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

withastro/astro (@​astrojs/image)

v0.18.0

Compare Source

Minor Changes

v0.17.3

Compare Source

Patch Changes
withastro/astro (@​astrojs/react)

v2.3.2

Compare Source

Patch Changes

v2.3.1

Compare Source

Patch Changes

v2.3.0

Compare Source

Minor Changes

  • #​8082 16a3fdf93 Thanks @​matthewp! - Optionally parse React slots as React children.

    This adds a new configuration option for the React integration experimentalReactChildren:

    export default {
  integrations: [
    react({
      experimentalReactChildren: true,
    }),
  ],
};

    With this enabled, children passed to React from Astro components via the default slot are parsed as React components.

    This enables better compatibility with certain React components which manipulate their children.

v2.2.2

Compare Source

Patch Changes
  • #​8075 da517d405 Thanks @​SudoCat! - fix a bug where react identifierPrefix was set to null for client:only components causing React.useId to generate ids prefixed with null
floating-ui/floating-ui (@​floating-ui/dom)

v1.6.12

Compare Source

Patch Changes
  • fix: handle relative html offset clipping rect
  • fix(getClippingRect): allow passing DOMRect as a boundary

v1.6.11

Compare Source

Patch Changes

v1.6.10

Compare Source

Patch Changes

v1.6.9

Compare Source

Patch Changes
  • fix: test if frameElement is readable to avoid errors in Safari and MSEdge with cross-origin iframes
  • Update dependencies: @floating-ui/[email protected]

v1.6.8

Compare Source

Patch Changes

v1.6.7

Compare Source

Patch Changes
  • chore: fix internal dependency versioning
  • Update dependencies: @floating-ui/[email protected]

v1.6.6

Compare Source

Patch Changes
  • fix(getContainingBlock): detect top layer elements
  • fix(types): add optional getClientRects() method to VirtualElement
  • chore: fix internal deps
  • refactor: improve types and internal codebase consistency. All documented types are now exported.
  • Update dependencies: @floating-ui/[email protected]

v1.6.5

Compare Source

Patch Changes
  • fix: correctly calculate <svg> arrow element offsetParent. Fixes arrow positioning when styling an inner element of the floating element with a border.
  • fix: ignore clippingAncestors collision boundary for top layer elements
  • fix(types): correct OffsetOptions alias

v1.6.4

Compare Source

Patch Changes
  • fix: avoid spreading rects to support DOMRect types
  • fix(types): use DOM Derivable type
  • perf(autoUpdate): reduce layoutShift update checks while reference is clipped from view

v1.6.3

Compare Source

Patch Changes
  • fix: calculate reference element offset relative to offsetParent iframe. Fixes issue with positioning in nested iframes, such as the following:
<html>
  <iframe>
    <div>floating</div>
    <iframe>
      <div>reference</div>
    </iframe>
  </iframe>
</html>

v1.6.2

Compare Source

Patch Changes
  • fix: top layer element positioning and collision detection when using absolute strategy

v1.6.1

Compare Source

Patch Changes
  • perf: avoid getContainingBlock call for non-top layer elements

v1.6.0

Compare Source

Minor Changes
Patch Changes

v1.5.4

Compare Source

Patch Changes

v1.5.3

Compare Source

Patch Changes

v1.5.2

Compare Source

Patch Changes
  • 3426bc2: fix: traverse into iframe parents when finding overflow ancestors

v1.5.1

Compare Source

Bug Fixes
  • fix(types): resolution when using moduleResolution: "NodeNext" (#​2473)

v1.5.0

Compare Source

Refactors
  • Split utils into @floating-ui/utils package (@floating-ui/utils/dom import) (#​2449)

v1.4.5

Compare Source

Bug Fixes

  • fix: avoid documentElement error in testing envs (#​2438)

  • fix: add check for own instance in is* guard functions (#​2439)

percy/cli (@​percy/cli)

v1.30.2

Compare Source

What's Changed

✨ Enhancements
🏗 Maintenance
⬆️⬇️ Dependency Updates

Full Changelog: percy/cli@v1.30.1...v1.30.2

v1.30.1

Compare Source

What's Changed

✨ Enhancements
🏗 Maintenance
⬆️⬇️ Dependency Updates

New Contributors

Full Changelog: percy/cli@v1.30.0...v1.30.1

v1.30.0

Compare Source

What's Changed

Full Changelog: percy/cli@v1.29.4...v1.30.0

v1.29.4

Compare Source

What's Changed

✨ Enhancements
🐛 Bug Fixes
🏗 Maintenance
⬆️⬇️ Dependency Updates

New Contributors

Full Changelog: percy/cli@v1.29.3...v1.29.4

v1.29.3

Compare Source

What's Changed

✨ Enhancements
🐛 Bug Fixes

Full Changelog: percy/cli@v1.29.2...v1.29.3

v1.29.2

Compare Source

What's Changed

  • Update messaging for collecting logs in #​1690
  • Validate presence of error in config validator in #​1675

New Contributors

Full Changelog: percy/cli@v1.29.1...v1.29.2

v1.29.1

Compare Source

Full Changelog: percy/cli@v1.29.0...v1.29.1

v1.29.0

Compare Source

What's Changed

New Contributors

Full Changelog: percy/cli@v1.28.9...v1.29.0

v1.28.9

Compare Source

What's Changed

✨ Enhancements

Full Changelog: percy/cli@v1.28.8...v1.28.9

v1.28.8

Compare Source

What's Changed

✨ Enhancements
🐛 Bug Fixes
🏗 Maintenance
⬆️⬇️ Dependency Updates

New Contributors

Full Changelog: percy/cli@v1.28.7...v1.28.8

v1.28.7

Compare Source

What's Changed

✨ Enhancements

Full Changelog: percy/cli@v1.28.6...v1.28.7

New Contributors

v1.28.6

Compare Source

What's Changed

✨ Enhancements

Full Changelog: percy/cli@v1.28.5...v1.28.6

v1.28.5

Compare Source

What's Changed

🐛 Bug Fixes

Full Changelog: percy/cli@v1.28.4...v1.28.5

v1.28.4

Compare Source

What's Changed

✨ Enhancements
Issues

CLI executables are not published for this version

Full Changelog: percy/cli@v1.28.3...v1.28.4

v1.28.3

Compare Source

What's Changed

✨ Enhancements

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 label Sep 2, 2024
@renovate Renovate
Copy link
Author

renovate bot commented Sep 2, 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 unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/prettier
npm error   dev prettier@"2.8.8" from the root project
npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
npm error   node_modules/@ianvs/prettier-plugin-sort-imports
npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
npm error     node_modules/prettier-plugin-tailwindcss
npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
npm error   3 more (@shopify/prettier-plugin-liquid, ...)
npm error
npm error Could not resolve dependency:
npm error peer prettier@"^3.0" from [email protected]
npm error node_modules/prettier-plugin-tailwindcss
npm error   dev prettier-plugin-tailwindcss@"0.6.8" 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-11-19T02_29_04_559Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-19T02_29_04_559Z-debug-0.log

@secure-code-warrior-for-github Secure Code Warrior for GitHub
Copy link

Micro-Learning Topic: Race condition (Detected by phrase)

Matched on "race condition"

What is this? (2min video)

A race condition is a flaw that produces an unexpected result when the timing of actions impact other actions.

Try a challenge in Secure Code Warrior

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from b51faed to 5de85bd Compare September 4, 2024 20:44
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from e6574a2 to 2ff391c Compare September 15, 2024 08:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 23914c0 to 620b2cb Compare September 25, 2024 12:46
@codiumai-pr-agent-pro CodiumAI PR-Agent Pro
Copy link

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Run TypeScript check

Failed stage: Install dependencies [❌]

Failure summary:

The action failed due to a dependency conflict error during the npm ci command:

  • The [email protected] requires prettier version ^3.0, but the project currently has
    [email protected].
  • This conflict prevents the dependency tree from being resolved.
  • Suggested solutions include fixing the upstream dependency conflict or retrying the command with
    --force or --legacy-peer-deps to bypass the conflict.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

437:  ##[endgroup]
438:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
439:  /home/runner/.npm
440:  npm cache is not found
441:  ##[group]Run npm ci
442:  �[36;1mnpm ci�[0m
443:  shell: /usr/bin/bash -e {0}
444:  ##[endgroup]
445:  npm error code ERESOLVE
446:  npm error ERESOLVE unable to resolve dependency tree
447:  npm error
448:  npm error While resolving: [email protected]
449:  npm error Found: [email protected]
450:  npm error node_modules/prettier
451:  npm error   dev prettier@"2.8.8" from the root project
452:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
453:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
454:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
455:  npm error     node_modules/prettier-plugin-tailwindcss
456:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
457:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
458:  npm error
459:  npm error Could not resolve dependency:
460:  npm error peer prettier@"^3.0" from [email protected]
461:  npm error node_modules/prettier-plugin-tailwindcss
462:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
463:  npm error
464:  npm error Fix the upstream dependency conflict, or retry
465:  npm error this command with --force or --legacy-peer-deps
466:  npm error to accept an incorrect (and potentially broken) dependency resolution.
467:  npm error
468:  npm error
469:  npm error For a full report see:
470:  npm error /home/runner/.npm/_logs/2024-09-28T05_38_25_083Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-28T05_38_25_083Z-debug-0.log
472:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Astro check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution error during the npm ci command:

  • The prettier package version 2.8.8 is installed, but [email protected] requires
    prettier version ^3.0.
  • This results in a conflict in the dependency tree that npm cannot resolve automatically.
  • The error suggests fixing the upstream dependency conflict or using --force or --legacy-peer-deps to
    bypass the conflict.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

435:  ##[endgroup]
436:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
437:  /home/runner/.npm
438:  npm cache is not found
439:  ##[group]Run npm ci
440:  �[36;1mnpm ci�[0m
441:  shell: /usr/bin/bash -e {0}
442:  ##[endgroup]
443:  npm error code ERESOLVE
444:  npm error ERESOLVE unable to resolve dependency tree
445:  npm error
446:  npm error While resolving: [email protected]
447:  npm error Found: [email protected]
448:  npm error node_modules/prettier
449:  npm error   dev prettier@"2.8.8" from the root project
450:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
451:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
452:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
453:  npm error     node_modules/prettier-plugin-tailwindcss
454:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
455:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
456:  npm error
457:  npm error Could not resolve dependency:
458:  npm error peer prettier@"^3.0" from [email protected]
459:  npm error node_modules/prettier-plugin-tailwindcss
460:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
461:  npm error
462:  npm error Fix the upstream dependency conflict, or retry
463:  npm error this command with --force or --legacy-peer-deps
464:  npm error to accept an incorrect (and potentially broken) dependency resolution.
465:  npm error
466:  npm error
467:  npm error For a full report see:
468:  npm error /home/runner/.npm/_logs/2024-09-28T05_38_27_036Z-eresolve-report.txt
469:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-28T05_38_27_036Z-debug-0.log
470:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run TypeScript check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to an npm dependency resolution error:

  • The npm ci command encountered an ERESOLVE error, indicating a dependency conflict.
  • The project requires [email protected], but [email protected] requires prettier@^3.0.
  • This conflict prevents npm from resolving the dependency tree correctly.
  • Suggested solutions include fixing the upstream dependency conflict or using --force or
    --legacy-peer-deps options to bypass the conflict.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

437:  ##[endgroup]
438:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
439:  /home/runner/.npm
440:  npm cache is not found
441:  ##[group]Run npm ci
442:  �[36;1mnpm ci�[0m
443:  shell: /usr/bin/bash -e {0}
444:  ##[endgroup]
445:  npm error code ERESOLVE
446:  npm error ERESOLVE unable to resolve dependency tree
447:  npm error
448:  npm error While resolving: [email protected]
449:  npm error Found: [email protected]
450:  npm error node_modules/prettier
451:  npm error   dev prettier@"2.8.8" from the root project
452:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
453:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
454:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
455:  npm error     node_modules/prettier-plugin-tailwindcss
456:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
457:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
458:  npm error
459:  npm error Could not resolve dependency:
460:  npm error peer prettier@"^3.0" from [email protected]
461:  npm error node_modules/prettier-plugin-tailwindcss
462:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
463:  npm error
464:  npm error Fix the upstream dependency conflict, or retry
465:  npm error this command with --force or --legacy-peer-deps
466:  npm error to accept an incorrect (and potentially broken) dependency resolution.
467:  npm error
468:  npm error
469:  npm error For a full report see:
470:  npm error /home/runner/.npm/_logs/2024-09-28T05_38_30_688Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-28T05_38_30_688Z-debug-0.log
472:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Astro check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution conflict during the npm ci command:

  • The package [email protected] requires prettier with a peer dependency of ^3.0.
  • The root project has [email protected] installed, which does not satisfy the ^3.0 requirement.
  • This conflict prevents the dependency tree from being resolved.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

438:  ##[endgroup]
439:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
440:  /home/runner/.npm
441:  npm cache is not found
442:  ##[group]Run npm ci
443:  �[36;1mnpm ci�[0m
444:  shell: /usr/bin/bash -e {0}
445:  ##[endgroup]
446:  npm error code ERESOLVE
447:  npm error ERESOLVE unable to resolve dependency tree
448:  npm error
449:  npm error While resolving: [email protected]
450:  npm error Found: [email protected]
451:  npm error node_modules/prettier
452:  npm error   dev prettier@"2.8.8" from the root project
453:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
454:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
455:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
456:  npm error     node_modules/prettier-plugin-tailwindcss
457:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
458:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
459:  npm error
460:  npm error Could not resolve dependency:
461:  npm error peer prettier@"^3.0" from [email protected]
462:  npm error node_modules/prettier-plugin-tailwindcss
463:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
464:  npm error
465:  npm error Fix the upstream dependency conflict, or retry
466:  npm error this command with --force or --legacy-peer-deps
467:  npm error to accept an incorrect (and potentially broken) dependency resolution.
468:  npm error
469:  npm error
470:  npm error For a full report see:
471:  npm error /home/runner/.npm/_logs/2024-09-28T05_38_30_671Z-eresolve-report.txt
472:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-28T05_38_30_671Z-debug-0.log
473:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Prettier check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution conflict during the npm ci command:

  • The package [email protected] requires prettier with a peer dependency of ^3.0.
  • The root project has [email protected] installed, which does not satisfy the
    prettier-plugin-tailwindcss peer dependency requirement.
  • This conflict prevents the dependency tree from being resolved.
  • Suggested solutions include fixing the upstream dependency conflict or using --force or
    --legacy-peer-deps options with the npm command.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

437:  ##[endgroup]
438:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
439:  /home/runner/.npm
440:  npm cache is not found
441:  ##[group]Run npm ci
442:  �[36;1mnpm ci�[0m
443:  shell: /usr/bin/bash -e {0}
444:  ##[endgroup]
445:  npm error code ERESOLVE
446:  npm error ERESOLVE unable to resolve dependency tree
447:  npm error
448:  npm error While resolving: [email protected]
449:  npm error Found: [email protected]
450:  npm error node_modules/prettier
451:  npm error   dev prettier@"2.8.8" from the root project
452:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
453:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
454:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
455:  npm error     node_modules/prettier-plugin-tailwindcss
456:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
457:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
458:  npm error
459:  npm error Could not resolve dependency:
460:  npm error peer prettier@"^3.0" from [email protected]
461:  npm error node_modules/prettier-plugin-tailwindcss
462:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
463:  npm error
464:  npm error Fix the upstream dependency conflict, or retry
465:  npm error this command with --force or --legacy-peer-deps
466:  npm error to accept an incorrect (and potentially broken) dependency resolution.
467:  npm error
468:  npm error
469:  npm error For a full report see:
470:  npm error /home/runner/.npm/_logs/2024-09-28T05_38_27_544Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-28T05_38_27_544Z-debug-0.log
472:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Prettier check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution conflict during the npm ci command:

  • The prettier-plugin-tailwindcss package requires prettier version ^3.0.
  • The root project has prettier version 2.8.8 installed.
  • This conflict caused the ERESOLVE error, preventing the dependency tree from being resolved.
  • Suggested solutions include fixing the upstream dependency conflict or using --force or
    --legacy-peer-deps options with the npm command.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

437:  ##[endgroup]
438:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
439:  /home/runner/.npm
440:  npm cache is not found
441:  ##[group]Run npm ci
442:  �[36;1mnpm ci�[0m
443:  shell: /usr/bin/bash -e {0}
444:  ##[endgroup]
445:  npm error code ERESOLVE
446:  npm error ERESOLVE unable to resolve dependency tree
447:  npm error
448:  npm error While resolving: [email protected]
449:  npm error Found: [email protected]
450:  npm error node_modules/prettier
451:  npm error   dev prettier@"2.8.8" from the root project
452:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
453:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
454:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
455:  npm error     node_modules/prettier-plugin-tailwindcss
456:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
457:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
458:  npm error
459:  npm error Could not resolve dependency:
460:  npm error peer prettier@"^3.0" from [email protected]
461:  npm error node_modules/prettier-plugin-tailwindcss
462:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
463:  npm error
464:  npm error Fix the upstream dependency conflict, or retry
465:  npm error this command with --force or --legacy-peer-deps
466:  npm error to accept an incorrect (and potentially broken) dependency resolution.
467:  npm error
468:  npm error
469:  npm error For a full report see:
470:  npm error /home/runner/.npm/_logs/2024-09-28T05_38_34_940Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-28T05_38_34_940Z-debug-0.log
472:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Prettier check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution conflict during the npm ci command:

  • The project requires [email protected], but [email protected] requires prettier@^3.0.
  • This conflict prevents npm from resolving the dependency tree correctly.
  • The error suggests fixing the upstream dependency conflict or using --force or --legacy-peer-deps to
    bypass the issue.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

437:  ##[endgroup]
438:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
439:  /home/runner/.npm
440:  npm cache is not found
441:  ##[group]Run npm ci
442:  �[36;1mnpm ci�[0m
443:  shell: /usr/bin/bash -e {0}
444:  ##[endgroup]
445:  npm error code ERESOLVE
446:  npm error ERESOLVE unable to resolve dependency tree
447:  npm error
448:  npm error While resolving: [email protected]
449:  npm error Found: [email protected]
450:  npm error node_modules/prettier
451:  npm error   dev prettier@"2.8.8" from the root project
452:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
453:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
454:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
455:  npm error     node_modules/prettier-plugin-tailwindcss
456:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
457:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
458:  npm error
459:  npm error Could not resolve dependency:
460:  npm error peer prettier@"^3.0" from [email protected]
461:  npm error node_modules/prettier-plugin-tailwindcss
462:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
463:  npm error
464:  npm error Fix the upstream dependency conflict, or retry
465:  npm error this command with --force or --legacy-peer-deps
466:  npm error to accept an incorrect (and potentially broken) dependency resolution.
467:  npm error
468:  npm error
469:  npm error For a full report see:
470:  npm error /home/runner/.npm/_logs/2024-09-29T02_28_43_621Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-29T02_28_43_621Z-debug-0.log
472:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Astro check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution conflict during the npm ci command:

  • The [email protected] requires prettier version ^3.0.
  • The root project is using [email protected], which does not satisfy the ^3.0 version requirement.
  • This conflict prevented npm from resolving the dependency tree, resulting in an ERESOLVE error.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

438:  ##[endgroup]
439:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
440:  /home/runner/.npm
441:  npm cache is not found
442:  ##[group]Run npm ci
443:  �[36;1mnpm ci�[0m
444:  shell: /usr/bin/bash -e {0}
445:  ##[endgroup]
446:  npm error code ERESOLVE
447:  npm error ERESOLVE unable to resolve dependency tree
448:  npm error
449:  npm error While resolving: [email protected]
450:  npm error Found: [email protected]
451:  npm error node_modules/prettier
452:  npm error   dev prettier@"2.8.8" from the root project
453:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
454:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
455:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
456:  npm error     node_modules/prettier-plugin-tailwindcss
457:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
458:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
459:  npm error
460:  npm error Could not resolve dependency:
461:  npm error peer prettier@"^3.0" from [email protected]
462:  npm error node_modules/prettier-plugin-tailwindcss
463:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
464:  npm error
465:  npm error Fix the upstream dependency conflict, or retry
466:  npm error this command with --force or --legacy-peer-deps
467:  npm error to accept an incorrect (and potentially broken) dependency resolution.
468:  npm error
469:  npm error
470:  npm error For a full report see:
471:  npm error /home/runner/.npm/_logs/2024-09-29T02_28_47_261Z-eresolve-report.txt
472:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-29T02_28_47_261Z-debug-0.log
473:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run TypeScript check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution conflict during the npm ci command:

  • The project requires [email protected], but [email protected] requires prettier@^3.0.
  • This conflict prevents npm from resolving the dependency tree.
  • The error suggests fixing the upstream dependency conflict or using --force or --legacy-peer-deps to
    bypass the issue.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

437:  ##[endgroup]
438:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
439:  /home/runner/.npm
440:  npm cache is not found
441:  ##[group]Run npm ci
442:  �[36;1mnpm ci�[0m
443:  shell: /usr/bin/bash -e {0}
444:  ##[endgroup]
445:  npm error code ERESOLVE
446:  npm error ERESOLVE unable to resolve dependency tree
447:  npm error
448:  npm error While resolving: [email protected]
449:  npm error Found: [email protected]
450:  npm error node_modules/prettier
451:  npm error   dev prettier@"2.8.8" from the root project
452:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
453:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
454:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
455:  npm error     node_modules/prettier-plugin-tailwindcss
456:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
457:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
458:  npm error
459:  npm error Could not resolve dependency:
460:  npm error peer prettier@"^3.0" from [email protected]
461:  npm error node_modules/prettier-plugin-tailwindcss
462:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
463:  npm error
464:  npm error Fix the upstream dependency conflict, or retry
465:  npm error this command with --force or --legacy-peer-deps
466:  npm error to accept an incorrect (and potentially broken) dependency resolution.
467:  npm error
468:  npm error
469:  npm error For a full report see:
470:  npm error /home/runner/.npm/_logs/2024-09-29T02_28_48_515Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-29T02_28_48_515Z-debug-0.log
472:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run TypeScript check

    Failed stage: Install dependencies [❌]

    Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

437:  ##[endgroup]
438:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
439:  /home/runner/.npm
440:  npm cache is not found
441:  ##[group]Run npm ci
442:  �[36;1mnpm ci�[0m
443:  shell: /usr/bin/bash -e {0}
444:  ##[endgroup]
445:  npm error code ERESOLVE
446:  npm error ERESOLVE unable to resolve dependency tree
447:  npm error
448:  npm error While resolving: [email protected]
449:  npm error Found: [email protected]
450:  npm error node_modules/prettier
451:  npm error   dev prettier@"2.8.8" from the root project
452:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
453:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
454:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
455:  npm error     node_modules/prettier-plugin-tailwindcss
456:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
457:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
458:  npm error
459:  npm error Could not resolve dependency:
460:  npm error peer prettier@"^3.0" from [email protected]
461:  npm error node_modules/prettier-plugin-tailwindcss
462:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
463:  npm error
464:  npm error Fix the upstream dependency conflict, or retry
465:  npm error this command with --force or --legacy-peer-deps
466:  npm error to accept an incorrect (and potentially broken) dependency resolution.
467:  npm error
468:  npm error
469:  npm error For a full report see:
470:  npm error /home/runner/.npm/_logs/2024-09-29T02_28_44_243Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-29T02_28_44_243Z-debug-0.log
472:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Prettier check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution conflict during the npm ci command:

  • The project requires [email protected], but [email protected] requires prettier@^3.0.
  • This conflict prevents npm from resolving the dependency tree, resulting in an ERESOLVE error.
  • To resolve this, the upstream dependency conflict needs to be fixed, or the command should be
    retried with --force or --legacy-peer-deps options.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

437:  ##[endgroup]
438:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
439:  /home/runner/.npm
440:  npm cache is not found
441:  ##[group]Run npm ci
442:  �[36;1mnpm ci�[0m
443:  shell: /usr/bin/bash -e {0}
444:  ##[endgroup]
445:  npm error code ERESOLVE
446:  npm error ERESOLVE unable to resolve dependency tree
447:  npm error
448:  npm error While resolving: [email protected]
449:  npm error Found: [email protected]
450:  npm error node_modules/prettier
451:  npm error   dev prettier@"2.8.8" from the root project
452:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
453:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
454:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
455:  npm error     node_modules/prettier-plugin-tailwindcss
456:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
457:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
458:  npm error
459:  npm error Could not resolve dependency:
460:  npm error peer prettier@"^3.0" from [email protected]
461:  npm error node_modules/prettier-plugin-tailwindcss
462:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
463:  npm error
464:  npm error Fix the upstream dependency conflict, or retry
465:  npm error this command with --force or --legacy-peer-deps
466:  npm error to accept an incorrect (and potentially broken) dependency resolution.
467:  npm error
468:  npm error
469:  npm error For a full report see:
470:  npm error /home/runner/.npm/_logs/2024-09-29T02_28_49_453Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-29T02_28_49_453Z-debug-0.log
472:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Astro check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to an npm dependency resolution error:

  • The npm ci command encountered an ERESOLVE error, indicating it was unable to resolve the dependency
    tree.
  • The conflict arose because [email protected] requires prettier version ^3.0, but the
    project currently has [email protected] installed.
  • This mismatch in prettier versions between the installed package and the required peer dependency
    caused the failure.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

437:  ##[endgroup]
438:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
439:  /home/runner/.npm
440:  npm cache is not found
441:  ##[group]Run npm ci
442:  �[36;1mnpm ci�[0m
443:  shell: /usr/bin/bash -e {0}
444:  ##[endgroup]
445:  npm error code ERESOLVE
446:  npm error ERESOLVE unable to resolve dependency tree
447:  npm error
448:  npm error While resolving: [email protected]
449:  npm error Found: [email protected]
450:  npm error node_modules/prettier
451:  npm error   dev prettier@"2.8.8" from the root project
452:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
453:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
454:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
455:  npm error     node_modules/prettier-plugin-tailwindcss
456:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
457:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
458:  npm error
459:  npm error Could not resolve dependency:
460:  npm error peer prettier@"^3.0" from [email protected]
461:  npm error node_modules/prettier-plugin-tailwindcss
462:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
463:  npm error
464:  npm error Fix the upstream dependency conflict, or retry
465:  npm error this command with --force or --legacy-peer-deps
466:  npm error to accept an incorrect (and potentially broken) dependency resolution.
467:  npm error
468:  npm error
469:  npm error For a full report see:
470:  npm error /home/runner/.npm/_logs/2024-09-29T02_28_49_055Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-29T02_28_49_055Z-debug-0.log
472:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @renovate renovate bot force-pushed the renovate/all-minor-patch branch from 25879ca to 9f69fc8 Compare October 3, 2024 04:57
    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Prettier check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution error during the npm ci command:

  • The prettier package version 2.8.8 is installed, but [email protected] requires
    prettier version ^3.0.
  • This results in a conflict as the installed version does not satisfy the required peer dependency
    version.
  • The error suggests fixing the upstream dependency conflict or using --force or --legacy-peer-deps to
    bypass the issue.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

442:  [command]/usr/bin/tar -xf /home/runner/work/_temp/e6aac681-d1a1-4c42-952a-6e4dd98ea160/cache.tzst -P -C /home/runner/work/PortfolioWebsite/PortfolioWebsite --use-compress-program unzstd
443:  Cache restored successfully
444:  Cache restored from key: node-cache-Linux-npm-a5ebedd30fb544f5e457e182d7db501c9341da02ed915d8e68cfebaedff967a4
445:  Received 108446010 of 108446010 (100.0%), 51.7 MBs/sec
446:  ##[group]Run npm ci
447:  �[36;1mnpm ci�[0m
448:  shell: /usr/bin/bash -e {0}
449:  ##[endgroup]
450:  npm error code ERESOLVE
451:  npm error ERESOLVE unable to resolve dependency tree
452:  npm error
453:  npm error While resolving: [email protected]
454:  npm error Found: [email protected]
455:  npm error node_modules/prettier
456:  npm error   dev prettier@"2.8.8" from the root project
457:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
458:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
459:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
460:  npm error     node_modules/prettier-plugin-tailwindcss
461:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
462:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
463:  npm error
464:  npm error Could not resolve dependency:
465:  npm error peer prettier@"^3.0" from [email protected]
466:  npm error node_modules/prettier-plugin-tailwindcss
467:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
468:  npm error
469:  npm error Fix the upstream dependency conflict, or retry
470:  npm error this command with --force or --legacy-peer-deps
471:  npm error to accept an incorrect (and potentially broken) dependency resolution.
472:  npm error
473:  npm error
474:  npm error For a full report see:
475:  npm error /home/runner/.npm/_logs/2024-10-03T04_57_40_415Z-eresolve-report.txt
476:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-03T04_57_40_415Z-debug-0.log
477:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Astro check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution conflict in the npm ci command:

  • The project requires [email protected], but [email protected] requires prettier@^3.0.
  • This conflict prevents npm from resolving the dependency tree.
  • Suggested solutions include fixing the upstream dependency conflict or using --force or
    --legacy-peer-deps options with npm ci.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

442:  [command]/usr/bin/tar -xf /home/runner/work/_temp/4adc3a67-22d0-43b5-a457-cbf6aec51972/cache.tzst -P -C /home/runner/work/PortfolioWebsite/PortfolioWebsite --use-compress-program unzstd
443:  Cache restored successfully
444:  Cache restored from key: node-cache-Linux-npm-a5ebedd30fb544f5e457e182d7db501c9341da02ed915d8e68cfebaedff967a4
445:  Received 108446010 of 108446010 (100.0%), 103.3 MBs/sec
446:  ##[group]Run npm ci
447:  �[36;1mnpm ci�[0m
448:  shell: /usr/bin/bash -e {0}
449:  ##[endgroup]
450:  npm error code ERESOLVE
451:  npm error ERESOLVE unable to resolve dependency tree
452:  npm error
453:  npm error While resolving: [email protected]
454:  npm error Found: [email protected]
455:  npm error node_modules/prettier
456:  npm error   dev prettier@"2.8.8" from the root project
457:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
458:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
459:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
460:  npm error     node_modules/prettier-plugin-tailwindcss
461:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
462:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
463:  npm error
464:  npm error Could not resolve dependency:
465:  npm error peer prettier@"^3.0" from [email protected]
466:  npm error node_modules/prettier-plugin-tailwindcss
467:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
468:  npm error
469:  npm error Fix the upstream dependency conflict, or retry
470:  npm error this command with --force or --legacy-peer-deps
471:  npm error to accept an incorrect (and potentially broken) dependency resolution.
472:  npm error
473:  npm error
474:  npm error For a full report see:
475:  npm error /home/runner/.npm/_logs/2024-10-03T04_57_40_374Z-eresolve-report.txt
476:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-03T04_57_40_374Z-debug-0.log
477:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run TypeScript check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution conflict in the npm ci command:

  • The package [email protected] requires prettier version ^3.0.
  • The root project has [email protected] installed, which does not satisfy the
    prettier-plugin-tailwindcss dependency requirement.
  • This conflict caused the npm ci command to fail with an ERESOLVE error.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

443:  Received 108446010 of 108446010 (100.0%), 51.7 MBs/sec
444:  [command]/usr/bin/tar -xf /home/runner/work/_temp/93c41a56-73c1-49bc-a338-6533081a6230/cache.tzst -P -C /home/runner/work/PortfolioWebsite/PortfolioWebsite --use-compress-program unzstd
445:  Cache restored successfully
446:  Cache restored from key: node-cache-Linux-npm-a5ebedd30fb544f5e457e182d7db501c9341da02ed915d8e68cfebaedff967a4
447:  ##[group]Run npm ci
448:  �[36;1mnpm ci�[0m
449:  shell: /usr/bin/bash -e {0}
450:  ##[endgroup]
451:  npm error code ERESOLVE
452:  npm error ERESOLVE unable to resolve dependency tree
453:  npm error
454:  npm error While resolving: [email protected]
455:  npm error Found: [email protected]
456:  npm error node_modules/prettier
457:  npm error   dev prettier@"2.8.8" from the root project
458:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
459:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
460:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
461:  npm error     node_modules/prettier-plugin-tailwindcss
462:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
463:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
464:  npm error
465:  npm error Could not resolve dependency:
466:  npm error peer prettier@"^3.0" from [email protected]
467:  npm error node_modules/prettier-plugin-tailwindcss
468:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
469:  npm error
470:  npm error Fix the upstream dependency conflict, or retry
471:  npm error this command with --force or --legacy-peer-deps
472:  npm error to accept an incorrect (and potentially broken) dependency resolution.
473:  npm error
474:  npm error
475:  npm error For a full report see:
476:  npm error /home/runner/.npm/_logs/2024-10-03T04_57_43_203Z-eresolve-report.txt
477:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-03T04_57_43_203Z-debug-0.log
478:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Astro check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution error during the npm ci command:

  • The prettier package version 2.8.8 is installed, but [email protected] requires
    prettier version ^3.0.
  • This results in a conflict because the installed version does not satisfy the required peer
    dependency version.
  • The error suggests fixing the upstream dependency conflict or using --force or --legacy-peer-deps to
    bypass the conflict.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

442:  [command]/usr/bin/tar -xf /home/runner/work/_temp/a8a1d2c0-fb41-4350-94d9-58b03768cbc1/cache.tzst -P -C /home/runner/work/PortfolioWebsite/PortfolioWebsite --use-compress-program unzstd
443:  Cache restored successfully
444:  Received 108446010 of 108446010 (100.0%), 103.3 MBs/sec
445:  Cache restored from key: node-cache-Linux-npm-a5ebedd30fb544f5e457e182d7db501c9341da02ed915d8e68cfebaedff967a4
446:  ##[group]Run npm ci
447:  �[36;1mnpm ci�[0m
448:  shell: /usr/bin/bash -e {0}
449:  ##[endgroup]
450:  npm error code ERESOLVE
451:  npm error ERESOLVE unable to resolve dependency tree
452:  npm error
453:  npm error While resolving: [email protected]
454:  npm error Found: [email protected]
455:  npm error node_modules/prettier
456:  npm error   dev prettier@"2.8.8" from the root project
457:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
458:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
459:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
460:  npm error     node_modules/prettier-plugin-tailwindcss
461:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
462:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
463:  npm error
464:  npm error Could not resolve dependency:
465:  npm error peer prettier@"^3.0" from [email protected]
466:  npm error node_modules/prettier-plugin-tailwindcss
467:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
468:  npm error
469:  npm error Fix the upstream dependency conflict, or retry
470:  npm error this command with --force or --legacy-peer-deps
471:  npm error to accept an incorrect (and potentially broken) dependency resolution.
472:  npm error
473:  npm error
474:  npm error For a full report see:
475:  npm error /home/runner/.npm/_logs/2024-10-08T02_40_12_856Z-eresolve-report.txt
476:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-08T02_40_12_856Z-debug-0.log
477:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Astro check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution error in npm:

  • The npm ci command encountered an ERESOLVE error, indicating an inability to resolve the dependency
    tree.
  • The root project requires [email protected], but [email protected] requires
    prettier@^3.0.
  • This results in a conflict between the required versions of prettier.
  • The error suggests fixing the upstream dependency conflict or using --force or --legacy-peer-deps to
    bypass the conflict.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

447:  [command]/usr/bin/tar -xf /home/runner/work/_temp/2b42d613-4000-4de2-92e4-52b8c266a04c/cache.tzst -P -C /home/runner/work/PortfolioWebsite/PortfolioWebsite --use-compress-program unzstd
448:  Cache restored successfully
449:  Cache restored from key: node-cache-Linux-npm-a5ebedd30fb544f5e457e182d7db501c9341da02ed915d8e68cfebaedff967a4
450:  Received 108446010 of 108446010 (100.0%), 17.2 MBs/sec
451:  ##[group]Run npm ci
452:  �[36;1mnpm ci�[0m
453:  shell: /usr/bin/bash -e {0}
454:  ##[endgroup]
455:  npm error code ERESOLVE
456:  npm error ERESOLVE unable to resolve dependency tree
457:  npm error
458:  npm error While resolving: [email protected]
459:  npm error Found: [email protected]
460:  npm error node_modules/prettier
461:  npm error   dev prettier@"2.8.8" from the root project
462:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
463:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
464:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
465:  npm error     node_modules/prettier-plugin-tailwindcss
466:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
467:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
468:  npm error
469:  npm error Could not resolve dependency:
470:  npm error peer prettier@"^3.0" from [email protected]
471:  npm error node_modules/prettier-plugin-tailwindcss
472:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
473:  npm error
474:  npm error Fix the upstream dependency conflict, or retry
475:  npm error this command with --force or --legacy-peer-deps
476:  npm error to accept an incorrect (and potentially broken) dependency resolution.
477:  npm error
478:  npm error
479:  npm error For a full report see:
480:  npm error /home/runner/.npm/_logs/2024-10-08T02_40_16_291Z-eresolve-report.txt
481:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-08T02_40_16_291Z-debug-0.log
482:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run TypeScript check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution error during the npm ci command:

  • The prettier-plugin-tailwindcss package requires prettier version ^3.0.
  • The current project has prettier version 2.8.8 installed.
  • This version conflict caused npm to be unable to resolve the dependency tree.
  • Suggested solutions include fixing the upstream dependency conflict or retrying the command with
    --force or --legacy-peer-deps.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

441:  [command]/usr/bin/tar -xf /home/runner/work/_temp/43cc6103-c155-48a6-809a-64b87934afeb/cache.tzst -P -C /home/runner/work/PortfolioWebsite/PortfolioWebsite --use-compress-program unzstd
442:  Cache restored successfully
443:  Cache restored from key: node-cache-Linux-npm-a5ebedd30fb544f5e457e182d7db501c9341da02ed915d8e68cfebaedff967a4
444:  Received 108446010 of 108446010 (100.0%), 103.4 MBs/sec
445:  ##[group]Run npm ci
446:  �[36;1mnpm ci�[0m
447:  shell: /usr/bin/bash -e {0}
448:  ##[endgroup]
449:  npm error code ERESOLVE
450:  npm error ERESOLVE unable to resolve dependency tree
451:  npm error
452:  npm error While resolving: [email protected]
453:  npm error Found: [email protected]
454:  npm error node_modules/prettier
455:  npm error   dev prettier@"2.8.8" from the root project
456:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
457:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
458:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
459:  npm error     node_modules/prettier-plugin-tailwindcss
460:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
461:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
462:  npm error
463:  npm error Could not resolve dependency:
464:  npm error peer prettier@"^3.0" from [email protected]
465:  npm error node_modules/prettier-plugin-tailwindcss
466:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
467:  npm error
468:  npm error Fix the upstream dependency conflict, or retry
469:  npm error this command with --force or --legacy-peer-deps
470:  npm error to accept an incorrect (and potentially broken) dependency resolution.
471:  npm error
472:  npm error
473:  npm error For a full report see:
474:  npm error /home/runner/.npm/_logs/2024-10-08T02_40_14_068Z-eresolve-report.txt
475:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-08T02_40_14_068Z-debug-0.log
476:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @renovate renovate bot force-pushed the renovate/all-minor-patch branch from e7cc9b5 to a4794af Compare October 9, 2024 05:44
    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Prettier check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution error during the npm ci command:

  • The [email protected] requires prettier version ^3.0, but the project has
    [email protected] installed.
  • This version conflict caused npm to be unable to resolve the dependency tree.
  • The error suggests fixing the upstream dependency conflict or using --force or --legacy-peer-deps to
    bypass the issue.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

442:  [command]/usr/bin/tar -xf /home/runner/work/_temp/59a2fd67-2cdc-4df4-8c18-3b0bed29364b/cache.tzst -P -C /home/runner/work/PortfolioWebsite/PortfolioWebsite --use-compress-program unzstd
443:  Cache restored successfully
444:  Cache restored from key: node-cache-Linux-npm-a5ebedd30fb544f5e457e182d7db501c9341da02ed915d8e68cfebaedff967a4
445:  Received 108446010 of 108446010 (100.0%), 103.3 MBs/sec
446:  ##[group]Run npm ci
447:  �[36;1mnpm ci�[0m
448:  shell: /usr/bin/bash -e {0}
449:  ##[endgroup]
450:  npm error code ERESOLVE
451:  npm error ERESOLVE unable to resolve dependency tree
452:  npm error
453:  npm error While resolving: [email protected]
454:  npm error Found: [email protected]
455:  npm error node_modules/prettier
456:  npm error   dev prettier@"2.8.8" from the root project
457:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
458:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
459:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
460:  npm error     node_modules/prettier-plugin-tailwindcss
461:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
462:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
463:  npm error
464:  npm error Could not resolve dependency:
465:  npm error peer prettier@"^3.0" from [email protected]
466:  npm error node_modules/prettier-plugin-tailwindcss
467:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
468:  npm error
469:  npm error Fix the upstream dependency conflict, or retry
470:  npm error this command with --force or --legacy-peer-deps
471:  npm error to accept an incorrect (and potentially broken) dependency resolution.
472:  npm error
473:  npm error
474:  npm error For a full report see:
475:  npm error /home/runner/.npm/_logs/2024-10-09T05_44_46_347Z-eresolve-report.txt
476:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-09T05_44_46_347Z-debug-0.log
477:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Astro check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution conflict during the npm ci command:

  • The prettier package version 2.8.8 is installed, but [email protected] requires
    prettier version ^3.0.
  • This conflict prevents the dependency tree from being resolved.
  • Suggested solutions include fixing the upstream dependency conflict or using --force or
    --legacy-peer-deps options with the npm command.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

441:  [command]/usr/bin/tar -xf /home/runner/work/_temp/f4825291-ba78-46b2-986a-d59c48cbafb2/cache.tzst -P -C /home/runner/work/PortfolioWebsite/PortfolioWebsite --use-compress-program unzstd
442:  Cache restored successfully
443:  Cache restored from key: node-cache-Linux-npm-a5ebedd30fb544f5e457e182d7db501c9341da02ed915d8e68cfebaedff967a4
444:  Received 108446010 of 108446010 (100.0%), 103.4 MBs/sec
445:  ##[group]Run npm ci
446:  �[36;1mnpm ci�[0m
447:  shell: /usr/bin/bash -e {0}
448:  ##[endgroup]
449:  npm error code ERESOLVE
450:  npm error ERESOLVE unable to resolve dependency tree
451:  npm error
452:  npm error While resolving: [email protected]
453:  npm error Found: [email protected]
454:  npm error node_modules/prettier
455:  npm error   dev prettier@"2.8.8" from the root project
456:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
457:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
458:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
459:  npm error     node_modules/prettier-plugin-tailwindcss
460:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
461:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
462:  npm error
463:  npm error Could not resolve dependency:
464:  npm error peer prettier@"^3.0" from [email protected]
465:  npm error node_modules/prettier-plugin-tailwindcss
466:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
467:  npm error
468:  npm error Fix the upstream dependency conflict, or retry
469:  npm error this command with --force or --legacy-peer-deps
470:  npm error to accept an incorrect (and potentially broken) dependency resolution.
471:  npm error
472:  npm error
473:  npm error For a full report see:
474:  npm error /home/runner/.npm/_logs/2024-10-09T05_44_46_318Z-eresolve-report.txt
475:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-09T05_44_46_318Z-debug-0.log
476:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run TypeScript check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution conflict in the npm ci command:

  • The project [email protected] has a dependency on [email protected].
  • The [email protected] requires prettier@^3.0, which conflicts with the installed
    version 2.8.8.
  • This conflict prevents npm from resolving the dependency tree, resulting in an ERESOLVE error.
  • Suggested solutions include fixing the upstream dependency conflict or using --force or
    --legacy-peer-deps options to bypass the conflict.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

439:  [command]/usr/bin/tar -xf /home/runner/work/_temp/d3a6231e-cff9-44bf-bb74-aa9f799acf76/cache.tzst -P -C /home/runner/work/PortfolioWebsite/PortfolioWebsite --use-compress-program unzstd
440:  Cache restored successfully
441:  Cache restored from key: node-cache-Linux-npm-a5ebedd30fb544f5e457e182d7db501c9341da02ed915d8e68cfebaedff967a4
442:  Received 108446010 of 108446010 (100.0%), 103.3 MBs/sec
443:  ##[group]Run npm ci
444:  �[36;1mnpm ci�[0m
445:  shell: /usr/bin/bash -e {0}
446:  ##[endgroup]
447:  npm error code ERESOLVE
448:  npm error ERESOLVE unable to resolve dependency tree
449:  npm error
450:  npm error While resolving: [email protected]
451:  npm error Found: [email protected]
452:  npm error node_modules/prettier
453:  npm error   dev prettier@"2.8.8" from the root project
454:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
455:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
456:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
457:  npm error     node_modules/prettier-plugin-tailwindcss
458:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
459:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
460:  npm error
461:  npm error Could not resolve dependency:
462:  npm error peer prettier@"^3.0" from [email protected]
463:  npm error node_modules/prettier-plugin-tailwindcss
464:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
465:  npm error
466:  npm error Fix the upstream dependency conflict, or retry
467:  npm error this command with --force or --legacy-peer-deps
468:  npm error to accept an incorrect (and potentially broken) dependency resolution.
469:  npm error
470:  npm error
471:  npm error For a full report see:
472:  npm error /home/runner/.npm/_logs/2024-10-09T05_44_51_499Z-eresolve-report.txt
473:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-09T05_44_51_499Z-debug-0.log
474:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Prettier check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency conflict in the npm ci command:

  • The project requires [email protected], but [email protected] requires prettier@^3.0.
  • This conflict prevents the dependency tree from being resolved.
  • To fix this, the upstream dependency conflict needs to be resolved, or the command can be retried
    with --force or --legacy-peer-deps to bypass the conflict.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

440:  [command]/usr/bin/tar -xf /home/runner/work/_temp/cd9189a3-f702-4701-aff9-942b4fc16ac9/cache.tzst -P -C /home/runner/work/PortfolioWebsite/PortfolioWebsite --use-compress-program unzstd
441:  Received 108446010 of 108446010 (100.0%), 103.4 MBs/sec
442:  Cache restored successfully
443:  Cache restored from key: node-cache-Linux-npm-a5ebedd30fb544f5e457e182d7db501c9341da02ed915d8e68cfebaedff967a4
444:  ##[group]Run npm ci
445:  �[36;1mnpm ci�[0m
446:  shell: /usr/bin/bash -e {0}
447:  ##[endgroup]
448:  npm error code ERESOLVE
449:  npm error ERESOLVE unable to resolve dependency tree
450:  npm error
451:  npm error While resolving: [email protected]
452:  npm error Found: [email protected]
453:  npm error node_modules/prettier
454:  npm error   dev prettier@"2.8.8" from the root project
455:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
456:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
457:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
458:  npm error     node_modules/prettier-plugin-tailwindcss
459:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
460:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
461:  npm error
462:  npm error Could not resolve dependency:
463:  npm error peer prettier@"^3.0" from [email protected]
464:  npm error node_modules/prettier-plugin-tailwindcss
465:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
466:  npm error
467:  npm error Fix the upstream dependency conflict, or retry
468:  npm error this command with --force or --legacy-peer-deps
469:  npm error to accept an incorrect (and potentially broken) dependency resolution.
470:  npm error
471:  npm error
472:  npm error For a full report see:
473:  npm error /home/runner/.npm/_logs/2024-10-09T05_44_53_366Z-eresolve-report.txt
474:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-09T05_44_53_366Z-debug-0.log
475:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run TypeScript check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution conflict during the npm ci command:

  • The project requires [email protected].
  • The [email protected] requires prettier@^3.0.
  • This conflict prevented npm from resolving the dependency tree.
  • The error suggests fixing the upstream dependency conflict or using --force or --legacy-peer-deps to
    bypass the conflict.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

442:  [command]/usr/bin/tar -xf /home/runner/work/_temp/84673863-c6bc-4d85-8b55-b40e11406935/cache.tzst -P -C /home/runner/work/PortfolioWebsite/PortfolioWebsite --use-compress-program unzstd
443:  Cache restored successfully
444:  Cache restored from key: node-cache-Linux-npm-a5ebedd30fb544f5e457e182d7db501c9341da02ed915d8e68cfebaedff967a4
445:  Received 108446010 of 108446010 (100.0%), 103.3 MBs/sec
446:  ##[group]Run npm ci
447:  �[36;1mnpm ci�[0m
448:  shell: /usr/bin/bash -e {0}
449:  ##[endgroup]
450:  npm error code ERESOLVE
451:  npm error ERESOLVE unable to resolve dependency tree
452:  npm error
453:  npm error While resolving: [email protected]
454:  npm error Found: [email protected]
455:  npm error node_modules/prettier
456:  npm error   dev prettier@"2.8.8" from the root project
457:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
458:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
459:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
460:  npm error     node_modules/prettier-plugin-tailwindcss
461:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
462:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
463:  npm error
464:  npm error Could not resolve dependency:
465:  npm error peer prettier@"^3.0" from [email protected]
466:  npm error node_modules/prettier-plugin-tailwindcss
467:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
468:  npm error
469:  npm error Fix the upstream dependency conflict, or retry
470:  npm error this command with --force or --legacy-peer-deps
471:  npm error to accept an incorrect (and potentially broken) dependency resolution.
472:  npm error
473:  npm error
474:  npm error For a full report see:
475:  npm error /home/runner/.npm/_logs/2024-10-09T05_44_53_327Z-eresolve-report.txt
476:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-09T05_44_53_327Z-debug-0.log
477:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @codiumai-pr-agent-pro CodiumAI PR-Agent Pro
    Copy link

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: Run Astro check

    Failed stage: Install dependencies [❌]

    Failure summary:

    The action failed due to a dependency resolution conflict in the npm ci command:

  • The prettier-plugin-tailwindcss package requires prettier version ^3.0.
  • The root project currently has prettier version 2.8.8.
  • This creates a conflict as prettier-plugin-tailwindcss cannot resolve its peer dependency.
  • The error suggests fixing the upstream dependency conflict or using --force or --legacy-peer-deps to
    bypass the issue.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

444:  [command]/usr/bin/tar -xf /home/runner/work/_temp/fc3cadd5-513f-4242-a2c9-38bef83c528e/cache.tzst -P -C /home/runner/work/PortfolioWebsite/PortfolioWebsite --use-compress-program unzstd
445:  Cache restored successfully
446:  Cache restored from key: node-cache-Linux-npm-a5ebedd30fb544f5e457e182d7db501c9341da02ed915d8e68cfebaedff967a4
447:  Received 108446010 of 108446010 (100.0%), 34.5 MBs/sec
448:  ##[group]Run npm ci
449:  �[36;1mnpm ci�[0m
450:  shell: /usr/bin/bash -e {0}
451:  ##[endgroup]
452:  npm error code ERESOLVE
453:  npm error ERESOLVE unable to resolve dependency tree
454:  npm error
455:  npm error While resolving: [email protected]
456:  npm error Found: [email protected]
457:  npm error node_modules/prettier
458:  npm error   dev prettier@"2.8.8" from the root project
459:  npm error   peer prettier@"2 || 3" from @ianvs/[email protected]
460:  npm error   node_modules/@ianvs/prettier-plugin-sort-imports
461:  npm error     peerOptional @ianvs/prettier-plugin-sort-imports@"*" from [email protected]
462:  npm error     node_modules/prettier-plugin-tailwindcss
463:  npm error       dev prettier-plugin-tailwindcss@"0.6.8" from the root project
464:  npm error   3 more (@shopify/prettier-plugin-liquid, ...)
465:  npm error
466:  npm error Could not resolve dependency:
467:  npm error peer prettier@"^3.0" from [email protected]
468:  npm error node_modules/prettier-plugin-tailwindcss
469:  npm error   dev prettier-plugin-tailwindcss@"0.6.8" from the root project
470:  npm error
471:  npm error Fix the upstream dependency conflict, or retry
472:  npm error this command with --force or --legacy-peer-deps
473:  npm error to accept an incorrect (and potentially broken) dependency resolution.
474:  npm error
475:  npm error
476:  npm error For a full report see:
477:  npm error /home/runner/.npm/_logs/2024-10-09T05_44_56_610Z-eresolve-report.txt
478:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-09T05_44_56_610Z-debug-0.log
479:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 6949676 to a201a3b Compare October 19, 2024 02:44
    @renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 51803e0 to 58a114b Compare October 30, 2024 08:50
    @renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 53bb9eb to 5e6bc80 Compare November 8, 2024 02:35
    @renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 7f4d94a to 1f37e4f Compare November 15, 2024 09:00
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Reviewers
    No reviews
    Assignees
    No one assigned
    Labels
    dependencies
    Projects
    None yet
    Milestone
    No milestone
    Development

    Successfully merging this pull request may close these issues.
    0 participants