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
Contributor

@renovate renovate bot commented Jun 17, 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
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.0.14 -> 2.3.5 age adoption passing confidence devDependencies minor
auto-changelog 2.4.0 -> 2.5.0 age adoption passing confidence dependencies minor
concurrently 8.2.0 -> 8.2.2 age adoption passing confidence devDependencies patch
cspell (source) 8.8.4 -> 8.16.0 age adoption passing confidence dependencies 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
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.25 -> 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) 20.8.0 -> 20.9.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

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
🐛 Bug Fixes
⬆️⬇️ Dependency Updates

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

v1.28.2

Compare Source

What's Changed

✨ Enhancements
⬆️⬇️ Dependency Updates

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
Copy link
Contributor Author

renovate bot commented Jun 17, 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-15T05_11_52_253Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-15T05_11_52_253Z-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

@netlify Netlify
Copy link

netlify bot commented Jun 17, 2024 •
edited
Loading

❌ Deploy Preview for gurdipdev failed. Why did it fail? →

Name Link
🔨 Latest commit 87adc40
🔍 Latest deploy log https://app.netlify.com/sites/gurdipdev/deploys/6684693c41722f00084f1661

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from fdbef73 to c2dbbb4 Compare June 21, 2024 17:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from e59c8ea to 2f90302 Compare June 30, 2024 11:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 77df520 to d6d4ea0 Compare July 9, 2024 02:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from dd53d06 to aa6e325 Compare July 26, 2024 02:56
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 53af3e5 to 6a705d1 Compare August 2, 2024 20:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 4f37c94 to a68f5e3 Compare August 14, 2024 02:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 5111710 to 8858f42 Compare August 20, 2024 20:41
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 5158781 to 8c4c60b Compare September 3, 2024 05:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 291595f to 4e40709 Compare October 8, 2024 08:37
@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 specific conflict was between [email protected] and [email protected], which
    requires prettier@^3.0.
  • This conflict needs to be resolved by either updating the dependencies to compatible versions or
    using the --force or --legacy-peer-deps flags to bypass the conflict.

    • 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-10-08T08_38_05_951Z-eresolve-report.txt
472:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-08T08_38_05_951Z-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 conflict error 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
...

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-10-08T08_38_07_633Z-eresolve-report.txt
472:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-08T08_38_07_633Z-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 error in npm:

  • The npm ci command encountered an ERESOLVE error, indicating it was unable to resolve the dependency
    tree.
  • The specific conflict is between [email protected] and [email protected], which
    requires prettier@^3.0.
  • This conflict arises because prettier-plugin-tailwindcss has a peer dependency on prettier version
    ^3.0, but the project is using [email protected].
  • 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
...

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-10-08T08_38_06_095Z-eresolve-report.txt
472:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-08T08_38_06_095Z-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 conflict error during the npm ci command:

  • The [email protected] requires prettier version ^3.0.
  • The current project has [email protected] installed.
  • This conflict in the dependency tree caused the ERESOLVE error, preventing the installation of
    dependencies.

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

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

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

439:  ##[endgroup]
440:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
441:  /home/runner/.npm
442:  npm cache is not found
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-08T08_38_16_000Z-eresolve-report.txt
473:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-08T08_38_16_000Z-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 resolution error during the npm ci command:

  • The prettier-plugin-tailwindcss package requires prettier version ^3.0.
  • The project currently has prettier version 2.8.8 installed.
  • This version 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 npm.

    • 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-10-08T08_38_17_415Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-08T08_38_17_415Z-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 4e40709 to 17d132a Compare October 9, 2024 08:37
    @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 root project [email protected] requires [email protected].
  • There is a conflict with [email protected], which requires prettier@^3.0.
  • This dependency conflict needs to be resolved by either updating the dependencies to compatible
    versions or using --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-10-09T08_37_37_422Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-09T08_37_37_422Z-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 [❌]

    Failure summary:

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

  • The [email protected] requires prettier version ^3.0.
  • The current project has [email protected] installed.
  • 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
...

439:  ##[endgroup]
440:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
441:  /home/runner/.npm
442:  npm cache is not found
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-09T08_37_36_826Z-eresolve-report.txt
473:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-09T08_37_36_826Z-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 TypeScript 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.
  • The root project has [email protected] installed, which does not satisfy the
    prettier-plugin-tailwindcss dependency requirement.
  • This caused an ERESOLVE error, indicating an inability to resolve the dependency tree.
  • 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-10-09T08_37_46_635Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-09T08_37_46_635Z-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 an npm dependency resolution error:

  • The npm ci command encountered an ERESOLVE error, indicating it was unable to resolve the dependency
    tree.
  • The root project [email protected] requires [email protected].
  • The [email protected] requires a peer dependency of prettier@^3.0, which conflicts
    with the installed version 2.8.8.
  • This conflict prevents npm from resolving the dependencies correctly.
  • Suggested solutions include fixing the upstream dependency conflict or using --force or
    --legacy-peer-deps options to bypass the error.

    • 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-10-09T08_37_45_742Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-09T08_37_45_742Z-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 in 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 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-10-09T08_37_45_845Z-eresolve-report.txt
471:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-09T08_37_45_845Z-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 conflict in the npm ci command:

  • The [email protected] requires prettier version ^3.0.
  • The root project has [email protected] installed, which does not satisfy the
    prettier-plugin-tailwindcss requirement.
  • This results in an ERESOLVE error, indicating an inability 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
...

439:  ##[endgroup]
440:  [command]/opt/hostedtoolcache/node/18.20.4/x64/bin/npm config get cache
441:  /home/runner/.npm
442:  npm cache is not found
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-09T08_37_39_390Z-eresolve-report.txt
473:  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-09T08_37_39_390Z-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.

    @renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from d337a5b to 3c33974 Compare October 19, 2024 02:24
    @renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from abd6199 to a39e9a1 Compare November 6, 2024 20:49
    @renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from cd95efe to f7a5953 Compare November 12, 2024 08:45
    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