Skip to content

chore(deps): update astro monorepo - #21

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/astro-monorepo
Open

chore(deps): update astro monorepo#21
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/astro-monorepo

Conversation

@renovate

@renovaterenovateBot commented May 1, 2024•
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

PackageChangeAgeConfidence
@astrojs/tailwind (source)5.0.0 → 5.1.5ageconfidence
astro (source)3.0.12 → 3.6.5ageconfidence

Release Notes

withastro/astro (@​astrojs/tailwind)

v5.1.5

Compare Source

Patch Changes

v5.1.4

Compare Source

Patch Changes

v5.1.3

Compare Source

Patch Changes

v5.1.2

Compare Source

Patch Changes

v5.1.1

Compare Source

Patch Changes

v5.1.0

Compare Source

Minor Changes
Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes
withastro/astro (astro)

v3.6.5

Compare Source

Patch Changes

  • #​10287a90d685d7 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

  • #​92268f8a40e93 Thanks @​outofambit! - Fix i18n fallback routing with routing strategy of always-prefix

  • #​91793f28336d9 Thanks @​lilnasy! - Fixes an issue where the presence of a slot in a page led to an error.

  • #​9219067a65f5b Thanks @​natemoo-re! - Fix edge case where <style> updates inside of .astro files would ocassionally fail to update without reloading the page.

  • #​923627d3e86e4 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

v3.6.2

Compare Source

Patch Changes

v3.6.1

Compare Source

Patch Changes

v3.6.0

Compare Source

Minor Changes

  • #​9090c87223c21 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!

  • #​90920ea4bd47e 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.

  • #​9166cba6cf32d 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!

  • #​90920ea4bd47e 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

v3.5.6

Compare Source

Patch Changes

v3.5.5

Compare Source

Patch Changes

  • #​9091536c6c9fd Thanks @​ematipico! - The routingStrategyprefix-always should not force its logic to endpoints. This fixes some regression with astro:assets and @astrojs/rss.

  • #​910260e8210b0 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

v3.5.3

Compare Source

Patch Changes

v3.5.2

Compare Source

Patch Changes

v3.5.1

Compare Source

Patch Changes

v3.5.0

Compare Source

Minor Changes

  • #​8869f5bdfa272 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.jsimport{defineMiddleware}from'astro:middleware';exportconstonRequest=defineMiddleware(async(context,next)=>{constresponse=awaitnext();if(response.headers.get('content-type')==='text/html'){lethtml=awaitresponse.text();html=minify(html);returnnewResponse(html,{status: response.status,headers: response.headers,});}returnresponse;});

    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.jsexportfunctionmyIntegration(){return{name: 'my-integration',hooks: {'astro:config:setup': ({ addMiddleware })=>{addMiddleware({entrypoint: 'my-package/middleware',order: 'pre',});},},};}

  • #​88543e1239e42 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.mjsexportdefault{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

  • #​8963fda3a0213 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:

    ---// src/layouts/MainLayout.astroimport { ViewTransitions } from'astro:transitions';---
<html>
<head>
<!-- ... -->
<ViewTransitionshandleForms />
</head>
<body>
<!-- ... -->
</body>
</html>

    Just as with links, if you don't want the routing handling a form submission, you can opt out on a per-form basis with the data-astro-reload property:

    ---// src/components/Contact.astro---
