chore(deps): update astro monorepo to v3 (major) #7

renovate · 2024-09-23T02:38:23Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/react (source)	`2.2.1` -> `3.6.2`
astro (source)	`2.8.0` -> `3.6.5`

Warning

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

Release Notes

withastro/astro (@astrojs/react)

`v3.6.2`

Compare Source

Patch Changes

#11624 7adb350 Thanks @bluwy! - Prevents throwing errors when checking if a component is a React component in runtime

`v3.6.1`

Compare Source

Patch Changes

#11571 1c3265a Thanks @bholmesdev! - BREAKING CHANGE to the experimental Actions API only. Install the latest @astrojs/react integration as well if you're using React 19 features.

Make .safe() the default return value for actions. This means { data, error } will be returned when calling an action directly. If you prefer to get the data while allowing errors to throw, chain the .orThrow() modifier.
```
import { actions } from 'astro:actions';

// Before
const { data, error } = await actions.like.safe();
// After
const { data, error } = await actions.like();

// Before
const newLikes = await actions.like();
// After
const newLikes = await actions.like.orThrow();
```

`v3.6.0`

Compare Source

Minor Changes

#11234 4385bf7 Thanks @ematipico! - Adds a new function called addServerRenderer to the Container API. Use this function to manually store renderers inside the instance of your container.

This new function should be preferred when using the Container API in environments like on-demand pages:

import type { APIRoute } from 'astro';
import { experimental_AstroContainer } from 'astro/container';
import reactRenderer from '@&#8203;astrojs/react/server.js';
import vueRenderer from '@&#8203;astrojs/vue/server.js';
import ReactComponent from '../components/button.jsx';
import VueComponent from '../components/button.vue';

// MDX runtime is contained inside the Astro core
import mdxRenderer from 'astro/jsx/server.js';

// In case you need to import a custom renderer
import customRenderer from '../renderers/customRenderer.js';

export const GET: APIRoute = async (ctx) => {
  const container = await experimental_AstroContainer.create();
  container.addServerRenderer({ renderer: reactRenderer });
  container.addServerRenderer({ renderer: vueRenderer });
  container.addServerRenderer({ renderer: customRenderer });
  // You can pass a custom name too
  container.addServerRenderer({
    name: 'customRenderer',
    renderer: customRenderer,
  });
  const vueComponent = await container.renderToString(VueComponent);
  return await container.renderToResponse(Component);
};

`v3.5.0`

Compare Source

Minor Changes

#11144 803dd80 Thanks @ematipico! - The integration now exposes a function called getContainerRenderer, that can be used inside the Container APIs to load the relative renderer.

import { experimental_AstroContainer as AstroContainer } from 'astro/container';
import ReactWrapper from '../src/components/ReactWrapper.astro';
import { loadRenderers } from 'astro:container';
import { getContainerRenderer } from '@&#8203;astrojs/react';

test('ReactWrapper with react renderer', async () => {
  const renderers = await loadRenderers([getContainerRenderer()]);
  const container = await AstroContainer.create({
    renderers,
  });
  const result = await container.renderToString(ReactWrapper);

  expect(result).toContain('Counter');
  expect(result).toContain('Count: <!-- -->5');
});

`v3.4.0`

Compare Source

Minor Changes

#11071 8ca7c73 Thanks @bholmesdev! - Adds two new functions experimental_getActionState() and experimental_withState() to support the React 19 useActionState() hook when using Astro Actions. This introduces progressive enhancement when calling an Action with the withState() utility.

This example calls a like action that accepts a postId and returns the number of likes. Pass this action to the experimental_withState() function to apply progressive enhancement info, and apply to useActionState() to track the result:

import { actions } from 'astro:actions';
import { experimental_withState } from '@&#8203;astrojs/react/actions';

export function Like({ postId }: { postId: string }) {
  const [state, action, pending] = useActionState(
    experimental_withState(actions.like),
    0 // initial likes
  );

  return (
    <form action={action}>
      <input type="hidden" name="postId" value={postId} />
      <button disabled={pending}>{state} ❤️</button>
    </form>
  );
}

You can also access the state stored by useActionState() from your action handler. Call experimental_getActionState() with the API context, and optionally apply a type to the result:

import { defineAction, z } from 'astro:actions';
import { experimental_getActionState } from '@&#8203;astrojs/react/actions';

export const server = {
  like: defineAction({
    input: z.object({
      postId: z.string(),
    }),
    handler: async ({ postId }, ctx) => {
      const currentLikes = experimental_getActionState<number>(ctx);
      // write to database
      return currentLikes + 1;
    },
  }),
};

`v3.3.4`

Compare Source

Patch Changes

#10986 4d16381 Thanks @emish89! - Fixes incorrect peerDependencies for @types/react and @types/react-dom

`v3.3.3`

Compare Source

Patch Changes

#10942 d47baa4 Thanks @matthewp! - Updates package to support React 19 beta

`v3.3.2`

Compare Source

Patch Changes

#10893 fd7a9ed Thanks @Angrigo! - Removes using deprecated ReactDOMServer.renderToStaticNodeStream API

`v3.3.1`

Compare Source

Patch Changes

#10855 f6bddd3 Thanks @lamATnginx! - Fix Redoc usage in React integration

`v3.3.0`

Compare Source

Minor Changes

#10689 683d51a5eecafbbfbfed3910a3f1fbf0b3531b99 Thanks @ematipico! - Deprecate support for versions of Node.js older than v18.17.1 for Node.js 18, older than v20.0.3 for Node.js 20, and the complete Node.js v19 release line.

This change is in line with Astro's Node.js support policy.

Minor Changes

#10136 9cd84bd19b92fb43ae48809f575ee12ebd43ea8f Thanks @matthewp! - Changes the default behavior of transition:persist to update the props of persisted islands upon navigation. Also adds a new view transitions option transition:persist-props (default: false) to prevent props from updating as needed.

