Update astro monorepo (major) #10

renovate · 2024-05-09T13:33:41Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/mdx (source)	`^2.0.3` -> `^4.0.0`
astro (source)	`^4.0.0` -> `^5.0.0`

Release Notes

withastro/astro (@astrojs/mdx)

Patch Changes

#12594 4f2fd0a Thanks @Princesseuh! - Fixes compatibility with Astro 5

`v4.0.0`

Compare Source

Major Changes

#12231 90ae100 Thanks @bluwy! - Handles the breaking change in Astro where content pages (including .mdx pages located within src/pages/) no longer respond with charset=utf-8 in the Content-Type header.

For MDX pages without layouts, @astrojs/mdx will automatically add the <meta charset="utf-8"> tag to the page by default. This reduces the boilerplate needed to write with non-ASCII characters. If your MDX pages have a layout, the layout component should include the <meta charset="utf-8"> tag.

If you require charset=utf-8 to render your page correctly, make sure that your layout components have the <meta charset="utf-8"> tag added.
#12008 5608338 Thanks @Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.

Starting from this release, no breaking changes will be introduced unless absolutely necessary.

To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.

Minor Changes

#12539 827093e Thanks @bluwy! - Drops node 21 support
#11741 6617491 Thanks @bluwy! - Updates adapter server entrypoint to use @astrojs/mdx/server.js

This is an internal change. Handling JSX in your .mdx files has been moved from Astro internals and is now the responsibility of this integration. You should not notice a change in your project, and no update to your code is required.

Patch Changes

#12075 a19530e Thanks @bluwy! - Parses frontmatter ourselves
#11861 3ab3b4e Thanks @bluwy! - Updates @astrojs/markdown-remark and handle its breaking changes
#12533 1b61fdf Thanks @ematipico! - Fixes a case where the MDX renderer couldn't be loaded when used as a direct dependency of an Astro integration.
Updated dependencies [3ab3b4e, 5608338, 560ef15, 83a2a64, 3ab3b4e, a19530e]:
- @astrojs/markdown-remark @6.0.0

`v3.1.9`

Compare Source

Patch Changes

#12245 1d4f6a4 Thanks @bmenant! - Add components property to MDXInstance type definition (RenderResult and module import)

`v3.1.8`

Compare Source

Patch Changes

Updated dependencies [710a1a1]:
- @astrojs/markdown-remark @5.3.0

`v3.1.7`

Compare Source

Patch Changes

#12026 40e7a1b Thanks @bluwy! - Initializes the MDX processor only when there's .mdx files

`v3.1.6`

Compare Source

Patch Changes

#11975 c9ae7b1 Thanks @bluwy! - Handles nested root hast node when optimizing MDX

`v3.1.5`

Compare Source

Patch Changes

#11818 88ef1d0 Thanks @bluwy! - Fixes CSS in the layout component to be ordered first before any other components in the MDX file

`v3.1.4`

Compare Source

Patch Changes

#11717 423614e Thanks @bluwy! - Fixes stack trace location when failed to parse an MDX file with frontmatter

`v3.1.3`

Compare Source

Patch Changes

Updated dependencies [49b5145]:
- @astrojs/markdown-remark @5.2.0

`v3.1.2`

Compare Source

Patch Changes

Updated dependencies [b6afe6a]:
- @astrojs/markdown-remark @5.1.1

`v3.1.1`

Compare Source

Patch Changes

#11263 7d59750 Thanks @wackbyte! - Refactor to use Astro's integration logger for logging

`v3.1.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.0.1`

Compare Source

Patch Changes

#10813 3cc3e2c Thanks @Xetera! - Omitting compiler-internal symbol from user components to fix breaking error messages

`v3.0.0`

Compare Source

Major Changes

#10935 ddd8e49 Thanks @bluwy! - Refactors the MDX transformation to rely only on the unified pipeline. Babel and esbuild transformations are removed, which should result in faster build times. The refactor requires using Astro v4.8.0 but no other changes are necessary.
#10935 ddd8e49 Thanks @bluwy! - Allows integrations after the MDX integration to update markdown.remarkPlugins and markdown.rehypePlugins, and have the plugins work in MDX too.

If your integration relies on Astro's previous behavior that prevents integrations from adding remark/rehype plugins for MDX, you will now need to configure @astrojs/mdx with extendMarkdownConfig: false and explicitly specify any remarkPlugins and rehypePlugins options instead.
#10935 ddd8e49 Thanks @bluwy! - Renames the optimize.customComponentNames option to optimize.ignoreElementNames to better reflect its usecase. Its behaviour is not changed and should continue to work as before.
#10935 ddd8e49 Thanks @bluwy! - Replaces the internal remark-images-to-component plugin with rehype-images-to-component to let users use additional rehype plugins for images

Patch Changes

#10935 ddd8e49 Thanks @bluwy! - Simplifies plain MDX components as hast element nodes to further improve HTML string inlining for the optimize option
#10935 ddd8e49 Thanks @bluwy! - Allows Vite plugins to transform .mdx files before the MDX plugin transforms it
#10935 ddd8e49 Thanks @bluwy! - Updates the optimize option to group static sibling nodes as a <Fragment />. This reduces the number of AST nodes and simplifies runtime rendering of MDX pages.
#10935 ddd8e49 Thanks @bluwy! - Tags the MDX component export for quicker component checks while rendering
#10935 ddd8e49 Thanks @bluwy! - Fixes export const components keys detection for the optimize option
#10935 ddd8e49 Thanks @bluwy! - Improves optimize handling for MDX components with attributes and inline MDX components

withastro/astro (astro)

`v5.0.4`

Compare Source

Patch Changes

#12653 e21c7e6 Thanks @sarah11918! - Updates a reference in an error message
#12585 a9373c0 Thanks @florian-lefebvre! - Fixes a case where process.env would be frozen despite changes made to environment variables in development
#12695 a203d5d Thanks @ascorbic! - Throws a more helpful error when images are missing
Updated dependencies [f13417b, 87231b1, a71e9b9]:
- @astrojs/markdown-remark @6.0.1

`v5.0.3`

Compare Source

Patch Changes

#12645 8704c54 Thanks @sarah11918! - Updates some reference links in error messages for new v5 docs.
#12641 48ca399 Thanks @ascorbic! - Fixes a bug where astro info --copy wasn't working correctly on macOS systems.
#12461 62939ad Thanks @kyr0! - Removes the misleading log message telling that a custom renderer is not recognized while it clearly is and works.
#12642 ff18b9c Thanks @ematipico! - Provides more information when logging a warning for accessing Astro.request.headers in prerendered pages
#12634 03958d9 Thanks @delucis! - Improves error message formatting for user config and content collection frontmatter
#12547 6b6e18d Thanks @mtwilliams-code! - Fixes a bug where URL search parameters weren't passed when using the i18n fallback feature.
#12449 e6b8017 Thanks @apatel369! - Fixes an issue where the custom assetFileNames configuration caused assets to be incorrectly moved to the server directory instead of the client directory, resulting in 404 errors when accessed from the client side.
#12518 e216250 Thanks @ematipico! - Fixes an issue where SSR error pages would return duplicated custom headers.
#12625 74bfad0 Thanks @ematipico! - Fixes an issue where the experimental.svg had incorrect type, resulting in some errors in the editors.
#12631 dec0305 Thanks @ascorbic! - Fixes a bug where the class attribute was rendered twice on the image component
#12623 0e4fecb Thanks @ascorbic! - Correctly handles images in content collections with uppercase file extensions
#12633 8a551c1 Thanks @bluwy! - Cleans up content layer sync during builds and programmatic sync() calls
#12640 22e405a Thanks @ascorbic! - Fixes a bug that caused content collections to be returned empty when run in a test environment
#12613 306c9f9 Thanks @matthewp! - Fix use of cloned requests in middleware with clientAddress

When using context.clientAddress or Astro.clientAddress Astro looks up the address in a hidden property. Cloning a request can cause this hidden property to be lost.

The fix is to pass the address as an internal property instead, decoupling it from the request.

`v5.0.2`

Compare Source

Patch Changes

#12601 0724929 Thanks @ascorbic! - Includes "undefined" in types for getEntry

`v5.0.1`

Compare Source

Patch Changes

#12590 92c269b Thanks @kidonng! - fix: devtools warnings about dev toolbar form fields

`v5.0.0`

Compare Source

Major Changes

#11798 e9e2139 Thanks @matthewp! - Unflag globalRoutePriority

The previously experimental feature globalRoutePriority is now the default in Astro 5.

This was a refactoring of route prioritization in Astro, making it so that injected routes, file-based routes, and redirects are all prioritized using the same logic. This feature has been enabled for all Starlight projects since it was added and should not affect most users.
#11864 ee38b3a Thanks @ematipico! - ### [changed]: entryPoint type inside the hook astro:build:ssr
In Astro v4.x, the entryPoint type was RouteData.

Astro v5.0 the entryPoint type is IntegrationRouteData, which contains a subset of the RouteData type. The fields isIndex and fallbackRoutes were removed.

What should I do?

Update your adapter to change the type of entryPoint from RouteData to IntegrationRouteData.

-import type {RouteData} from 'astro';
+import type {IntegrationRouteData} from "astro"

-function useRoute(route: RouteData) {
+function useRoute(route: IntegrationRouteData) {

}

#12524 9f44019 Thanks @bluwy! - Bumps Vite to ^6.0.1 and handles its breaking changes
#10742 b6fbdaa Thanks @ematipico! - The lowest version of Node supported by Astro is now Node v18.17.1 and higher.
#11916 46ea29f Thanks @bluwy! - Updates how the build.client and build.server option values get resolved to match existing documentation. With this fix, the option values will now correctly resolve relative to the outDir option. So if outDir is set to ./dist/nested/, then by default:
- build.client will resolve to <root>/dist/nested/client/
- build.server will resolve to <root>/dist/nested/server/
Previously the values were incorrectly resolved:
- build.client was resolved to <root>/dist/nested/dist/client/
- build.server was resolved to <root>/dist/nested/dist/server/
If you were relying on the previous build paths, make sure that your project code is updated to the new build paths.
#11982 d84e444 Thanks @Princesseuh! - Adds a default exclude and include value to the tsconfig presets. {projectDir}/dist is now excluded by default, and {projectDir}/.astro/types.d.ts and {projectDir}/**/* are included by default.

Both of these options can be overridden by setting your own values to the corresponding settings in your tsconfig.json file.
#11861 3ab3b4e Thanks @bluwy! - Cleans up Astro-specfic metadata attached to vfile.data in Remark and Rehype plugins. Previously, the metadata was attached in different locations with inconsistent names. The metadata is now renamed as below:
- vfile.data.__astroHeadings -> vfile.data.astro.headings
- vfile.data.imagePaths -> vfile.data.astro.imagePaths
The types of imagePaths has also been updated from Set<string> to string[]. The vfile.data.astro.frontmatter metadata is left unchanged.

While we don't consider these APIs public, they can be accessed by Remark and Rehype plugins that want to re-use Astro's metadata. If you are using these APIs, make sure to access them in the new locations.
#11987 bf90a53 Thanks @florian-lefebvre! - The locals object can no longer be overridden

Middleware, API endpoints, and pages can no longer override the locals object in its entirety. You can still append values onto the object, but you can not replace the entire object and delete its existing values.

If you were previously overwriting like so:
```
ctx.locals = {
  one: 1,
  two: 2,
};
```
This can be changed to an assignment on the existing object instead:
```
Object.assign(ctx.locals, {
  one: 1,
  two: 2,
});
```
#11908 518433e Thanks @Princesseuh! - The image.endpoint config now allow customizing the route of the image endpoint in addition to the entrypoint. This can be useful in niche situations where the default route /_image conflicts with an existing route or your local server setup.
```
import { defineConfig } from 'astro/config';

defineConfig({
  image: {
    endpoint: {
      route: '/image',
      entrypoint: './src/image_endpoint.ts',
    },
  },
});
```
#12008 5608338 Thanks @Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.

Starting from this release, no breaking changes will be introduced unless absolutely necessary.

To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.
#11679 ea71b90 Thanks @florian-lefebvre! - The astro:env feature introduced behind a flag in v4.10.0 is no longer experimental and is available for general use. If you have been waiting for stabilization before using astro:env, you can now do so.

This feature lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client.

To configure a schema, add the env option to your Astro config and define your client and server variables. If you were previously using this feature, please remove the experimental flag from your Astro config and move your entire env configuration unchanged to a top-level option.
```
import { defineConfig, envField } from 'astro/config';

export default defineConfig({
  env: {
    schema: {
      API_URL: envField.string({ context: 'client', access: 'public', optional: true }),
      PORT: envField.number({ context: 'server', access: 'public', default: 4321 }),
      API_SECRET: envField.string({ context: 'server', access: 'secret' }),
    },
  },
});
```
You can import and use your defined variables from the appropriate /client or /server module:

`v4.16.17`

Compare Source

Patch Changes

#12632 e7d14c3 Thanks @ematipico! - Fixes an issue where the checkOrigin feature wasn't correctly checking the content-type header

`v4.16.16`

Compare Source

Patch Changes

#12542 65e50eb Thanks @kadykov! - Fix JPEG image size determination
#12525 cf0d8b0 Thanks @ematipico! - Fixes an issue where with i18n enabled, Astro couldn't render the 404.astro component for non-existent routes.

`v4.16.15`

Compare Source

Patch Changes

#12498 b140a3f Thanks @ematipico! - Fixes a regression where Astro was trying to access Request.headers

`v4.16.14`

Compare Source

Patch Changes

#12480 c3b7e7c Thanks @matthewp! - Removes the default throw behavior in astro:env
#12444 28dd3ce Thanks @ematipico! - Fixes an issue where a server island hydration script might fail case the island ID misses from the DOM.
#12476 80a9a52 Thanks @florian-lefebvre! - Fixes a case where the Content Layer glob() loader would not update when renaming or deleting an entry
#12418 25baa4e Thanks @oliverlynch! - Fix cached image redownloading if it is the first asset
#12477 46f6b38 Thanks @ematipico! - Fixes an issue where the SSR build was emitting the dist/server/entry.mjs file with an incorrect import at the top of the file/
#12365 a23985b Thanks @apatel369! - Fixes an issue where Astro.currentLocale was not correctly returning the locale for 404 and 500 pages.

`v4.16.13`

Compare Source

Patch Changes

#12436 453ec6b Thanks @martrapp! - Fixes a potential null access in the clientside router
#12392 0462219 Thanks @apatel369! - Fixes an issue where scripts were not correctly injected during the build. The issue was triggered when there were injected routes with the same entrypoint and different pattern

`v4.16.12`

Compare Source

Patch Changes

#12420 acac0af Thanks @ematipico! - Fixes an issue where the dev server returns a 404 status code when a user middleware returns a valid Response.

`v4.16.11`

Compare Source

Patch Changes

#12305 f5f7109 Thanks @florian-lefebvre! - Fixes a case where the error overlay would not escape the message
#12402 823e73b Thanks @ematipico! - Fixes a case where Astro allowed to call an action without using Astro.callAction. This is now invalid, and Astro will show a proper error.

`v4.16.10`

Compare Source

Patch Changes

#12311 bf2723e Thanks @dinesh-58! - Adds checked to the list of boolean attributes.
#12363 222f718 Thanks @Fryuni! - Fixes code generated by astro add command when adding a version of an integration other than the default latest.
#12368 493fe43 Thanks @bluwy! - Improves error logs when executing commands
#12355 c4726d7 Thanks @apatel369! - Improves error reporting for invalid frontmatter in MDX files during the astro build command. The error message now includes the file path where the frontmatter parsing failed.

`v4.16.9`

Compare Source

Patch Changes

#12333 836cd91 Thanks @imattacus! - Destroy the server response stream if async error is thrown
#12358 7680349 Thanks @spacedawwwg! - Honors inlineAstroConfig parameter in getViteConfig when creating a logger
#12353 35795a1 Thanks @hippotastic! - Fixes an issue in dev server watch file handling that could cause multiple restarts for a single file change.
#12351 5751488 Thanks @florian-lefebvre! - Reverts a change made in 4.16.6 that prevented usage of astro:env secrets inside middleware in SSR
#12346 20e5a84 Thanks @bluwy! - Fixes sourcemap generation when prefetch is enabled
#12349 1fc83d3 Thanks @norskeld! - Fixes the getImage options type so it properly extends ImageTransform

`v4.16.8`

Compare Source

Patch Changes

#12338 9ca89b3 Thanks @situ2001! - Resets NODE_ENV to ensure install command run in dev mode
#12286 9d6bcdb Thanks @florian-lefebvre! - Fixes a case where a warning for experimental astro:env support would be shown when using an adapter but not actually using astro:env
#12342 ffc836b Thanks @liruifengv! - Fixes a typo in the command name of the CLI
#12301 0cfc69d Thanks @apatel369! - Fixes an issue with action handler context by passing the correct context (ActionAPIContext).
#12312 5642ef9 Thanks @koyopro! - Fixes an issue where using getViteConfig() returns incorrect and duplicate configuration
#12245 1d4f6a4 Thanks @bmenant! - Add components property to MDXInstance type definition (RenderResult and module import)
#12340 94eaeea Thanks @ematipico! - Fixes an issue where Astro actions didn't work when base was different from /

`v4.16.7`

Compare Source

Patch Changes

#12263 e9e8080 Thanks @Fryuni! - Fixes conflict between server islands and on-demand dynamic routes in the form of /[...rest] or /[paramA]/[paramB].
#12279 b781f88 Thanks @jsparkdev! - Update wrong error message
#12273 c2ee963 Thanks @ascorbic! - Fixes an issue with some package managers where sites would not build if TypeScript was not installed.
#12235 a75bc5e Thanks @ematipico! - Fixes a bug where Astro Actions couldn't redirect to the correct pathname when there was a rewrite involved.
#11839 ff522b9 Thanks @icaliman! - Fixes error when returning a top-level null from an Astro file frontmatter
#12272 388d237 Thanks @ascorbic! - Correctly handles local images when using a base path in SSR

`v4.16.6`

Compare Source

Patch Changes

#11823 a3d30a6 Thanks @DerTimonius! - fix: improve error message when inferSize is used in local images with the Image component
#12227 8b1a641 Thanks @florian-lefebvre! - Fixes a case where environment variables would not be refreshed when using astro:env
#12239 2b6daa5 Thanks @ematipico! - BREAKING CHANGE to the experimental Container API only

Changes the default page rendering behavior of Astro components in containers, and adds a new option partial: false to render full Astro pages as before.

Previously, the Container API was rendering all Astro components as if they were full Astro pages containing <!DOCTYPE html> by default. This was not intended, and now by default, all components will render as page partials: only the contents of the components without a page shell.

To render the component as a full-fledged Astro page, pass a new option called partial: false to renderToString() and renderToResponse():
```
import { experimental_AstroContainer as AstroContainer } from 'astro/container';
import Card from '../src/components/Card.astro';

const container = AstroContainer.create();

await container.renderToString(Card); // the string will not contain `<!DOCTYPE html>`
await container.renderToString(Card, { partial: false }); // the string will contain `<!DOCTYPE html>`
```

`v4.16.5`

Compare Source

Patch Changes

#12232 ff68ba5 Thanks @martrapp! - Fixes an issue with cssesc in dev mode when setting vite.ssr.noExternal: true

`v4.16.4`

Compare Source

Patch Changes

#12223 79ffa5d Thanks @ArmandPhilippot! - Fixes a false positive reported by the dev toolbar Audit app where a label was considered missing when associated with a button

The button element can be used with a label (e.g. to create a switch) and should not be reported as an accessibility issue when used as a child of a label.
#12199 c351352 Thanks @ematipico! - Fixes a regression in the computation of Astro.currentLocale
#12222 fb55695 Thanks @ematipico! - Fixes an issue where the edge middleware couldn't correctly compute the client IP address when calling ctx.clientAddress()

`v4.16.3`

Compare Source

Patch Changes

#12220 b049359 Thanks @bluwy! - Fixes accidental internal setOnSetGetEnv parameter rename that caused runtime errors
#12197 2aa2dfd Thanks @ematipico! - Fix a regression where a port was incorrectly added to the Astro.url

`v4.16.2`

Compare Source

Patch Changes

#12206 12b0022 Thanks @bluwy! - Reverts https://github.com/withastro/astro/pull/12173 which caused Can't modify immutable headers warnings and 500 errors on Cloudflare Pages

`v4.16.1`

Compare Source

Patch Changes

#12177 a4ffbfa Thanks @matthewp! - Ensure we target scripts for execution in the router

Using document.scripts is unsafe because if the application has a name="scripts" this will shadow the built-in document.scripts. Fix is to use getElementsByTagName to ensure we're only grabbing real scripts.
#12173 2d10de5 Thanks @ematipico! - Fixes a bug where Astro Actions couldn't redirect to the correct pathname when there was a rewrite involved.

`v4.16.0`

Compare Source

Minor Changes

#12039 710a1a1 Thanks @ematipico! - Adds a markdown.shikiConfig.langAlias option that allows aliasing a non-supported code language to a known language. This is useful when the language of your code samples is not a built-in Shiki language, but you want your Markdown source to contain an accurate language while also displaying syntax highlighting.

The following example configures Shiki to highlight cjs code blocks using the javascript syntax highlighter:
```
import { defineConfig } from 'astro/config';

export default defineConfig({
  markdown: {
    shikiConfig: {
      langAlias: {
        c
```

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

👻 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.

vercel · 2024-05-09T13:33:42Z

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
tompluess-astro	❌ Failed (Inspect)			Dec 3, 2024 1:35pm

renovate · 2024-12-03T13:35:18Z

⚠️ 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   astro@"^5.0.0" from the root project
npm error   peer astro@"^5.0.0" from @astrojs/[email protected]
npm error   node_modules/@astrojs/mdx
npm error     @astrojs/mdx@"^4.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer astro@"^3.0.0 || ^4.0.0" from @astrojs/[email protected]
npm error node_modules/@astrojs/tailwind
npm error   @astrojs/tailwind@"^5.0.4" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/astro
npm error   peer astro@"^3.0.0 || ^4.0.0" from @astrojs/[email protected]
npm error   node_modules/@astrojs/tailwind
npm error     @astrojs/tailwind@"^5.0.4" 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-12-03T13_35_08_335Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-03T13_35_08_335Z-debug-0.log

vercel bot deployed to Preview May 9, 2024 13:34 View deployment

renovate bot force-pushed the renovate/major-astro-monorepo branch from dfa1882 to 246fd89 Compare May 13, 2024 17:38

vercel bot deployed to Preview May 13, 2024 17:39 View deployment

Update astro monorepo

69d2f41

renovate bot force-pushed the renovate/major-astro-monorepo branch from 246fd89 to 69d2f41 Compare December 3, 2024 13:35

renovate bot changed the title ~~Update dependency @astrojs/mdx to v3~~ Update astro monorepo (major) Dec 3, 2024

vercel bot had a problem deploying to Preview December 3, 2024 13:35 Failure

renovate bot changed the title ~~Update astro monorepo (major)~~ Update dependency astro to v5 Dec 8, 2024

renovate bot changed the title ~~Update dependency astro to v5~~ Update astro monorepo (major) Dec 8, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update astro monorepo (major) #10

Update astro monorepo (major) #10

renovate bot commented May 9, 2024 •

edited

Loading

vercel bot commented May 9, 2024 •

edited

Loading

renovate bot commented Dec 3, 2024

Update astro monorepo (major) #10

Are you sure you want to change the base?

Update astro monorepo (major) #10

Conversation

renovate bot commented May 9, 2024 • edited Loading

Release Notes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

What should I do?

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Configuration

vercel bot commented May 9, 2024 • edited Loading

renovate bot commented Dec 3, 2024

⚠️ Artifact update problem

File name: package-lock.json

renovate bot commented May 9, 2024 •

edited

Loading

vercel bot commented May 9, 2024 •

edited

Loading