Skip to content

Update astro monorepo#181

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

Update astro monorepo#181
renovate[bot] wants to merge 1 commit intonextfrom
renovate/astro-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 25, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@astrojs/mdx (source) 0.18.2 → 0.19.7 age confidence
@astrojs/sitemap (source) 1.2.1 → 1.4.0 age confidence
@astrojs/solid-js (source) 2.1.0 → 2.2.1 age confidence
astro (source) 2.1.6 → 2.10.15 age confidence

Release Notes

withastro/astro (@​astrojs/mdx)

v0.19.7

Compare Source

Patch Changes

v0.19.6

Compare Source

Patch Changes
  • #​7185 339529fc8 Thanks @​bholmesdev! - Bring back improved style and script handling across content collection files. This addresses bugs found in a previous release to @astrojs/markdoc.

v0.19.5

Compare Source

Patch Changes

v0.19.4

Compare Source

Patch Changes
  • #​7178 57e65d247 Thanks @​bholmesdev! - Fix: revert Markdoc asset bleed changes. Production build issues were discovered that deserve a different fix.

v0.19.3

Compare Source

Patch Changes
  • #​6758 f558a9e20 Thanks @​bholmesdev! - Improve style and script handling across content collection files. This addresses style bleed present in @astrojs/markdoc v0.1.0

v0.19.2

Compare Source

Patch Changes

v0.19.1

Compare Source

Patch Changes

v0.19.0

Compare Source

Minor Changes
Patch Changes

v0.18.4

Compare Source

Patch Changes

v0.18.3

Compare Source

Patch Changes
withastro/astro (@​astrojs/sitemap)

v1.4.0

Compare Source

Minor Changes

v1.3.3

Compare Source

Patch Changes

v1.3.2

Compare Source

Patch Changes

v1.3.1

Compare Source

Patch Changes

v1.3.0

Compare Source

Minor Changes

v1.2.2

Compare Source

Patch Changes
withastro/astro (@​astrojs/solid-js)

v2.2.1

Compare Source

Patch Changes

v2.2.0

Compare Source

Minor Changes

  • #​7093 3d525efc9 Thanks @​matthewp! - Prevent removal of nested slots within islands

    This change introduces a new flag that renderers can add called supportsAstroStaticSlot. What this does is let Astro know that the render is sending <astro-static-slot> as placeholder values for static (non-hydrated) slots which Astro will then remove.

    This change is completely backwards compatible, but fixes bugs caused by combining ssr-only and client-side framework components like so:

    <Component>
  <div>
    <Component client:load>
      <span>Nested</span>
    </Component>
  </div>
</Component>
Patch Changes

v2.1.1

Compare Source

Patch Changes
  • #​6934 b6797fc85 Thanks @​matthewp! - Allow Solid ecosystem packages to not need special export map configuration. By default Solid is now treated as an external package in SSR, so any other dependent packages will receive the same instance.
withastro/astro (astro)

v2.10.15

Compare Source

Patch Changes

v2.10.14

Compare Source

Patch Changes

v2.10.13

Compare Source

Patch Changes

v2.10.12

Compare Source

Patch Changes
  • #​8144 04caa99c4 Thanks @​lilnasy! - Fixed an issue where data entries' id included backslashes instead of forward slashes on Windows.

v2.10.11

Compare Source

Patch Changes

v2.10.10

Compare Source

Patch Changes

  • #​8127 b12c8471f Thanks @​natemoo-re! - Do not throw Error when users pass an object with a "type" property

  • #​8092 7177f7579 Thanks @​natemoo-re! - Ensure dotfiles are cleaned during static builds

  • #​8122 fa6b68a77 Thanks @​natemoo-re! - Improve fidelity of time stats when running astro build

  • #​8070 097a8e4e9 Thanks @​lilnasy! - Fix a handful of edge cases with prerendered 404/500 pages

  • #​8123 1f6497c33 Thanks @​natemoo-re! - Open to configured base when astro dev --open runs

  • #​8105 0e0fa605d Thanks @​martrapp! - ViewTransition: bug fix for lost scroll position in browser history

  • #​8116 b290f0a99 Thanks @​martrapp! - On back navigation only animate view transitions that were animated going forward.

  • #​7778 d6b494376 Thanks @​y-nk! - Added support for optimizing remote images from authorized sources when using astro:assets. This comes with two new parameters to specify which domains (image.domains) and host patterns (image.remotePatterns) are authorized for remote images.

    For example, the following configuration will only allow remote images from astro.build to be optimized:

    // astro.config.mjs
export default defineConfig({
  image: {
    domains: ['astro.build'],
  },
});

    The following configuration will only allow remote images from HTTPS hosts:

    // astro.config.mjs
export default defineConfig({
  image: {
    remotePatterns: [{ protocol: 'https' }],
  },
});

  • #​8109 da6e3da1c Thanks @​martrapp! - fix: reinsert attribute to specify direction of ViewTransition (forward / back)

v2.10.9

Compare Source

Patch Changes

v2.10.8

Compare Source

Patch Changes

v2.10.7

Compare Source

Patch Changes

v2.10.6

Compare Source

Patch Changes

v2.10.5

Compare Source

Patch Changes
  • #​8011 5b1e39ef6 Thanks @​bluwy! - Move hoisted script analysis optimization behind the experimental.optimizeHoistedScript option

v2.10.4

Compare Source

Patch Changes

v2.10.3

Compare Source

Patch Changes

v2.10.2

Compare Source

Patch Changes