Islands which have the transition:persist property to keep their state when using the <ViewTransitions /> router will now have their props updated upon navigation. This is useful in cases where the component relies on page-specific props, such as the current page title, which should update upon navigation.

For example, the component below is set to persist across navigation. This component receives a products props and might have some internal state, such as which filters are applied:
```
<ProductListing transition:persist products={products} />
```
Upon navigation, this component persists, but the desired products might change, for example if you are visiting a category of products, or you are performing a search.

Previously the props would not change on navigation, and your island would have to handle updating them externally, such as with API calls.

With this change the props are now updated, while still preserving state.

You can override this new default behavior on a per-component basis using transition:persist-props=true to persist both props and state during navigation:
```
<ProductListing transition:persist-props="true" products={products} />
```

`v3.0.10`

Compare Source

Patch Changes

#9849 20ca3154fb37049cbcd51b06d9fa2ef25ac25a36 Thanks @StandardGage! - Fixes an issue where passing void elements (img, etc..) did not work with the experimentalReactChildren option enabled

`v3.0.9`

Compare Source

Patch Changes

#9482 72b26daf694b213918f02d0fcbf90ab5b7ebc31f Thanks @natemoo-re! - Improves compatability with the Qwik adapter
#9479 1baf0b0d3cbd0564954c2366a7278794fad6726e Thanks @sarah11918! - Updates README

`v3.0.8`

Compare Source

Patch Changes

#9403 7eb9fe8a7 Thanks @knpwrs! - Prevents unsupported forwardRef components created by Preact from being rendered by React
#9452 e83b5095f Thanks @florian-lefebvre! - Upgrades vite to latest

`v3.0.7`

Compare Source

Patch Changes

#9122 1c48ed286 Thanks @bluwy! - Adds Vite 5 support. There are no breaking changes from Astro. Check the Vite migration guide for details of the breaking changes from Vite instead.

`v3.0.6`

Compare Source

Patch Changes

#9141 af43fb517 Thanks @lilnasy! - Fixes an issue where slotting self-closing elements (img, br, hr) into react components with experimentalReactChildren enabled led to an error.

`v3.0.5`

Compare Source

Patch Changes

#8925 ac5633b8f Thanks @brandonsdebt! - Uses node:stream during server rendering for compatibility with Cloudflare

`v3.0.4`

Compare Source

Patch Changes

#8898 4dee38711 Thanks @matthewp! - Fixes client hydration in islands when using experimentalReactChildren

`v3.0.3`

Compare Source

Patch Changes

#8737 6f60da805 Thanks @ematipico! - Add provenance statement when publishing the library from CI

`v3.0.2`

Compare Source

Patch Changes

#8455 85fe213fe Thanks @natemoo-re! - Update experimentalReactChildren behavior to support void tags

`v3.0.1`

Compare Source

Patch Changes

#9849 20ca3154fb37049cbcd51b06d9fa2ef25ac25a36 Thanks @StandardGage! - Fixes an issue where passing void elements (img, etc..) did not work with the experimentalReactChildren option enabled

`v3.0.0`

Compare Source

Major Changes

#8188 d0679a666 Thanks @ematipico! - Remove support for Node 16. The lowest supported version by Astro and all integrations is now v18.14.1. As a reminder, Node 16 will be deprecated on the 11th September 2023.
#8179 6011d52d3 Thanks @matthewp! - Astro 3.0 Release Candidate
#7924 519a1c4e8 Thanks @matthewp! - Support for React Refresh

The React integration now fully supports React Refresh and is backed by @vitejs/plugin-react.

Also included in this change are new include and exclude config options. Use these if you want to use React alongside another JSX framework; include specifies files to be compiled for React and exclude does the opposite.

Patch Changes

#8228 4bd2fac8d Thanks @bluwy! - Publish missing vnode-children.js file
#8264 1f58a7a1b Thanks @natemoo-re! - Automatically unmount islands when astro:unmount is fired
Updated dependencies [d0679a666, 2aa6d8ace, 6011d52d3]:
- @astrojs/internal-helpers @0.2.0

`v2.3.2`

Compare Source

Patch Changes

#8149 531cc3e49 Thanks @matthewp! - Fix missing package file regression

`v2.3.1`

Compare Source

Patch Changes

#8137 8c0a4ed10 Thanks @natemoo-re! - Fix missing export for new experimentalReactChildren option

`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

withastro/astro (astro)

`v3.6.5`

Compare Source

Patch Changes

#10287 a90d685d7 Thanks @ematipico! - Fixes an issue where in Node SSR, the image endpoint could be used maliciously to reveal unintended information about the underlying system.

Thanks to Google Security Team for reporting this issue.

`v3.6.4`

Compare Source

Patch Changes

#9226 8f8a40e93 Thanks @outofambit! - Fix i18n fallback routing with routing strategy of always-prefix
#9179 3f28336d9 Thanks @lilnasy! - Fixes an issue where the presence of a slot in a page led to an error.
#9219 067a65f5b Thanks @natemoo-re! - Fix edge case where <style> updates inside of .astro files would ocassionally fail to update without reloading the page.

#9236 27d3e86e4 Thanks @ematipico! - The configuration i18n.routingStrategy has been replaced with an object called routing.

export default defineConfig({
  experimental: {
      i18n: {
-          routingStrategy: "prefix-always",
+          routing: {
+              prefixDefaultLocale: true,
+          }
      }
  }
})

export default defineConfig({
  experimental: {
      i18n: {
-          routingStrategy: "prefix-other-locales",
+          routing: {
+              prefixDefaultLocale: false,
+          }
      }
  }
})

`v3.6.3`

Compare Source

Patch Changes

#9193 0dc99c9a2 Thanks @florian-lefebvre! - Prevents the Code component from crashing if the lang isn't supported by falling back to plaintext.

`v3.6.2`

Compare Source

Patch Changes

#9189 d90714fc3 Thanks @SpencerWhitehead7! - Fixes an issue where links with the same pathname as the current page, but different search params, were not prefetched.

`v3.6.1`

Compare Source

Patch Changes

#9173 04fdc1c61 Thanks @lilnasy! - Fixes an issue where having a middleware prevented the SSR app from being deployed on Netlify.
#9186 607542c7c Thanks @martrapp! - Fixes a view transition issue on webKit browsers that prevented scrolling to #fragments

`v3.6.0`

Compare Source

Minor Changes

#9090 c87223c21 Thanks @martrapp! - Take full control over the behavior of view transitions!

Three new events now complement the existing astro:after-swap and astro:page-load events:
```
'astro:before-preparation'; // Control how the DOM and other resources of the target page are loaded
'astro:after-preparation'; // Last changes before taking off? Remove that loading indicator? Here you go!
'astro:before-swap'; // Control how the DOM is updated to match the new page
```
The astro:before-* events allow you to change properties and strategies of the view transition implementation.
The astro:after-* events are notifications that a phase is complete.
Head over to docs to see the full view transitions lifecycle including these new events!
#9092 0ea4bd47e Thanks @smitbarmase! - Changes the fallback prefetch behavior on slow connections and when data saver mode is enabled. Instead of disabling prefetch entirely, the tap strategy will be used.
#9166 cba6cf32d Thanks @matthewp! - The Picture component is no longer experimental

The <Picture /> component, part of astro:assets, has exited experimental status and is now recommended for use. There are no code changes to the component, and no upgrade to your project is necessary.

This is only a change in documentation/recommendation. If you were waiting to use the <Picture /> component until it had exited the experimental stage, wait no more!
#9092 0ea4bd47e Thanks @smitbarmase! - Adds a ignoreSlowConnection option to the prefetch() API to prefetch even on data saver mode or slow connection.

`v3.5.7`

Compare Source

Patch Changes

#9157 7ff8d62bf Thanks @ematipico! - Revert fix around fallback system, which broken injected styles

`v3.5.6`

Compare Source

Patch Changes

#9121 f4efd1c80 Thanks @peng! - Adds a warning if astro add fetches a package but returns a non-404 status
#9142 7d55cf68d Thanks @ematipico! - Consistely emit fallback routes in the correct folders.
#9119 306781795 Thanks @ematipico! - Fix a flaw in the i18n fallback logic, where the routes didn't preserve their metadata, such as hoisted scripts
#9140 7742fd7dc Thanks @martrapp! - View Transitions: handle clicks on SVGAElements and image maps"
#9101 e3dce215a Thanks @ematipico! - Add a new property Astro.currentLocale, available when i18n is enabled.

`v3.5.5`

Compare Source

Patch Changes

#9091 536c6c9fd Thanks @ematipico! - The routingStrategy prefix-always should not force its logic to endpoints. This fixes some regression with astro:assets and @astrojs/rss.
#9102 60e8210b0 Thanks @Princesseuh! - In the dev overlay, when there's too many plugins enabled at once, some of the plugins will now be hidden in a separate sub menu to avoid the bar becoming too long

`v3.5.4`

Compare Source

Patch Changes

#9085 fc66ecff1 Thanks @ematipico! - When redirecting to the default root locale, Astro middleare should take into consideration the value of trailingSlash
#9067 c6e449c5b Thanks @danielhajduk! - Fixes display of debug messages when using the --verbose flag
#9075 c5dc8f2ec Thanks @Princesseuh! - Fix Passthrough image service generating multiple images with the same content in certain cases
#9083 4537ecf0d Thanks @bluwy! - Uses new createShikiHighlighter API from @astrojs/markdown-remark to avoid code duplication
#9084 045e5ec97 Thanks @matthewp! - Supports formmethod and formaction for form overrides
#9087 b895113a0 Thanks @alexanderniebuhr! - Fixes the regression which broke bundling of image service for pre-rendered pages, which was introduced by #8854
#9058 5ef89ef33 Thanks @Princesseuh! - Add a new settings panel to the dev overlay
#9045 84312f24f Thanks @rishi-raj-jain! - Fixes preview server trailingSlash handling for request URLs with query strings
Updated dependencies [4537ecf0d]:
- @astrojs/markdown-remark @3.5.0

`v3.5.3`

Compare Source

Patch Changes

#9069 50164f5e3 Thanks @natemoo-re! - Fix a regression introduced in 3.5.0 related to content collection styles

`v3.5.2`

Compare Source

Patch Changes

#9057 1bc331968 Thanks @ematipico! - Correctly infer the presence of an user middleware

`v3.5.1`

Compare Source

Patch Changes

#9037 ea71975ec Thanks @sarah11918! - Updates i18n configuration reference
#9051 15b84ccb9 Thanks @ematipico! - Fix a regression where endpoints were incorrectly processed during SSG build when trailingSlash: "always"
#9042 7dedd17fc Thanks @rishi-raj-jain! - Safely bail when the xclip command does not exist on Linux when trying to copy to clipboard with astro info
#9050 bf0286e50 Thanks @Princesseuh! - Fix --verbose flag not working
#9049 49b82edb2 Thanks @Princesseuh! - Fix image errors when images were used on the client

`v3.5.0`

Compare Source

Minor Changes

#8869 f5bdfa272 Thanks @matthewp! - ## Integration Hooks to add Middleware

It's now possible in Astro for an integration to add middleware on behalf of the user. Previously when a third party wanted to provide middleware, the user would need to create a src/middleware.ts file themselves. Now, adding third-party middleware is as easy as adding a new integration.

For integration authors, there is a new addMiddleware function in the astro:config:setup hook. This function allows you to specify a middleware module and the order in which it should be applied:

// my-package/middleware.js
import { defineMiddleware } from 'astro:middleware';

export const onRequest = defineMiddleware(async (context, next) => {
  const response = await next();

  if (response.headers.get('content-type') === 'text/html') {
    let html = await response.text();
    html = minify(html);
    return new Response(html, {
      status: response.status,
      headers: response.headers,
    });
  }

  return response;
});

You can now add your integration's middleware and specify that it runs either before or after the application's own defined middleware (defined in src/middleware.{js,ts})

// my-package/integration.js
export function myIntegration() {
  return {
    name: 'my-integration',
    hooks: {
      'astro:config:setup': ({ addMiddleware }) => {
        addMiddleware({
          entrypoint: 'my-package/middleware',
          order: 'pre',
        });
      },
    },
  };
}

#8854 3e1239e42 Thanks @natemoo-re! - Provides a new, experimental build cache for Content Collections as part of the Incremental Build RFC. This includes multiple refactors to Astro's build process to optimize how Content Collections are handled, which should provide significant performance improvements for users with many collections.

Users building a static site can opt-in to preview the new build cache by adding the following flag to your Astro config:
```
// astro.config.mjs
export default {
  experimental: {
    contentCollectionCache: true,
  },
};
```
When this experimental feature is enabled, the files generated from your content collections will be stored in the cacheDir (by default, node_modules/.astro) and reused between builds. Most CI environments automatically restore files in node_modules/ by default.

In our internal testing on the real world Astro Docs project, this feature reduces the bundling step of astro build from 133.20s to 10.46s, about 92% faster. The end-to-end astro build process used to take 4min 58s and now takes just over 1min for a total reduction of 80%.

If you run into any issues with this experimental feature, please let us know!

You can always bypass the cache for a single build by passing the --force flag to astro build.
```
astro build --force
```
#8963 fda3a0213 Thanks @matthewp! - Form support in View Transitions router

The <ViewTransitions /> router can now handle form submissions, allowing the same animated transitions and stateful UI retention on form posts that are already available on <a> links. With this addition, your Astro project can have animations in all of these scenarios:
- Clicking links between pages.
- Making stateful changes in forms (e.g. updating site preferences).
- Manually triggering navigation via the navigate() API.
This feature is opt-in for semver reasons and can be enabled by adding the handleForms prop to the ` component:

`v3.4.4`

Compare Source

Patch Changes

#9000 35739d01e Thanks @martrapp! - Fixes an error in dev mode on Safari where view transitions prevented navigating to pages with client:only components
#9014 d979b8f0a Thanks @Princesseuh! - Add animations, shadows and general styling tweaks to the Dev Overlay to better match the intended design.
#8996 3988bbcc9 Thanks @bluwy! - Adds compatibility for shiki languages with the path property
#8986 910eb00fe Thanks @Princesseuh! - Fix sizes attribute not being present on source elements when using it on the Picture component

`v3.4.3`

Compare Source

Patch Changes

#8981 ab7e745cc Thanks @matthewp! - Increase the scroll restoration throttle time
#8940 937522fb7 Thanks @MarvinXu! - Omit nullish and falsy (non-zero) values when stringifying object-form style attributes in Astro files

`v3.4.2`

Compare Source

Patch Changes

#8977 40a061679 Thanks @matthewp! - Prevent route announcer from being visible
#8929 2da33b7a1 Thanks @lilnasy! - Fixes an issue where rendering the same slot multiple times invoked it only once.
#8978 cc3278bb6 Thanks @Princesseuh! - In the dev overlay, add a tooltip showing the currently hovered / focused plugin's name

`v3.4.1`

Compare Source

Patch Changes

#8966 262cef248 Thanks @Princesseuh! - Fix Dev Overlay not working properly when view transitions are enabled
#8932 5fed432b0 Thanks @Princesseuh! - Fixed window component appearing over the dev overlay on small windows. Added a maximum length to sections of the tooltip component
#8965 430c470ac Thanks @matthewp! - Move VT route announcer styles to a class

Doing so allows stricter CSP policies.
#8762 35cd810f0 Thanks @evadecker! - Upgrades Zod to 3.22.4
#8928 ca90b47cf Thanks @HiDeoo! - Renames dev overlay UI Toolkit component names for consistency.

`v3.4.0`

Compare Source

Minor Changes

#8755 fe4079f05 Thanks @matthewp! - Page Partials

A page component can now be identified as a partial page, which will render its HTML content without including a <! DOCTYPE html> declaration nor any <head> content.

A rendering library, like htmx or Stimulus or even just jQuery can access partial content on the client to dynamically update only parts of a page.

Pages marked as partials do not have a doctype or any head content included in the rendered result. You can mark any page as a partial by setting this option:

`v3.3.4`

Compare Source

Patch Changes

#8877 26b77b8fe Thanks @bluwy! - Fixes CSS modules ordering by rendering styles before links
Updated dependencies [341ef6578]:
- @astrojs/telemetry @3.0.4

`v3.3.3`

Compare Source

Patch Changes

#8870 5ea6ee0ed Thanks @xstevenyung! - prevent production install on astro add cmd
#8840 5c888c10b Thanks @martrapp! - Fixes styles of client:only components not persisting during view transitions in dev mode
#8814 ad2bb9155 Thanks @lilnasy! - Fix an issue where 500.astro did not render when the middleware threw an error.
#8863 326e17893 Thanks @florian-lefebvre! - Fixes an issue where the dev server logged the full file path on updates.

`v3.3.2`

Compare Source

Patch Changes

#8852 [2c18e2d12](https://redirect.github.com/withastro/astro/commit/2c18e2

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate · 2024-09-23T02:38:25Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @astrojs/[email protected]
npm error Found: [email protected]
npm error node_modules/astro
npm error   dev astro@"3.6.5" from the root project
npm error   astro@"*" from [email protected]
npm error   node_modules/astro-compress
npm error     dev astro-compress@"2.2.28" from the root project
npm error
npm error Could not resolve dependency:
npm error peer astro@"^2.7.3" from @astrojs/[email protected]
npm error node_modules/@astrojs/image
npm error   dev @astrojs/image@"0.17.2" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/astro
npm error   peer astro@"^2.7.3" from @astrojs/[email protected]
npm error   node_modules/@astrojs/image
npm error     dev @astrojs/image@"0.17.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-10-03T04_57_38_594Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-10-03T04_57_38_594Z-debug-0.log

codiumai-pr-agent-pro · 2024-10-03T04:58:17Z

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 issues with the `npm ci` command, which requires the `package.json` and `package-lock.json` files to be in sync. The following problems were identified: The lock file contains dependencies that do not match the required versions specified in `package.json`. Several dependencies are missing from the lock file. The lock file's versions for various packages do not satisfy the required versions. The error code `EUSAGE` indicates that the lock file needs to be updated with `npm install` to resolve these discrepancies.
Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 461: npm warn node_modules/astro 462: npm warn dev astro@"3.6.5" from the root project 463: npm warn 4 more (@astrojs/image, @astrojs/markdown-remark, ...) 464: npm warn 465: npm warn Could not resolve dependency: 466: npm warn peer astro@"^2.6.5" from @astrojs/[email protected] 467: npm warn node_modules/@astrojs/tailwind 468: npm warn dev @astrojs/tailwind@"4.0.0" from the root project 469: npm error code EUSAGE 470: npm error 471: npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing. 472: npm error 473: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 474: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 475: npm error Missing: @vitejs/[email protected] from lock file 476: npm error Missing: [email protected] from lock file 477: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 478: npm error Missing: @babel/[email protected] from lock file 479: npm error Missing: @babel/[email protected] from lock file 480: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 481: npm error Missing: [email protected] from lock file 482: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 483: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 484: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 485: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 486: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 487: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 488: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 489: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 490: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 491: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 492: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 493: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 494: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 495: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 496: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 497: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 498: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 499: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 500: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 501: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 502: npm error Missing: @astrojs/[email protected] from lock file 503: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 504: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 505: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 506: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 507: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 508: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 509: npm error Missing: [email protected] from lock file 510: npm error Missing: [email protected] from lock file 511: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 512: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 513: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 514: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 515: npm error Missing: [email protected] from lock file 516: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 517: npm error Missing: [email protected] from lock file 518: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 519: npm error Missing: [email protected] from lock file 520: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 521: npm error Missing: [email protected] from lock file 522: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 523: npm error Missing: [email protected] from lock file 524: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 525: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 526: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 527: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 528: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 529: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 530: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 531: npm error Missing: [email protected] from lock file 532: npm error Missing: [email protected] from lock file 533: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 534: npm error Missing: [email protected] from lock file 535: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 536: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 537: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 538: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 539: npm error Missing: @esbuild/[email protected] from lock file 540: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 541: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 542: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 543: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 544: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 545: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 546: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 547: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 548: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 549: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 550: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 551: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 552: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 553: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 554: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 555: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 556: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 557: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 558: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 559: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 560: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 561: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 562: npm error Missing: @types/[email protected] from lock file 563: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 564: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 565: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 566: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 567: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 568: npm error Missing: @types/[email protected] from lock file 569: npm error Missing: [email protected] from lock file 570: npm error Missing: @types/[email protected] from lock file 571: npm error Missing: [email protected] from lock file 572: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 573: npm error Missing: [email protected] from lock file 574: npm error Missing: [email protected] from lock file 575: npm error Missing: [email protected] from lock file 576: npm error Missing: [email protected] from lock file 577: npm error Missing: [email protected] from lock file 578: npm error Missing: [email protected] from lock file 579: npm error Missing: [email protected] from lock file 580: npm error Missing: @types/[email protected] from lock file 581: npm error Missing: @types/[email protected] from lock file 582: npm error Missing: @types/[email protected] from lock file 583: npm error Missing: @types/[email protected] from lock file 584: npm error Missing: @types/[email protected] from lock file 585: npm error Missing: @types/[email protected] from lock file 586: npm error Missing: @types/[email protected] from lock file 587: npm error Missing: @types/[email protected] from lock file 588: npm error Missing: @types/[email protected] from lock file 589: npm error Missing: @types/[email protected] from lock file 590: npm error Missing: @types/[email protected] from lock file 591: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 592: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 593: npm error Missing: @types/[email protected] from lock file 594: npm error Missing: @types/[email protected] from lock file 595: npm error Missing: [email protected] from lock file 596: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 597: npm error Missing: [email protected] from lock file 598: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 599: npm error Missing: [email protected] from lock file 600: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 601: npm error Missing: [email protected] from lock file 602: npm error Missing: [email protected] from lock file 603: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 604: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 605: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 606: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 607: npm error Missing: [email protected] from lock file 608: npm error Missing: [email protected] from lock file 609: npm error Invalid: lock file's @jridgewell/[email protected] does not satisfy @jridgewell/[email protected] 610: npm error Missing: [email protected] from lock file 611: npm error Missing: [email protected] from lock file 612: npm error Missing: [email protected] from lock file 613: npm error Missing: @types/[email protected] from lock file 614: npm error Missing: [email protected] from lock file 615: npm error Missing: [email protected] from lock file 616: npm error Missing: @types/[email protected] from lock file 617: npm error Missing: @types/[email protected] from lock file 618: npm error Missing: [email protected] from lock file 619: npm error Missing: [email protected] from lock file 620: npm error Missing: [email protected] from lock file 621: npm error Missing: @ungap/[email protected] from lock file 622: npm error Missing: [email protected] from lock file 623: npm error Missing: [email protected] from lock file 624: npm error Missing: [email protected] from lock file 625: npm error Missing: [email protected] from lock file 626: npm error Missing: [email protected] from lock file 627: npm error Missing: [email protected] from lock file 628: npm error Missing: [email protected] from lock file 629: npm error Missing: [email protected] from lock file 630: npm error Missing: [email protected] from lock file 631: npm error Missing: [email protected] from lock file 632: npm error Missing: [email protected] from lock file 633: npm error Missing: [email protected] from lock file 634: npm error Missing: [email protected] from lock file 635: npm error Missing: [email protected] from lock file 636: npm error Missing: [email protected] from lock file 637: npm error Missing: [email protected] from lock file 638: npm error 639: npm error Clean install a project 640: npm error 641: npm error Usage: 642: npm error npm ci 643: npm error 644: npm error Options: 645: npm error [--install-strategy <hoisted\|nested\|shallow\|linked>] [--legacy-bundling] 646: npm error [--global-style] [--omit <dev\|optional\|peer> [--omit <dev\|optional\|peer> ...]] 647: npm error [--include <prod\|dev\|optional\|peer> [--include <prod\|dev\|optional\|peer> ...]] 648: npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit] 649: npm error [--no-bin-links] [--no-fund] [--dry-run] 650: npm error [-w\|--workspace <workspace-name> [-w\|--workspace <workspace-name> ...]] 651: npm error [-ws\|--workspaces] [--include-workspace-root] [--install-links] 652: npm error 653: npm error aliases: clean-install, ic, install-clean, isntall-clean 654: npm error 655: npm error Run "npm help ci" for more info 656: npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-03T04_57_55_523Z-debug-0.log 657: ##[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 · 2024-10-03T04:58:24Z

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 issues with the `npm ci` command, which requires the `package.json` and `package-lock.json` files to be in sync. The following problems were identified: The lock file contains invalid or missing dependencies that do not satisfy the required versions specified in `package.json`. Specific errors include: - Invalid versions for packages such as `@astrojs/react`, `astro`, `@babel/core`, and many others. - Missing dependencies like `@vitejs/plugin-react`, `ultrahtml`, and several others. The error code `EUSAGE` indicates that the lock file needs to be updated using `npm install` to resolve these discrepancies.
Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 464: npm warn node_modules/astro 465: npm warn dev astro@"3.6.5" from the root project 466: npm warn 4 more (@astrojs/image, @astrojs/markdown-remark, ...) 467: npm warn 468: npm warn Could not resolve dependency: 469: npm warn peer astro@"^2.6.5" from @astrojs/[email protected] 470: npm warn node_modules/@astrojs/tailwind 471: npm warn dev @astrojs/tailwind@"4.0.0" from the root project 472: npm error code EUSAGE 473: npm error 474: npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing. 475: npm error 476: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 477: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 478: npm error Missing: @vitejs/[email protected] from lock file 479: npm error Missing: [email protected] from lock file 480: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 481: npm error Missing: @babel/[email protected] from lock file 482: npm error Missing: @babel/[email protected] from lock file 483: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 484: npm error Missing: [email protected] from lock file 485: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 486: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 487: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 488: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 489: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 490: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 491: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 492: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 493: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 494: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 495: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 496: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 497: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 498: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 499: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 500: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 501: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 502: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 503: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 504: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 505: npm error Missing: @astrojs/[email protected] from lock file 506: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 507: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 508: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 509: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 510: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 511: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 512: npm error Missing: [email protected] from lock file 513: npm error Missing: [email protected] from lock file 514: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 515: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 516: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 517: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 518: npm error Missing: [email protected] from lock file 519: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 520: npm error Missing: [email protected] from lock file 521: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 522: npm error Missing: [email protected] from lock file 523: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 524: npm error Missing: [email protected] from lock file 525: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 526: npm error Missing: [email protected] from lock file 527: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 528: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 529: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 530: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 531: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 532: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 533: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 534: npm error Missing: [email protected] from lock file 535: npm error Missing: [email protected] from lock file 536: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 537: npm error Missing: [email protected] from lock file 538: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 539: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 540: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 541: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 542: npm error Missing: @esbuild/[email protected] from lock file 543: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 544: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 545: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 546: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 547: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 548: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 549: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 550: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 551: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 552: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 553: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 554: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 555: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 556: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 557: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 558: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 559: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 560: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 561: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 562: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 563: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 564: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 565: npm error Missing: @types/[email protected] from lock file 566: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 567: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 568: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 569: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 570: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 571: npm error Missing: @types/[email protected] from lock file 572: npm error Missing: [email protected] from lock file 573: npm error Missing: @types/[email protected] from lock file 574: npm error Missing: [email protected] from lock file 575: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 576: npm error Missing: [email protected] from lock file 577: npm error Missing: [email protected] from lock file 578: npm error Missing: [email protected] from lock file 579: npm error Missing: [email protected] from lock file 580: npm error Missing: [email protected] from lock file 581: npm error Missing: [email protected] from lock file 582: npm error Missing: [email protected] from lock file 583: npm error Missing: @types/[email protected] from lock file 584: npm error Missing: @types/[email protected] from lock file 585: npm error Missing: @types/[email protected] from lock file 586: npm error Missing: @types/[email protected] from lock file 587: npm error Missing: @types/[email protected] from lock file 588: npm error Missing: @types/[email protected] from lock file 589: npm error Missing: @types/[email protected] from lock file 590: npm error Missing: @types/[email protected] from lock file 591: npm error Missing: @types/[email protected] from lock file 592: npm error Missing: @types/[email protected] from lock file 593: npm error Missing: @types/[email protected] from lock file 594: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 595: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 596: npm error Missing: @types/[email protected] from lock file 597: npm error Missing: @types/[email protected] from lock file 598: npm error Missing: [email protected] from lock file 599: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 600: npm error Missing: [email protected] from lock file 601: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 602: npm error Missing: [email protected] from lock file 603: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 604: npm error Missing: [email protected] from lock file 605: npm error Missing: [email protected] from lock file 606: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 607: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 608: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 609: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 610: npm error Missing: [email protected] from lock file 611: npm error Missing: [email protected] from lock file 612: npm error Invalid: lock file's @jridgewell/[email protected] does not satisfy @jridgewell/[email protected] 613: npm error Missing: [email protected] from lock file 614: npm error Missing: [email protected] from lock file 615: npm error Missing: [email protected] from lock file 616: npm error Missing: @types/[email protected] from lock file 617: npm error Missing: [email protected] from lock file 618: npm error Missing: [email protected] from lock file 619: npm error Missing: @types/[email protected] from lock file 620: npm error Missing: @types/[email protected] from lock file 621: npm error Missing: [email protected] from lock file 622: npm error Missing: [email protected] from lock file 623: npm error Missing: [email protected] from lock file 624: npm error Missing: @ungap/[email protected] from lock file 625: npm error Missing: [email protected] from lock file 626: npm error Missing: [email protected] from lock file 627: npm error Missing: [email protected] from lock file 628: npm error Missing: [email protected] from lock file 629: npm error Missing: [email protected] from lock file 630: npm error Missing: [email protected] from lock file 631: npm error Missing: [email protected] from lock file 632: npm error Missing: [email protected] from lock file 633: npm error Missing: [email protected] from lock file 634: npm error Missing: [email protected] from lock file 635: npm error Missing: [email protected] from lock file 636: npm error Missing: [email protected] from lock file 637: npm error Missing: [email protected] from lock file 638: npm error Missing: [email protected] from lock file 639: npm error Missing: [email protected] from lock file 640: npm error Missing: [email protected] from lock file 641: npm error 642: npm error Clean install a project 643: npm error 644: npm error Usage: 645: npm error npm ci 646: npm error 647: npm error Options: 648: npm error [--install-strategy <hoisted\|nested\|shallow\|linked>] [--legacy-bundling] 649: npm error [--global-style] [--omit <dev\|optional\|peer> [--omit <dev\|optional\|peer> ...]] 650: npm error [--include <prod\|dev\|optional\|peer> [--include <prod\|dev\|optional\|peer> ...]] 651: npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit] 652: npm error [--no-bin-links] [--no-fund] [--dry-run] 653: npm error [-w\|--workspace <workspace-name> [-w\|--workspace <workspace-name> ...]] 654: npm error [-ws\|--workspaces] [--include-workspace-root] [--install-links] 655: npm error 656: npm error aliases: clean-install, ic, install-clean, isntall-clean 657: npm error 658: npm error Run "npm help ci" for more info 659: npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-03T04_57_58_969Z-debug-0.log 660: ##[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 · 2024-10-03T04:58:25Z

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 issues with the `npm ci` command, which requires the `package.json` and `package-lock.json` files to be in sync. The following issues were identified: The lock file contains versions of packages that do not satisfy the versions specified in `package.json`. Several packages are missing from the lock file. The error code `EUSAGE` indicates that the lock file needs to be updated with `npm install` to resolve these discrepancies.
Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 464: npm warn node_modules/astro 465: npm warn dev astro@"3.6.5" from the root project 466: npm warn 4 more (@astrojs/image, @astrojs/markdown-remark, ...) 467: npm warn 468: npm warn Could not resolve dependency: 469: npm warn peer astro@"^2.6.5" from @astrojs/[email protected] 470: npm warn node_modules/@astrojs/tailwind 471: npm warn dev @astrojs/tailwind@"4.0.0" from the root project 472: npm error code EUSAGE 473: npm error 474: npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing. 475: npm error 476: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 477: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 478: npm error Missing: @vitejs/[email protected] from lock file 479: npm error Missing: [email protected] from lock file 480: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 481: npm error Missing: @babel/[email protected] from lock file 482: npm error Missing: @babel/[email protected] from lock file 483: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 484: npm error Missing: [email protected] from lock file 485: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 486: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 487: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 488: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 489: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 490: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 491: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 492: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 493: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 494: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 495: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 496: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 497: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 498: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 499: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 500: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 501: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 502: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 503: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 504: npm error Invalid: lock file's @babel/[email protected] does not satisfy @babel/[email protected] 505: npm error Missing: @astrojs/[email protected] from lock file 506: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 507: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 508: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 509: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 510: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 511: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 512: npm error Missing: [email protected] from lock file 513: npm error Missing: [email protected] from lock file 514: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 515: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 516: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 517: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 518: npm error Missing: [email protected] from lock file 519: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 520: npm error Missing: [email protected] from lock file 521: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 522: npm error Missing: [email protected] from lock file 523: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 524: npm error Missing: [email protected] from lock file 525: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 526: npm error Missing: [email protected] from lock file 527: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 528: npm error Invalid: lock file's @astrojs/[email protected] does not satisfy @astrojs/[email protected] 529: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 530: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 531: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 532: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 533: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 534: npm error Missing: [email protected] from lock file 535: npm error Missing: [email protected] from lock file 536: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 537: npm error Missing: [email protected] from lock file 538: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 539: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 540: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 541: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 542: npm error Missing: @esbuild/[email protected] from lock file 543: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 544: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 545: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 546: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 547: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 548: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 549: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 550: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 551: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 552: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 553: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 554: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 555: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 556: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 557: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 558: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 559: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 560: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 561: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 562: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 563: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 564: npm error Invalid: lock file's @esbuild/[email protected] does not satisfy @esbuild/[email protected] 565: npm error Missing: @types/[email protected] from lock file 566: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 567: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 568: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 569: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 570: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 571: npm error Missing: @types/[email protected] from lock file 572: npm error Missing: [email protected] from lock file 573: npm error Missing: @types/[email protected] from lock file 574: npm error Missing: [email protected] from lock file 575: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 576: npm error Missing: [email protected] from lock file 577: npm error Missing: [email protected] from lock file 578: npm error Missing: [email protected] from lock file 579: npm error Missing: [email protected] from lock file 580: npm error Missing: [email protected] from lock file 581: npm error Missing: [email protected] from lock file 582: npm error Missing: [email protected] from lock file 583: npm error Missing: @types/[email protected] from lock file 584: npm error Missing: @types/[email protected] from lock file 585: npm error Missing: @types/[email protected] from lock file 586: npm error Missing: @types/[email protected] from lock file 587: npm error Missing: @types/[email protected] from lock file 588: npm error Missing: @types/[email protected] from lock file 589: npm error Missing: @types/[email protected] from lock file 590: npm error Missing: @types/[email protected] from lock file 591: npm error Missing: @types/[email protected] from lock file 592: npm error Missing: @types/[email protected] from lock file 593: npm error Missing: @types/[email protected] from lock file 594: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 595: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 596: npm error Missing: @types/[email protected] from lock file 597: npm error Missing: @types/[email protected] from lock file 598: npm error Missing: [email protected] from lock file 599: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 600: npm error Missing: [email protected] from lock file 601: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 602: npm error Missing: [email protected] from lock file 603: npm error Invalid: lock file's @types/[email protected] does not satisfy @types/[email protected] 604: npm error Missing: [email protected] from lock file 605: npm error Missing: [email protected] from lock file 606: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 607: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 608: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 609: npm error Invalid: lock file's [email protected] does not satisfy [email protected] 610: npm error Missing: [email protected] from lock file 611: npm error Missing: [email protected] from lock file 612: npm error Invalid: lock file's @jridgewell/[email protected] does not satisfy @jridgewell/[email protected] 613: npm error Missing: [email protected] from lock file 614: npm error Missing: [email protected] from lock file 615: npm error Missing: [email protected] from lock file 616: npm error Missing: @types/[email protected] from lock file 617: npm error Missing: [email protected] from lock file 618: npm error Missing: [email protected] from lock file 619: npm error Missing: @types/[email protected] from lock file 620: npm error Missing: @types/[email protected] from lock file 621: npm error Missing: [email protected] from lock file 622: npm error Missing: [email protected] from lock file 623: npm error Missing: [email protected] from lock file 624: npm error Missing: @ungap/[email protected] from lock file 625: npm error Missing: [email protected] from lock file 626: npm error Missing: [email protected] from lock file 627: npm error Missing: [email protected] from lock file 628: npm error Missing: [email protected] from lock file 629: npm error Missing: [email protected] from lock file 630: npm error Missing: [email protected] from lock file 631: npm error Missing: [email protected] from lock file 632: npm error Missing: [email protected] from lock file 633: npm error Missing: [email protected] from lock file 634: npm error Missing: [email protected] from lock file 635: npm error Missing: [email protected] from lock file 636: npm error Missing: [email protected] from lock file 637: npm error Missing: [email protected] from lock file 638: npm error Missing: [email protected] from lock file 639: npm error Missing: [email protected] from lock file 640: npm error Missing: [email protected] from lock file 641: npm error 642: npm error Clean install a project 643: npm error 644: npm error Usage: 645: npm error npm ci 646: npm error 647: npm error Options: 648: npm error [--install-strategy <hoisted\|nested\|shallow\|linked>] [--legacy-bundling] 649: npm error [--global-style] [--omit <dev\|optional\|peer> [--omit <dev\|optional\|peer> ...]] 650: npm error [--include <prod\|dev\|optional\|peer> [--include <prod\|dev\|optional\|peer> ...]] 651: npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit] 652: npm error [--no-bin-links] [--no-fund] [--dry-run] 653: npm error [-w\|--workspace <workspace-name> [-w\|--workspace <workspace-name> ...]] 654: npm error [-ws\|--workspaces] [--include-workspace-root] [--install-links] 655: npm error 656: npm error aliases: clean-install, ic, install-clean, isntall-clean 657: npm error 658: npm error Run "npm help ci" for more info 659: npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-03T04_57_59_257Z-debug-0.log 660: ##[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 bot added the dependencies label Sep 23, 2024