<formclass="contact-form"action="/request"method="post"data-astro-reload>
<!-- ...-->
</form>

    Form support works on post method="get" and method="post" forms.

  • #​8954f0031b0a3 Thanks @​Princesseuh! - Updates the Image Services API to now delete original images from the final build that are not used outside of the optimization pipeline. For users with a large number of these images (e.g. thumbnails), this should reduce storage consumption and deployment times.

  • #​898426b1484e8 Thanks @​Princesseuh! - Adds a new property propertiesToHash to the Image Services API to allow specifying which properties of getImage() / <Image /> / <Picture /> should be used for hashing the result files when doing local transformations. For most services, this will include properties such as src, width or quality that directly changes the content of the generated image.

  • #​9010100b61ab5 Thanks @​jasikpark! - The <Picture /> component will now use jpg and jpeg respectively as fallback formats when the original image is in those formats.

  • #​8974143bacf39 Thanks @​ematipico! - Experimental support for i18n routing.

    Astro's experimental i18n routing API allows you to add your multilingual content with support for configuring a default language, computing relative page URLs, and accepting preferred languages provided by your visitor's browser. You can also specify fallback languages on a per-language basis so that your visitors can always be directed to existing content on your site.

    Enable the experimental routing option by adding an i18n object to your Astro configuration with a default location and a list of all languages to support:

    // astro.config.mjsimport{defineConfig}from'astro/config';exportdefaultdefineConfig({experimental: {i18n: {defaultLocale: 'en',locales: ['en','es','pt-br'],},},});

    Organize your content folders by locale depending on your i18n.routingStrategy, and Astro will handle generating your routes and showing your preferred URLs to your visitors.

    ├── src
│ ├── pages
│ │ ├── about.astro
│ │ ├── index.astro
│ │ ├── es
│ │ │ ├── about.astro
│ │ │ ├── index.astro
│ │ ├── pt-br
│ │ │ ├── about.astro
│ │ │ ├── index.astro

    Compute relative URLs for your links with getRelativeLocaleUrl from the new astro:i18n module:

    ---import { getRelativeLocaleUrl } from'astro:i18n';const aboutUrl =getRelativeLocaleUrl('pt-br', 'about');---
<p>Learn more <ahref={aboutURL}>About</a> this site!</p>

    Enabling i18n routing also provides two new properties for browser language detection: Astro.preferredLocale and Astro.preferredLocaleList. These combine the browser's Accept-Langauge header, and your site's list of supported languages and can be used to automatically respect your visitor's preferred languages.

    Read more about Astro's experimental i18n routing in our documentation.

  • #​895138e21d127 Thanks @​bluwy! - Prefetching is now supported in core

    You can enable prefetching for your site with the prefetch: true config. It is enabled by default when using View Transitions and can also be used to configure the prefetch behaviour used by View Transitions.

    You can enable prefetching by setting prefetch:true in your Astro config:

    // astro.config.jsimport{defineConfig}from'astro/config';exportdefaultdefineConfig({prefetch: true,});

    This replaces the @astrojs/prefetch integration, which is now deprecated and will eventually be removed.
    Visit the Prefetch guide for more information.

  • #​8903c5010aad3 Thanks @​horo-fox! - Adds experimental support for multiple shiki themes with the new markdown.shikiConfig.experimentalThemes option.

Patch Changes

  • #​90161ecc9aa32 Thanks @​Princesseuh! - Add ability to "Click to go editor" on auditted elements in the dev overlay

  • #​902929b83e9e4 Thanks @​Princesseuh! - Use UInt8Array instead of Buffer for both the input and return values of the transform() hook of the Image Service API to ensure compatibility with non-Node runtimes.

    This change is unlikely to affect you, but if you were previously relying on the return value being a Buffer, you may convert an UInt8Array to a Buffer using Buffer.from(your_array).

  • Updated dependencies [c5010aad3]:

v3.4.4

Compare Source

Patch Changes

v3.4.3

Compare Source

Patch Changes

v3.4.2

Compare Source

Patch Changes

v3.4.1

Compare Source

Patch Changes

v3.4.0

Compare Source

Minor Changes

  • #​8755fe4079f05 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:

    ---exportconst partial =true;---
