chore: update astro monorepo (major) #1638

renovate · 2025-05-23T02:03:42Z

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/mdx (source)	`^3.1.9` -> `^4.3.13`
@astrojs/react (source)	`^3.6.3` -> `^4.4.2`
astro (source)	`^4.16.18` -> `^5.16.5`

Release Notes

withastro/astro (@astrojs/mdx)

Patch Changes

#14813 e1dd377 Thanks @ematipico! - Removes picocolors as dependency in favor of the fork piccolore.

`v4.3.11`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.9

`v4.3.10`

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

Patch Changes

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

`v4.3.8`

Patch Changes

#14591 3e887ec Thanks @matthewp! - Adds TypeScript support for the components prop on MDX Content component when using await render(). Developers now get proper IntelliSense and type checking when passing custom components to override default MDX element rendering.
#14598 7b45c65 Thanks @delucis! - Reduces terminal text styling dependency size by switching from kleur to picocolors

`v4.3.7`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.8

`v4.3.6`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.7

`v4.3.5`

Compare Source

Patch Changes

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

`v4.3.4`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.6

`v4.3.3`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.5

`v4.3.2`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.4

`v4.3.1`

Compare Source

Patch Changes

Updated dependencies [6bd5f75]:
- @astrojs/markdown-remark@6.3.3

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

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.2

`v4.2.6`

Compare Source

Patch Changes

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

`v4.2.5`

Compare Source

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

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

Patch Changes

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

`v4.2.1`

Patch Changes

#13448 91c9503 Thanks @ematipico! - Upgrade to shiki v3
Updated dependencies [91c9503]:
- @astrojs/markdown-remark@6.3.1

`v4.2.0`

Compare Source

Minor Changes

#13352 cb886dc Thanks @delucis! - Adds support for a new experimental.headingIdCompat flag

By default, Astro removes a trailing - from the end of IDs it generates for headings ending with
special characters. This differs from the behavior of common Markdown processors.

You can now disable this behavior with a new configuration flag:

// astro.config.mjs
import { defineConfig } from 'astro/config';

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

This can be useful when heading IDs and anchor links need to behave consistently across your site
and other platforms such as GitHub and npm.

If you are using the rehypeHeadingIds plugin directly, you can also pass this new option:

// astro.config.mjs
import { defineConfig } from 'astro/config';
import { rehypeHeadingIds } from '@&#8203;astrojs/markdown-remark';
import { otherPluginThatReliesOnHeadingIDs } from 'some/plugin/source';

export default defineConfig({
  markdown: {
    rehypePlugins: [
      [rehypeHeadingIds, { experimentalHeadingIdCompat: true }],
      otherPluginThatReliesOnHeadingIDs,
    ],
  },
});

Patch Changes

Updated dependencies [cb886dc, a3327ff]:
- @astrojs/markdown-remark@6.3.0

`v4.1.1`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.2.1

`v4.1.0`

Compare Source

Minor Changes

#13254 1e11f5e Thanks @p0lyw0lf! - Adds the ability to process and optimize remote images in Markdown syntax in MDX files.

Previously, Astro only allowed local images to be optimized when included using ![]() syntax. Astro's image service could only display remote images without any processing.

Now, Astro's image service can also optimize remote images written in standard Markdown syntax. This allows you to enjoy the benefits of Astro's image processing when your images are stored externally, for example in a CMS or digital asset manager.

No additional configuration is required to use this feature! Any existing remote images written in Markdown will now automatically be optimized. To opt-out of this processing, write your images in Markdown using the JSX <img/> tag instead. Note that images located in your public/ folder are still never processed.

Patch Changes

Updated dependencies [1e11f5e]:
- @astrojs/markdown-remark@6.2.0

`v4.0.8`

Compare Source

Patch Changes

Updated dependencies [db252e0]:
- @astrojs/markdown-remark@6.1.0

`v4.0.7`

Compare Source

Patch Changes

#13011 cf30880 Thanks @ascorbic! - Upgrades Vite

`v4.0.6`

Compare Source

Patch Changes

Updated dependencies [3d89e62]:
- @astrojs/markdown-remark@6.0.2

`v4.0.5`

Compare Source

Patch Changes

#12959 3a267f3 Thanks @bluwy! - Reverts 9a3b48c which caused a regression for rendering inline MDX components and MDX files from content collections

`v4.0.4`

Compare Source

Patch Changes

#12921 aeb7e1a Thanks @ascorbic! - Fixes a bug that caused Image component to be imported on MDX pages that did not include images
#12913 9a3b48c Thanks @bluwy! - Makes internal check() function a no-op to allow faster component renders and prevent React 19 component warnings

`v4.0.3`

Compare Source

Patch Changes

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

`v4.0.2`

Compare Source

Patch Changes

Updated dependencies [f13417b, 87231b1, a71e9b9]:
- @astrojs/markdown-remark@6.0.1

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

withastro/astro (astro)

`v5.16.5`

Compare Source

Patch Changes

#14985 c016f10 Thanks @florian-lefebvre! - Fixes a case where JSDoc annotations wouldn't show for fonts related APIs in the Astro config
#14973 ed7cc2f Thanks @amankumarpandeyin! - Fixes performance regression and OOM errors when building medium-sized blogs with many content entries. Replaced O(n²) object spread pattern with direct mutation in generateLookupMap.
#14958 70eb542 Thanks @ascorbic! - Gives a helpful error message if a user sets output: "hybrid" in their Astro config.

The option was removed in Astro 5, but lots of content online still references it, and LLMs often suggest it. It's not always clear that the replacement is output: "static", rather than output: "server". This change adds a helpful error message to guide humans and robots.
#14901 ef53716 Thanks @Darknab! - Updates the glob() loader to log a warning when duplicated IDs are detected
Updated dependencies [d8305f8]:
- @astrojs/markdown-remark@6.3.10

`v5.16.4`

Compare Source

Patch Changes

#14940 2cf79c2 Thanks @ematipico! - Fixes a bug where Astro didn't properly combine CSP resources from the csp configuration with those added using the runtime API (Astro.csp.insertDirective()) to form grammatically correct CSP headers

Now Astro correctly deduplicate CSP resources. For example, if you have a global resource in the configuration file, and then you add a
a new one using the runtime APIs.

`v5.16.3`

Compare Source

Patch Changes

#14889 4bceeb0 Thanks @florian-lefebvre! - Fixes actions types when using specific TypeScript configurations
#14929 e0f277d Thanks @matthewp! - Fixes authentication bypass via double URL encoding in middleware

Prevents attackers from bypassing path-based authentication checks using multi-level URL encoding (e.g., /%2561dmin instead of /%61dmin). Pathnames are now validated after decoding to ensure no additional encoding remains.

`v5.16.2`

Compare Source

Patch Changes

#14876 b43dc7f Thanks @florian-lefebvre! - Fixes a vite warning log during builds when using npm
#14884 10273e0 Thanks @florian-lefebvre! - Fixes a case where setting the status of a page to 404 in ssr would show an empty page (or 404.astro page if provided) instead of using the current page

`v5.16.1`

Compare Source

Patch Changes

#14769 b43ee71 Thanks @adriandlam! - Fixes an unhandled rejection issue when using Astro with Vercel Workflow DevKit
#14761 345eb22 Thanks @ooga! - Updates button attributes types to allow command and commandfor
#14866 65e214b Thanks @GameRoMan! - Fixes Astro.glob to be correctly marked as deprecated
#14894 1ad9a5b Thanks @delucis! - Fixes support for Astro component rendering in Vitest test suites using a “client” environment such as happy-dom or jsdom
#14782 abed929 Thanks @florian-lefebvre! - Improves syncing

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

Rev

Configuration

📅 Schedule: Branch creation - "after 8am and before 5pm every weekday" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, 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.

netlify · 2025-05-23T02:03:46Z

❌ Deploy Preview for smarthr-design-system failed. Why did it fail? →

Name	Link
🔨 Latest commit	`65c29c0`
🔍 Latest deploy log	https://app.netlify.com/projects/smarthr-design-system/deploys/6944ad25c1a9c1000841df7d

renovate · 2025-06-19T04:48:14Z

⚠️ 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: yarn.lock

error This project's package.json defines "packageManager": "yarn@[email protected]". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.

renovate bot added the renovate label May 23, 2025

renovate bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from f64a7fd to 598133e Compare June 5, 2025 00:41

renovate bot force-pushed the renovate/major-astro-monorepo branch 5 times, most recently from 633e1ee to f83dab3 Compare June 16, 2025 03:43

renovate bot force-pushed the renovate/major-astro-monorepo branch from f83dab3 to e9735b4 Compare June 18, 2025 00:29

renovate bot changed the title ~~chore: update astro monorepo (major)~~ Update astro monorepo (major) Jun 19, 2025

renovate bot force-pushed the renovate/major-astro-monorepo branch from e9735b4 to efef562 Compare June 19, 2025 04:48

renovate bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from 14f097f to 4a79056 Compare June 24, 2025 07:09

renovate bot changed the title ~~Update astro monorepo (major)~~ chore: update astro monorepo (major) Jun 26, 2025

renovate bot changed the title ~~chore: update astro monorepo (major)~~ Update astro monorepo (major) Jun 30, 2025

renovate bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from f7b08ed to 1d1e897 Compare July 4, 2025 01:28

renovate bot changed the title ~~Update astro monorepo (major)~~ chore: update astro monorepo (major) Jul 4, 2025

renovate bot force-pushed the renovate/major-astro-monorepo branch from 1d1e897 to 5ec3fdd Compare July 11, 2025 03:31

renovate bot changed the title ~~chore: update astro monorepo (major)~~ Update astro monorepo (major) Jul 11, 2025

renovate bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from ea3bf53 to 5f80aa4 Compare July 22, 2025 01:03

renovate bot force-pushed the renovate/major-astro-monorepo branch from 5f80aa4 to c2e6d58 Compare July 23, 2025 00:24

renovate bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from d6c974d to 5717d57 Compare July 29, 2025 23:29

renovate bot changed the title ~~Update astro monorepo (major)~~ chore: update astro monorepo (major) Jul 30, 2025

renovate bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 93758d7 to 19d35b0 Compare August 5, 2025 04:03

renovate bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from 8891a01 to 1a6b689 Compare August 15, 2025 02:06

renovate bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 207a634 to 984f761 Compare August 22, 2025 01:50

renovate bot force-pushed the renovate/major-astro-monorepo branch from 984f761 to b49af2e Compare August 25, 2025 04:14

renovate bot changed the title ~~chore: update astro monorepo (major)~~ Update astro monorepo (major) Aug 25, 2025

chore: update astro monorepo

65c29c0

renovate bot force-pushed the renovate/major-astro-monorepo branch from b49af2e to 65c29c0 Compare December 19, 2025 01:40

renovate bot changed the title ~~Update astro monorepo (major)~~ chore: update astro monorepo (major) Dec 19, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore: update astro monorepo (major) #1638

chore: update astro monorepo (major) #1638

Uh oh!

renovate bot commented May 23, 2025 •

edited

Loading

Uh oh!

netlify bot commented May 23, 2025 •

edited

Loading

Uh oh!

renovate bot commented Jun 19, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

chore: update astro monorepo (major) #1638

Are you sure you want to change the base?

chore: update astro monorepo (major) #1638

Uh oh!

Conversation

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

Uh oh!

Release Notes

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

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

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

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

Uh oh!

netlify bot commented May 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

❌ Deploy Preview for smarthr-design-system failed. Why did it fail? →

Uh oh!

renovate bot commented May 23, 2025 •

edited

Loading

netlify bot commented May 23, 2025 •

edited

Loading