chore(deps): update astro monorepo to v3

b4dca11

renovate bot force-pushed the renovate/major-3-astro-monorepo branch from 814c596 to b4dca11 Compare October 3, 2024 04:57

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update astro monorepo to v3 (major) #7

chore(deps): update astro monorepo to v3 (major) #7

renovate bot commented Sep 23, 2024 •

edited

Loading

renovate bot commented Sep 23, 2024 •

edited

Loading

codiumai-pr-agent-pro bot commented Oct 3, 2024

Configuration options

codiumai-pr-agent-pro bot commented Oct 3, 2024

Configuration options

codiumai-pr-agent-pro bot commented Oct 3, 2024

Configuration options

chore(deps): update astro monorepo to v3 (major) #7

Are you sure you want to change the base?

chore(deps): update astro monorepo to v3 (major) #7

Conversation

renovate bot commented Sep 23, 2024 • edited Loading

Release Notes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Configuration

renovate bot commented Sep 23, 2024 • edited Loading

⚠️ Artifact update problem

File name: package-lock.json

codiumai-pr-agent-pro bot commented Oct 3, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 3, 2024

CI Failure Feedback 🧐

Configuration options

codiumai-pr-agent-pro bot commented Oct 3, 2024

CI Failure Feedback 🧐

Configuration options

renovate bot commented Sep 23, 2024 •

edited

Loading

renovate bot commented Sep 23, 2024 •

edited

Loading