<li>This is a single list item.</li>

    Other valid page files that can export a value (e.g. .mdx) can also be marked as partials.

    Read more about Astro page partials in our documentation.

  • #​88214740d761a Thanks @​Princesseuh! - Improved image optimization performance

    Astro will now generate optimized images concurrently at build time, which can significantly speed up build times for sites with many images. Additionally, Astro will now reuse the same buffer for all variants of an image. This should improve performance for websites with many variants of the same image, especially when using remote images.

    No code changes are required to take advantage of these improvements.

  • #​8757e99586787 Thanks @​Princesseuh! - Dev Overlay (experimental)

    Provides a new dev overlay for your browser preview that allows you to inspect your page islands, see helpful audits on performance and accessibility, and more. A Dev Overlay Plugin API is also included to allow you to add new features and third-party integrations to it.

    You can enable access to the dev overlay and its API by adding the following flag to your Astro config:

    // astro.config.mjsexportdefault{experimental: {devOverlay: true,},};

    Read the Dev Overlay Plugin API documentation for information about building your own plugins to integrate with Astro's dev overlay.

  • #​88808c3d4a859 Thanks @​alexanderniebuhr! - Moves the logic for overriding the image service out of core and into adapters. Also fixes a regression where a valid astro:assets image service configuration could be overridden.

v3.3.4

Compare Source

Patch Changes

v3.3.3

Compare Source

Patch Changes

v3.3.2

Compare Source

Patch Changes

v3.3.1

Compare Source

Patch Changes

v3.3.0

Compare Source

Minor Changes

  • #​88082993055be Thanks @​delucis! - Adds support for an --outDir CLI flag to astro build

  • #​8502c4270e476 Thanks @​bluwy! - Updates the internal shiki syntax highlighter to shikiji, an ESM-focused alternative that simplifies bundling and maintenance.

    There are no new options and no changes to how you author code blocks and syntax highlighting.

    Potentially breaking change: While this refactor should be transparent for most projects, the transition to shikiji now produces a smaller HTML markup by attaching a fallback color style to the pre or code element, instead of to the line span directly. For example:

    Before:

    <codeclass="astro-code" style="background-color: #&#8203;24292e"><pre><spanclass="line" style="color: #e1e4e8">my code</span></pre></code>

    After:

    <codeclass="astro-code" style="background-color: #&#8203;24292e; color: #e1e4e8"><pre><spanclass="line">my code<span></pre></code>

    This does not affect the colors as the span will inherit the color from the parent, but if you're relying on a specific HTML markup, please check your site carefully after upgrading to verify the styles.

  • #​8798f369fa250 Thanks @​Princesseuh! - Fixed tsconfig.json's new array format for extends not working. This was done by migrating Astro to use tsconfck instead of tsconfig-resolver to find and parse tsconfig.json files.

  • #​8620b2ae9ee0c Thanks @​Princesseuh! - Adds experimental support for generating srcset attributes and a new <Picture /> component.

srcset support

Two new properties have been added to `Image` and `getImage()`: `densities` and `widths`.
These properties can be used to generate a `srcset` attribute, either based on absolute widths in pixels (e.g. [300, 600, 900]) or pixel density descriptors (e.g. `["2x"]` or `[1.5, 2]`).
```astro
---
import { Image } from 'astro';
import myImage from './my-image.jpg';
---
<Image src={myImage} width={myImage.width / 2} densities={[1.5, 2]} alt="My cool image" />
```
```html
<img
src="/_astro/my_image.hash.webp"
srcset="/_astro/my_image.hash.webp 1.5x, /_astro/my_image.hash.webp 2x"
alt="My cool image"
/>
```

Picture component

The experimental `<Picture />` component can be used to generate a `<picture>` element with multiple `<source>` elements.
The example below uses the `format` property to generate a `<source>` in each of the specified image formats:
```astro
---
import { Picture } from 'astro:assets';
import myImage from './my-image.jpg';
---
<Picture src={myImage} formats={['avif', 'webp']} alt="My super image in multiple formats!" />
```
The above code will generate the following HTML, and allow the browser to determine the best image to display:
```html
<picture>
<source srcset="..." type="image/avif" />
<source srcset="..." type="image/webp" />
<img src="..." alt="My super image in multiple formats!" />
</picture>
```
The `Picture` component takes all the same props as the `Image` component, including the new `densities` and `widths` properties.
Patch Changes

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • 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 becomes conflicted, 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.