v2.10.1

Compare Source

Patch Changes

v2.10.0

Compare Source

Minor Changes

  • #​7861 41afb8405 Thanks @​matthewp! - Persistent DOM and Islands in Experimental View Transitions

    With viewTransitions: true enabled in your Astro config's experimental section, pages using the <ViewTransition /> routing component can now access a new transition:persist directive.

    With this directive, you can keep the state of DOM elements and islands on the old page when transitioning to the new page.

    For example, to keep a video playing across page navigation, add transition:persist to the element:

    <video controls="" autoplay="" transition:persist>
  <source
    src="https://ia804502.us.archive.org/33/items/GoldenGa1939_3/GoldenGa1939_3_512kb.mp4"
    type="video/mp4"
  />
</video>

    This <video> element, with its current state, will be moved over to the next page (if the video also exists on that page).

    Likewise, this feature works with any client-side framework component island. In this example, a counter's state is preserved and moved to the new page:

    <Counter count={5} client:load transition:persist />

    See our View Transitions Guide to learn more on usage.

Patch Changes

v2.9.7

Compare Source

Patch Changes

v2.9.6

Compare Source

Patch Changes

v2.9.5

Compare Source

Patch Changes

v2.9.4

Compare Source

Patch Changes

v2.9.3

Compare Source

Patch Changes

  • #​7782 0f677c009 Thanks @​bluwy! - Refactor Astro rendering to write results directly. This improves the rendering performance for all Astro files.

  • #​7786 188eeddd4 Thanks @​matthewp! - Execute scripts when navigating to a new page.

    When navigating to an new page with client-side navigation, scripts are executed (and re-executed) so that any new scripts on the incoming page are run and the DOM can be updated.

    However, type=module scripts never re-execute in Astro, and will not do so in client-side routing. To support cases where you want to modify the DOM, a new astro:load event listener been added:

    document.addEventListener('astro:load', () => {
  updateTheDOMSomehow();
});

v2.9.2

Compare Source

Patch Changes

v2.9.1

Compare Source

Patch Changes

v2.9.0

Compare Source

Minor Changes

  • #​7686 ec745d689 Thanks @​matthewp! - Redirects configuration

    This change moves the redirects configuration out of experimental. If you were previously using experimental redirects, remove the following experimental flag:

    experimental: {
  redirects: true,
}

    If you have been waiting for stabilization before using redirects, now you can do so. Check out the docs on redirects to learn how to use this built-in feature.

  • #​7707 3a6e42e19 Thanks @​ottomated! - Improved hoisted script bundling

    Astro's static analysis to determine which <script> tags to bundle together just got a little smarter!

    Astro create bundles that optimize script usage between pages and place them in the head of the document so that they are downloaded as early as possible. One limitation to Astro's existing approach has been that you could not dynamically use hoisted scripts. Each page received the same, all-inclusive bundle whether or not every script was needed on that page.

    Now, Astro has improved the static analysis to take into account the actual imports used.

    For example, Astro would previously bundle the <script>s from both the <Tab> and <Accordian> component for the following library that re-exports multiple components:

    @​matthewp/my-astro-lib

    export { default as Tabs } from './Tabs.astro';
export { default as Accordion } from './Accordion.astro';

    Now, when an Astro page only uses a single component, Astro will send only the necessary script to the page. A page that only imports the <Accordian> component will not receive any <Tab> component's scripts:

    ---
import { Accordion } from '@&#8203;matthewp/my-astro-lib';
---

    You should now see more efficient performance with Astro now supporting this common library re-export pattern.

  • #​7511 6a12fcecb Thanks @​matthewp! - Built-in View Transitions Support (experimental)

    Astro now supports view transitions through the new <ViewTransitions /> component and the transition:animate (and associated) directives. View transitions are a great fit for content-oriented sites, and we see it as the best path to get the benefits of client-side routing (smoother transitions) without sacrificing the more simple mental model of MPAs.

    Enable support for view transitions in Astro 2.9 by adding the experimental flag to your config:

    import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
    viewTransitions: true,
  },
});

    This enables you to use the new APIs added.

This is a component which acts as the _router_ for transitions between pages. Add it to the `<head>` section of each individual page where transitions should occur _in the client_ as you navigate away to another page, instead of causing a full page browser refresh. To enable support throughout your entire app, add the component in some common layout or component that targets the `<head>` of every page.

**CommonHead.astro**

```astro
---
import { ViewTransitions } from 'astro:transitions';
---

<meta charset="utf-8" />
<title>{Astro.props.title}</title>
<ViewTransitions />
```

With only this change, your app will now route completely in-client. You can then add transitions to individual elements using the `transition:animate` directive.
Animations
Add `transition:animate` to any element to use Astro's built-in animations.

```astro
<header transition:animate="slide"></header>
```

In the above, Astro's `slide` animation will cause the `<header>` element to slide out to the left, and then slide in from the right when you navigate away from the page.

You can also customize these animations using any CSS animation properties, for example, by specifying a duration:

```astro
---
import { slide } from 'astro:transition';
---

<header transition:animate={slide({ duration: 200 })}></header>
```
Continue learning
Check out the [client-side routing docs](https://docs.astro.build/en/guides/client-side-routing/) to learn more.
Patch Changes

v2.8.5

Compare Source

Patch Changes

v2.8.4

Compare Source

Patch Changes

[v2.8.3](htt

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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
Copy link
Copy Markdown
Contributor Author

renovate bot commented Mar 25, 2026

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants