fix(deps): update astro monorepo (major) #26

renovate · 2024-05-01T14:40:09Z

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/react (source)	`^2.0.0` -> `^4.0.0`
astro (source)	`^2.0.0` -> `^5.0.0`

Release Notes

withastro/astro (@astrojs/react)

`v4.4.2`

Compare Source

Patch Changes

#14715 3d55c5d Thanks @ascorbic! - Adds support for client hydration in getContainerRenderer()

The getContainerRenderer() function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint.

See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

`v4.4.1`

Compare Source

Patch Changes

#14621 e3175d9 Thanks @GameRoMan! - Updates vite version to fix CVE

`v4.4.0`

Compare Source

Minor Changes

#14386 f75f446 Thanks @yanthomasdev! - Stabilizes the formerly experimental getActionState() and withState() functions introduced in @astrojs/react v3.4.0 used to integrate Astro Actions with React 19's useActionState() hook.

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

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

export function Like({ postId }: { postId: string }) {
  const [state, action, pending] = useActionState(
    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 getActionState() with the API context, and optionally apply a type to the result:

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

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

If you were previously using this experimental feature, you will need to update your code to use the new stable exports:

// src/components/Form.jsx
import { actions } from 'astro:actions';
-import { experimental_withState } from '@&#8203;astrojs/react/actions';
+import { withState } from '@&#8203;astrojs/react/actions';
import { useActionState } from "react";

// src/actions/index.ts
import { defineAction, type SafeResult } from 'astro:actions';
import { z } from 'astro:schema';
-import { experimental_getActionState } from '@&#8203;astrojs/react/actions';
+import { getActionState } from '@&#8203;astrojs/react/actions';

`v4.3.1`

Compare Source

Patch Changes

#14326 c24a8f4 Thanks @jsparkdev! - Updates vite version to fix CVE

`v4.3.0`

Compare Source

Minor Changes

#13809 3c3b492 Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8

Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

`v4.2.7`

Compare Source

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

`v4.2.6`

Compare Source

Patch Changes

#13720 e1cd1ae Thanks @florian-lefebvre! - Fixes SSR renderer type

`v4.2.5`

Compare Source

Patch Changes

#13663 a19a185 Thanks @florian-lefebvre! - Improves type-safety of renderers

`v4.2.4`

Compare Source

Patch Changes

#13596 3752519 Thanks @jsparkdev! - update vite to latest version to fix CVE
#13547 360cb91 Thanks @jsparkdev! - Updates vite to the latest version

`v4.2.3`

Compare Source

Patch Changes

#13526 ff9d69e Thanks @jsparkdev! - update vite to the latest version

`v4.2.2`

Compare Source

Patch Changes

#13505 a98ae5b Thanks @ematipico! - Updates the dependency vite to the latest.

`v4.2.1`

Compare Source

Patch Changes

#13323 80926fa Thanks @ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

`v4.2.0`

Compare Source

Minor Changes

#13036 3c90d8f Thanks @artmsilva! - Adds experimental support for disabling streaming

This is useful to support libraries that are not compatible with streaming such as some CSS-in-JS libraries. To disable streaming for all React components in your project, set experimentalDisableStreaming: true as a configuration option for @astrojs/react:
```
// astro.config.mjs
import { defineConfig } from 'astro/config';
import react from '@&#8203;astrojs/react';

export default defineConfig({
  integrations: [
    react({
+      experimentalDisableStreaming: true,
    }),
  ],
});
```

`v4.1.6`

Compare Source

Patch Changes

#12996 80c6801 Thanks @bluwy! - Removes hardcoded ssr.external: ['react-dom/server', 'react-dom/client'] config that causes issues with adapters that bundle all dependencies (e.g. Cloudflare). These externals should already be inferred by default by Vite when deploying to a server environment.
#13011 cf30880 Thanks @ascorbic! - Upgrades Vite

`v4.1.5`

Compare Source

Patch Changes

#12887 ea603ae Thanks @louisescher! - Adds a warning message when multiple JSX-based UI frameworks are being used without either the include or exclude property being set on the integration.

`v4.1.4`

Compare Source

Patch Changes

#12923 c7642fb Thanks @bluwy! - Removes react-specific entrypoints in optimizeDeps.include and rely on @vitejs/plugin-react to add

`v4.1.3`

Compare Source

Patch Changes

#12948 51ab7b5 Thanks @bluwy! - Supports checking for React 19 components

`v4.1.2`

Compare Source

Patch Changes

#12799 739dbfb Thanks @ascorbic! - Upgrades Vite to pin esbuild

`v4.1.1`

Compare Source

Patch Changes

#12755 391df0e Thanks @matthewp! - Preoptimize React compiler runtime

`v4.1.0`

Compare Source

Minor Changes

#12678 97c9265 Thanks @bskimball! - Add React 19 stable to peer dependencies

`v4.0.0`

Compare Source

Major Changes

#12524 9f44019 Thanks @bluwy! - Updates Vite dependency to v6 to match Astro v5

Minor Changes

#12539 827093e Thanks @bluwy! - Drops node 21 support
#12510 14feaf3 Thanks @bholmesdev! - Changes the generated URL query param from _astroAction to _action when submitting a form using Actions. This avoids leaking the framework name into the URL bar, which may be considered a security issue.

`v3.6.3`

Compare Source

Patch Changes

#12481 8a46e80 Thanks @marbrex! - Resolve vite peer dependency problem for strict package managers like Yarn in PnP mode.

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

withastro/astro (astro)

`v5.16.0`

Compare Source

Minor Changes

#13880 1a2ed01 Thanks @azat-io! - Adds experimental SVGO optimization support for SVG assets

Astro now supports automatic SVG optimization using SVGO during build time. This experimental feature helps reduce SVG file sizes while maintaining visual quality, improving your site's performance.

To enable SVG optimization with default settings, add the following to your astro.config.mjs:
```
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
    svgo: true,
  },
});
```
To customize optimization, pass a SVGO configuration object:
```
export default defineConfig({
  experimental: {
    svgo: {
      plugins: [
        'preset-default',
        {
          name: 'removeViewBox',
          active: false,
        },
      ],
    },
  },
});
```
For more information on enabling and using this feature in your project, see the experimental SVG optimization docs.
#14810 2e845fe Thanks @ascorbic! - Adds a hint for code agents to use the --yes flag to skip prompts when running astro add

#14698 f42ff9b Thanks @mauriciabad! - Adds the ActionInputSchema utility type to automatically infer the TypeScript type of an action's input based on its Zod schema

For example, this type can be used to retrieve the input type of a form action:

import { type ActionInputSchema, defineAction } from 'astro:actions';
import { z } from 'astro/zod';

const action = defineAction({
  accept: 'form',
  input: z.object({ name: z.string() }),
  handler: ({ name }) => ({ message: `Welcome, ${name}!` }),
});

type Schema = ActionInputSchema<typeof action>;
// typeof z.object({ name: z.string() })

type Input = z.input<Schema>;
// { name: string }

#14574 4356485 Thanks @jacobdalamb! - Adds new CLI shortcuts available when running astro preview:
- o + enter: open the site in your browser
- q + enter: quit the preview
- h + enter: print all available shortcuts

Patch Changes

#14813 e1dd377 Thanks @ematipico! - Removes picocolors as dependency in favor of the fork piccolore.
#14609 d774306 Thanks @florian-lefebvre! - Improves astro info
#14796 c29a785 Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Updates the default subsets to ["latin"]

Subsets have been a common source of confusion: they caused a lot of files to be downloaded by default. You now have to manually pick extra subsets.

Review your Astro config and update subsets if you need, for example if you need greek characters:
```
import { defineConfig, fontProviders } from "astro/config"

export default defineConfig({
    experimental: {
        fonts: [{
            name: "Roboto",
            cssVariable: "--font-roboto",
            provider: fontProviders.google(),
+            subsets: ["latin", "greek"]
        }]
    }
})
```

`v5.15.9`

Compare Source

Patch Changes

#14786 758a891 Thanks @mef! - Add handling of invalid encrypted props and slots in server islands.
#14783 504958f Thanks @florian-lefebvre! - Improves the experimental Fonts API build log to show the number of downloaded files. This can help spotting excessive downloading because of misconfiguration
#14791 9e9c528 Thanks @Princesseuh! - Changes the remote protocol checks for images to require explicit authorization in order to use data URIs.

In order to allow data URIs for remote images, you will need to update your astro.config.mjs file to include the following configuration:
```
// astro.config.mjs
import { defineConfig } from 'astro/config';

export default defineConfig({
  images: {
    remotePatterns: [
      {
        protocol: 'data',
      },
    ],
  },
});
```
#14787 0f75f6b Thanks @matthewp! - Fixes wildcard hostname pattern matching to correctly reject hostnames without dots

Previously, hostnames like localhost or other single-part names would incorrectly match patterns like *.example.com. The wildcard matching logic has been corrected to ensure that only valid subdomains matching the pattern are accepted.
#14776 3537876 Thanks @ktym4a! - Fixes the behavior of passthroughImageService so it does not generate webp.
Updated dependencies [9e9c528, 0f75f6b]:
- @astrojs/internal-helpers@0.7.5
- @astrojs/markdown-remark@6.3.9

`v5.15.8`

Compare Source

Patch Changes

#14772 00c579a Thanks @matthewp! - Improves the security of Server Islands slots by encrypting them before transmission to the browser, matching the security model used for props. This improves the integrity of slot content and prevents injection attacks, even when component templates don't explicitly support slots.

Slots continue to work as expected for normal usage—this change has no breaking changes for legitimate requests.
#14771 6f80081 Thanks @matthewp! - Fix middleware pathname matching by normalizing URL-encoded paths

Middleware now receives normalized pathname values, ensuring that encoded paths like /%61dmin are properly decoded to /admin before middleware checks. This prevents potential security issues where middleware checks might be bypassed through URL encoding.

`v5.15.7`

Compare Source

Patch Changes

#14765 03fb47c Thanks @florian-lefebvre! - Fixes a case where process.env wouldn't be properly populated during the build
#14690 ae7197d Thanks @fredriknorlin! - Fixes a bug where Astro's i18n fallback system with fallbackType: 'rewrite' would not generate fallback files for pages whose filename started with a locale key.

`v5.15.6`

Compare Source

Patch Changes

#14751 18c55e1 Thanks @delucis! - Fixes hydration of client components when running the dev server and using a barrel file that re-exports both Astro and UI framework components.
#14750 35122c2 Thanks @florian-lefebvre! - Updates the experimental Fonts API to log a warning if families with a conflicting cssVariable are provided
#14737 74c8852 Thanks @Arecsu! - Fixes an error when using transition:persist with components that use declarative Shadow DOM. Astro now avoids re-attaching a shadow root if one already exists, preventing "Unable to re-attach to existing ShadowDOM" navigation errors.
#14750 35122c2 Thanks @florian-lefebvre! - Updates the experimental Fonts API to allow for more granular configuration of remote font families

A font family is defined by a combination of properties such as weights and styles (e.g. weights: [500, 600] and styles: ["normal", "bold"]), but you may want to download only certain combinations of these.

For greater control over which font files are downloaded, you can specify the same font (ie. with the same cssVariable, name, and provider properties) multiple times with different combinations. Astro will merge the results and download only the required files. For example, it is possible to download normal 500 and 600 while downloading only italic 500:
```
// astro.config.mjs
import { defineConfig, fontProviders } from 'astro/config';

export default defineConfig({
  experimental: {
    fonts: [
      {
        name: 'Roboto',
        cssVariable: '--roboto',
        provider: fontProviders.google(),
        weights: [500, 600],
        styles: ['normal'],
      },
      {
        name: 'Roboto',
        cssVariable: '--roboto',
        provider: fontProviders.google(),
        weights: [500],
        styles: ['italic'],
      },
    ],
  },
});
```

`v5.15.5`

Compare Source

Patch Changes

#14712 91780cf Thanks @florian-lefebvre! - Fixes a case where build's process.env would be inlined in the server output
#14713 666d5a7 Thanks @florian-lefebvre! - Improves fallbacks generation when using the experimental Fonts API
#14743 dafbb1b Thanks @matthewp! - Improves X-Forwarded header validation to prevent cache poisoning and header injection attacks. Now properly validates X-Forwarded-Proto, X-Forwarded-Host, and X-Forwarded-Port headers against configured allowedDomains patterns, rejecting malformed or suspicious values. This is especi

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

shinevue approved these changes Nov 29, 2024

View reviewed changes

renovate bot force-pushed the renovate/major-astro-monorepo branch 5 times, most recently from 9678eb6 to 0ce78a2 Compare December 3, 2024 11:39

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

renovate bot closed this Dec 8, 2024

renovate bot deleted the renovate/major-astro-monorepo branch December 8, 2024 18:52

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

renovate bot reopened this Dec 9, 2024

renovate bot force-pushed the renovate/major-astro-monorepo branch from 61618dc to 0ce78a2 Compare December 9, 2024 02:16

renovate bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from 6ff34dc to 3ae0b47 Compare July 28, 2025 14:33

renovate bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from f9e7c67 to 06326a5 Compare August 1, 2025 16:04

renovate bot force-pushed the renovate/major-astro-monorepo branch 5 times, most recently from c8f84e2 to e974020 Compare August 15, 2025 14:23

renovate bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from b4b1d1c to b1e198c Compare August 22, 2025 19:26

renovate bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 70df7cc to c0d1256 Compare August 31, 2025 09:03

renovate bot force-pushed the renovate/major-astro-monorepo branch from c0d1256 to 03bde31 Compare September 8, 2025 22:01

renovate bot force-pushed the renovate/major-astro-monorepo branch from 03bde31 to fd17750 Compare September 9, 2025 18:06

renovate bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 82d1dc4 to ec092e8 Compare September 22, 2025 10:32

renovate bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from df0553b to 10cd887 Compare September 26, 2025 13:38

renovate bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from fb78d20 to 5a76e73 Compare October 14, 2025 13:57

renovate bot force-pushed the renovate/major-astro-monorepo branch 6 times, most recently from c1366c9 to 50712fa Compare October 23, 2025 16:48

renovate bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from c90cb4f to 322baae Compare October 30, 2025 16:50

renovate bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 4584232 to d633590 Compare November 11, 2025 01:37

renovate bot force-pushed the renovate/major-astro-monorepo branch 5 times, most recently from e22b8a1 to 7e5d134 Compare November 18, 2025 22:53

fix(deps): update astro monorepo

a532f55

renovate bot force-pushed the renovate/major-astro-monorepo branch from 7e5d134 to a532f55 Compare November 20, 2025 14:01

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update astro monorepo (major) #26

fix(deps): update astro monorepo (major) #26

Uh oh!

renovate bot commented May 1, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

fix(deps): update astro monorepo (major) #26

Are you sure you want to change the base?

fix(deps): update astro monorepo (major) #26

Uh oh!

Conversation

renovate bot commented May 1, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Minor 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

Patch Changes

Patch Changes

Minor Changes

Major Changes

Minor Changes

Patch Changes

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

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

renovate bot commented May 1, 2024 •

edited

Loading