fix(deps): update astro (major) - autoclosed #77

renovate · 2024-12-08T03:13:54Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/mdx (source)	`3.1.9` -> `4.0.1`
@astrojs/vercel (source)	`7.8.2` -> `8.0.0`
astro (source)	`4.16.10` -> `5.0.3`

Release Notes

withastro/astro (@astrojs/mdx)

`v4.0.1`

Compare Source

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

withastro/adapters (@astrojs/vercel)

`v8.0.0`

Compare Source

Major Changes

#375 e7881f7 Thanks @Princesseuh! - Updates internal code to works with Astro 5 changes to hybrid rendering. No changes are necessary to your project, apart from using Astro 5
#397 776a266 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.
#377 b77f99c Thanks @alexanderniebuhr! - Updates the adapter to use new IntegrationRouteData type
#451 f248546 Thanks @ematipico! - Updates esbuild dependency to v0.24.0
#384 7d83f60 Thanks @bluwy! - Removes deprecated speedInsights option in favor of Vercel's direct support: https://vercel.com/docs/speed-insights/quickstart
#392 3a49eb7 Thanks @Princesseuh! - Updates internal code for Astro 5 changes. No changes is required to your project, apart from using Astro 5

Minor Changes

#424 3351348 Thanks @ematipico! - Deprecates the entrypoints @astrojs/vercel/serverless and @astrojs/vercel/static. These will continue to work but are no longer documented and will be removed in a future version. We recommend updating to the @astrojs/vercel entrypoint as soon as you are able:
```
-import vercel from "@&#8203;astrojs/vercel/static"
+import vercel from "@&#8203;astrojs/vercel"
```
```
-import vercel from "@&#8203;astrojs/vercel/serverless"
+import vercel from "@&#8203;astrojs/vercel"
```
#447 7d9835f Thanks @laymonage! - Add support for Node 22 on Vercel serverless
#385 bb725b7 Thanks @florian-lefebvre! - Cleans up astro:env support

Patch Changes

#437 b725b49 Thanks @ematipico! - Fixes a regression where the @astrojs/vercel single entry point for the adapter was causing some regressions in users projects.

withastro/astro (astro)

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

Configuration

📅 Schedule: Branch creation - "every weekend on the 2nd week of the month" in timezone Europe/Zurich, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

renovate · 2024-12-08T03:13:54Z

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

Branch has one or more failed status checks

fix(deps): update astro

8f4011c

renovate bot changed the title ~~fix(deps): update astro (major)~~ fix(deps): update astro (major) - autoclosed Dec 8, 2024

renovate bot closed this Dec 8, 2024

renovate bot deleted the renovate/major-astro branch December 8, 2024 09:16

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update astro (major) - autoclosed #77

fix(deps): update astro (major) - autoclosed #77

renovate bot commented Dec 8, 2024

renovate bot commented Dec 8, 2024

fix(deps): update astro (major) - autoclosed #77

fix(deps): update astro (major) - autoclosed #77

Conversation

renovate bot commented Dec 8, 2024

Release Notes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Major Changes

Minor 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

Configuration

renovate bot commented Dec 8, 2024

Branch automerge failure