@cloudflare-workers-and-pages

cloudflare-workers-and-pagesBot commented May 1, 2024•
edited
Loading

Copy link
Copy Markdown

Deploying felicity with Cloudflare Pages Cloudflare Pages

Latest commit:720615d
Status: ✅ Deploy successful!
Preview URL:https://3c14a0b3.felicity.pages.dev
Branch Preview URL:https://renovate-astro-monorepo.felicity.pages.dev

View logs

@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch 2 times, most recently from 17e0b5e to 94d5bf9CompareJanuary 23, 2025 17:44
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 94d5bf9 to 639052aCompareJanuary 30, 2025 14:58
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 639052a to 086c6eaCompareFebruary 9, 2025 13:45
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 086c6ea to 6c79e0eCompareMarch 3, 2025 17:49
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch 3 times, most recently from 965c9ea to 796aa01CompareMarch 17, 2025 17:12
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 796aa01 to adc89ccCompareApril 1, 2025 12:34
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from adc89cc to c086509CompareApril 8, 2025 12:43
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from c086509 to fee1f9bCompareApril 24, 2025 08:42
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from fee1f9b to 54b16ffCompareMay 19, 2025 17:27
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch 2 times, most recently from 38c8b8b to 4b616e3CompareJune 4, 2025 07:04
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 4b616e3 to 3b8b85bCompareJune 22, 2025 14:32
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 3b8b85b to 7069c34CompareJuly 2, 2025 15:57
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch 2 times, most recently from e83ec6e to 8daa38aCompareAugust 13, 2025 16:06
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 8daa38a to b89bc53CompareAugust 19, 2025 17:58
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from b89bc53 to e5b09ffCompareAugust 31, 2025 09:57
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from e5b09ff to ae882f7CompareSeptember 25, 2025 21:36
@renovaterenovateBot changed the title fix(deps): update astro monorepochore(deps): update astro monorepoSep 25, 2025
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from ae882f7 to cc1cf16CompareOctober 21, 2025 10:38
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from cc1cf16 to 4af1c49CompareNovember 10, 2025 16:53
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 4af1c49 to 8b2ce2eCompareNovember 18, 2025 18:39
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 8b2ce2e to 60a1225CompareDecember 3, 2025 17:39
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 60a1225 to 492282cCompareDecember 31, 2025 15:29
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 492282c to 65c7bd4CompareJanuary 8, 2026 17:29
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 65c7bd4 to 356664fCompareJanuary 19, 2026 18:56
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 356664f to 495d5cfCompareJanuary 23, 2026 17:12
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 495d5cf to 0d2c952CompareFebruary 2, 2026 17:52
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch 2 times, most recently from 8d67d15 to 8413782CompareFebruary 17, 2026 21:04
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 8413782 to 4256c48CompareMarch 5, 2026 14:39
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 4256c48 to d9106cfCompareMarch 13, 2026 16:12
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch 2 times, most recently from 4af2fad to 1d349a9CompareApril 8, 2026 14:45
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 1d349a9 to 1b78b6dCompareApril 29, 2026 12:16
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch 2 times, most recently from 86c7613 to f0b313bCompareMay 18, 2026 19:56
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from f0b313b to e6be938CompareMay 28, 2026 17:48
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch 2 times, most recently from 342fae3 to 4e6c1ddCompareJune 11, 2026 18:43
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch 2 times, most recently from e31d97f to d920a86CompareJuly 17, 2026 00:54
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch 2 times, most recently from 357c6b3 to 25300d7CompareJuly 24, 2026 21:48
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 25300d7 to 140c6f2CompareJuly 30, 2026 15:47
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch 2 times, most recently from ce37d6f to 045966aCompareAugust 14, 2026 22:30
@renovate
renovateBotforce-pushed the renovate/astro-monorepo branch from 045966a to 720615dCompareAugust 26, 2026 21:34
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants