Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update astro to 5.3.0 #600

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 6, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
astro (source) 4.16.18 -> 5.3.0 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

withastro/astro (astro)

v5.3.0

Compare Source

Minor Changes
  • #​13210 344e9bc Thanks @​VitaliyR! - Handle HEAD requests to an endpoint when a handler is not defined.

    If an endpoint defines a handler for GET, but does not define a handler for HEAD, Astro will call the GET handler and return the headers and status but an empty body.

  • #​13195 3b66955 Thanks @​MatthewLymer! - Improves SSR performance for synchronous components by avoiding the use of Promises. With this change, SSR rendering of on-demand pages can be up to 4x faster.

  • #​13145 8d4e566 Thanks @​ascorbic! - Adds support for adapters auto-configuring experimental session storage drivers.

    Adapters can now configure a default session storage driver when the experimental.session flag is enabled. If a hosting platform has a storage primitive that can be used for session storage, the adapter can automatically configure the session storage using that driver. This allows Astro to provide a more seamless experience for users who want to use sessions without needing to manually configure the session storage.

Patch Changes
  • #​13145 8d4e566 Thanks @​ascorbic! - ⚠️ BREAKING CHANGE FOR EXPERIMENTAL SESSIONS ONLY ⚠️

    Changes the experimental.session option to a boolean flag and moves session config to a top-level value. This change is to allow the new automatic session driver support. You now need to separately enable the experimental.session flag, and then configure the session driver using the top-level session key if providing manual configuration.

    defineConfig({
      // ...
      experimental: {
    -    session: {
    -      driver: 'upstash',
    -    },
    +    session: true,
      },
    +  session: {
    +    driver: 'upstash',
    +  },
    });

    You no longer need to configure a session driver if you are using an adapter that supports automatic session driver configuration and wish to use its default settings.

    defineConfig({
      adapter: node({
        mode: "standalone",
      }),
      experimental: {
    -    session: {
    -      driver: 'fs',
    -      cookie: 'astro-cookie',
    -    },
    +    session: true,
      },
    +  session: {
    +    cookie: 'astro-cookie',
    +  },
    });

    However, you can still manually configure additional driver options or choose a non-default driver to use with your adapter with the new top-level session config option. For more information, see the experimental session docs.

  • #​13101 2ed67d5 Thanks @​corneliusroemer! - Fixes a bug where HEAD and OPTIONS requests for non-prerendered pages were incorrectly rejected with 403 FORBIDDEN

v5.2.6

Compare Source

Patch Changes

v5.2.5

Compare Source

Patch Changes
  • #​13133 e76aa83 Thanks @​ematipico! - Fixes a bug where Astro was failing to build an external redirect when the middleware was triggered

  • #​13119 ac43580 Thanks @​Hacksore! - Adds extra guidance in the terminal when using the astro add tailwind CLI command

    Now, users are given a friendly reminder to import the stylesheet containing their Tailwind classes into any pages where they want to use Tailwind. Commonly, this is a shared layout component so that Tailwind styling can be used on multiple pages.

v5.2.4

Compare Source

Patch Changes

v5.2.3

Compare Source

Patch Changes
  • #​13113 3a26e45 Thanks @​unprintable123! - Fixes the bug that rewrite will pass encoded url to the dynamic routing and cause params mismatch.

  • #​13111 23978dd Thanks @​ascorbic! - Fixes a bug that caused injected endpoint routes to return not found when trailingSlash was set to always

  • #​13112 0fa5c82 Thanks @​ematipico! - Fixes a bug where the i18n middleware was blocking a server island request when the prefixDefaultLocale option is set to true

v5.2.2

Compare Source

Patch Changes

v5.2.1

Compare Source

Patch Changes
  • #​13095 740eb60 Thanks @​ascorbic! - Fixes a bug that caused some dev server asset requests to return 404 when trailingSlash was set to "always"

v5.2.0

Compare Source

Minor Changes
  • #​12994 5361755 Thanks @​ascorbic! - Redirects trailing slashes for on-demand pages

    When the trailingSlash option is set to always or never, on-demand rendered pages will now redirect to the correct URL when the trailing slash doesn't match the configuration option. This was previously the case for static pages, but now works for on-demand pages as well.

    Now, it doesn't matter whether your visitor navigates to /about/, /about, or even /about///. In production, they'll always end up on the correct page. For GET requests, the redirect will be a 301 (permanent) redirect, and for all other request methods, it will be a 308 (permanent, and preserve the request method) redirect.

    In development, you'll see a helpful 404 page to alert you of a trailing slash mismatch so you can troubleshoot routes.

  • #​12979 e621712 Thanks @​ematipico! - Adds support for redirecting to external sites with the redirects configuration option.

    Now, you can redirect routes either internally to another path or externally by providing a URL beginning with http or https:

    // astro.config.mjs
    import { defineConfig } from 'astro/config';
    
    export default defineConfig({
      redirects: {
        '/blog': 'https://example.com/blog',
        '/news': {
          status: 302,
          destination: 'https://example.com/news',
        },
      },
    });
  • #​13084 0f3be31 Thanks @​ematipico! - Adds a new experimental virtual module astro:config that exposes a type-safe subset of your astro.config.mjs configuration

    The virtual module exposes two sub-paths for controlled access to your configuration:

    • astro:config/client: exposes config information that is safe to expose to the client.
    • astro:config/server: exposes additional information that is safe to expose to the server, such as file/dir paths.

    To enable this new virtual module, add the experimental.serializeManifest feature flag to your Astro config:

    // astro.config.mjs
    import { defineConfig } from 'astro/config';
    export default defineConfig({
      experimental: {
        serializeManifest: true,
      },
    });

    Then, you can access the module in any file inside your project to import and use values from your Astro config:

    // src/utils.js
    import { trailingSlash } from 'astro:config/client';
    
    function addForwardSlash(path) {
      if (trailingSlash === 'always') {
        return path.endsWith('/') ? path : path + '/';
      } else {
        return path;
      }
    }

    For a complete overview, and to give feedback on this experimental API, see the Serialized Manifest RFC.

Patch Changes

v5.1.10

Compare Source

Patch Changes

v5.1.9

Compare Source

Patch Changes

v5.1.8

Compare Source

Patch Changes

v5.1.7

Compare Source

Patch Changes

v5.1.6

Compare Source

Patch Changes

v5.1.5

Compare Source

Patch Changes
  • #​12934 673a518 Thanks @​ematipico! - Fixes a regression where the Astro Container didn't work during the build, using pnpm

  • #​12955 db447f2 Thanks @​martrapp! - Lets TypeScript know about the "blocking" and "disabled" attributes of the <link> element.

  • #​12922 faf74af Thanks @​adamchal! - Improves performance of static asset generation by fixing a bug that caused image transforms to be performed serially. This fix ensures that processing uses all CPUs when running in a multi-core environment.

  • #​12947 3c2292f Thanks @​ascorbic! - Fixes a bug that caused empty content collections when running dev with NODE_ENV set

v5.1.4

Compare Source

Patch Changes
  • #​12927 ad2a752 Thanks @​ematipico! - Fixes a bug where Astro attempted to decode a request URL multiple times, resulting in an unexpected behaviour when decoding the character %

  • #​12912 0c0c66b Thanks @​florian-lefebvre! - Improves the config error for invalid combinations of context and access properties under env.schema

  • #​12935 3d47e6b Thanks @​AirBorne04! - Fixes an issue where Astro.locals coming from an adapter weren't available in the 404.astro, when using the astro dev command,

  • #​12925 44841fc Thanks @​ascorbic! - Ensures image styles are not imported unless experimental responsive images are enabled

  • #​12926 8e64bb7 Thanks @​oliverlynch! - Improves remote image cache efficiency by separating image data and metadata into a binary and sidecar JSON file.

  • #​12920 8b9d530 Thanks @​bluwy! - Processes markdown with empty body as remark and rehype plugins may add additional content or frontmatter

  • #​12918 fd12a26 Thanks @​lameuler! - Fixes a bug where the logged output path does not match the actual output path when using build.format: 'preserve'

  • #​12676 2ffc0fc Thanks @​koyopro! - Allows configuring Astro modules TypeScript compilation with the vite.esbuild config

  • #​12938 dbb04f3 Thanks @​ascorbic! - Fixes a bug where content collections would sometimes appear empty when first running astro dev

  • #​12937 30edb6d Thanks @​ematipico! - Fixes a bug where users could use Astro.request.headers during a rewrite inside prerendered routes. This an invalid behaviour, and now Astro will show a warning if this happens.

  • #​12937 30edb6d Thanks @​ematipico! - Fixes an issue where the use of Astro.rewrite would trigger the invalid use of Astro.request.headers

v5.1.3

Compare Source

Patch Changes

v5.1.2

Compare Source

Patch Changes
  • #​12798 7b0cb85 Thanks @​ascorbic! - Improves warning logs for invalid content collection configuration

  • #​12781 96c4b92 Thanks @​ascorbic! - Fixes a regression that caused default() to not work with reference()

  • #​12820 892dd9f Thanks @​ascorbic! - Fixes a bug that caused cookies to not be deleted when destroying a session

  • #​12864 440d8a5 Thanks @​kaytwo! - Fixes a bug where the session ID wasn't correctly regenerated

  • #​12768 524c855 Thanks @​ematipico! - Fixes an issue where Astro didn't print error logs when Astro Islands were used in incorrect cases.

  • #​12814 f12f111 Thanks @​ematipico! - Fixes an issue where Astro didn't log anything in case a file isn't created during the build.

  • #​12875 e109002 Thanks @​ascorbic! - Fixes a bug in emulated legacy collections where the entry passed to the getCollection filter function did not include the legacy entry fields.

  • #​12768 524c855 Thanks @​ematipico! - Fixes an issue where Astro was printing the incorrect output format when running the astro build command

  • #​12810 70a9f0b Thanks @​louisescher! - Fixes server islands failing to check content-type header under certain circumstances

    Sometimes a reverse proxy or similar service might modify the content-type header to include the charset or other parameters in the media type of the response. This previously wasn't handled by the client-side server island script and thus removed the script without actually placing the requested content in the DOM. This fix makes it so the script checks if the header starts with the proper content type instead of exactly matching text/html, so the following will still be considered a valid header: text/html; charset=utf-8

  • #​12816 7fb2184 Thanks @​ematipico! - Fixes an issue where an injected route entrypoint wasn't correctly marked because the resolved file path contained a query parameter.

    This fixes some edge case where some injected entrypoint were not resolved when using an adapter.

v5.1.1

Compare Source

Patch Changes

v5.1.0

Compare Source

Minor Changes
  • #​12441 b4fec3c Thanks @​ascorbic! - Adds experimental session support

    Sessions are used to store user state between requests for server-rendered pages, such as login status, shopping cart contents, or other user-specific data.

v5.0.9

Compare Source

Patch Changes

v5.0.8

Compare Source

Patch Changes

v5.0.7

Compare Source

Patch Changes

v5.0.6

Compare Source

Patch Changes

v5.0.5

Compare Source

Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes
  • #​12645 8704c54 Thanks @​sarah11918! - Updates some reference links in error messages for new v5 docs.

  • #​12641 48ca399 Thanks @​ascorbic! - Fixes a bug where astro info --copy wasn't working correctly on macOS systems.

  • #​12461 62939ad Thanks @​kyr0! - Removes the misleading log message telling that a custom renderer is not recognized while it clearly is and works.

  • #​12642 ff18b9c Thanks @​ematipico! - Provides more information when logging a warning for accessing Astro.request.headers in prerendered pages

  • #​12634 03958d9 Thanks @​delucis! - Improves error message formatting for user config and content collection frontmatter

  • #​12547 6b6e18d Thanks @​mtwilliams-code! - Fixes a bug where URL search parameters weren't passed when using the i18n fallback feature.

  • #​12449 e6b8017 Thanks @​apatel369! - Fixes an issue where the custom assetFileNames configuration caused assets to be incorrectly moved to the server directory instead of the client directory, resulting in 404 errors when accessed from the client side.

  • #​12518 e216250 Thanks @​ematipico! - Fixes an issue where SSR error pages would return duplicated custom headers.

  • #​12625 74bfad0 Thanks @​ematipico! - Fixes an issue where the experimental.svg had incorrect type, resulting in some errors in the editors.

  • #​12631 dec0305 Thanks @​ascorbic! - Fixes a bug where the class attribute was rendered twice on the image component

  • #​12623 0e4fecb Thanks @​ascorbic! - Correctly handles images in content collections with uppercase file extensions

  • #​12633 8a551c1 Thanks @​bluwy! - Cleans up content layer sync during builds and programmatic sync() calls

  • #​12640 22e405a Thanks @​ascorbic! - Fixes a bug that caused content collections to be returned empty when run in a test environment

  • #​12613 306c9f9 Thanks @​matthewp! - Fix use of cloned requests in middleware with clientAddress

    When using context.clientAddress or Astro.clientAddress Astro looks up the address in a hidden property. Cloning a request can cause this hidden property to be lost.

    The fix is to pass the address as an internal property instead, decoupling it from the request.

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes
  • #​11798 e9e2139 Thanks @​matthewp! - Unflag globalRoutePriority

    The previously experimental feature globalRoutePriority is now the default in Astro 5.

    This was a refactoring of route prioritization in Astro, making it so that injected routes, file-based routes, and redirects are all prioritized using the same logic. This feature has been enabled for all Starlight projects since it was added and should not affect most users.

  • #​11864 ee38b3a Thanks @​ematipico! - ### [changed]: entryPoint type inside the hook astro:build:ssr
    In Astro v4.x, the entryPoint type was RouteData.

    Astro v5.0 the entryPoint type is IntegrationRouteData, which contains a subset of the RouteData type. The fields isIndex and fallbackRoutes were removed.

What should I do?

Update your adapter to change the type of entryPoint from RouteData to IntegrationRouteData.

-import type {RouteData} from 'astro';
+import type {IntegrationRouteData} from "astro"

-function useRoute(route: RouteData) {
+function useRoute(route: IntegrationRouteData) {

}

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

Copy link
Contributor Author

renovate bot commented Dec 6, 2024

⚠️ 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: package-lock.json
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @astrojs/mdx@3.1.9
npm warn Found: astro@5.3.0
npm warn node_modules/astro
npm warn   astro@"5.3.0" from the root project
npm warn   2 more (astro-expressive-code, starlight-links-validator)
npm warn
npm warn Could not resolve dependency:
npm warn peer astro@"^4.8.0" from @astrojs/mdx@3.1.9
npm warn node_modules/@astrojs/mdx
npm warn   @astrojs/mdx@"^3.1.3" from @astrojs/starlight@0.29.3
npm warn   node_modules/@astrojs/starlight
npm warn   1 more (starlight-blog)
npm warn
npm warn Conflicting peer dependency: astro@4.16.18
npm warn node_modules/astro
npm warn   peer astro@"^4.8.0" from @astrojs/mdx@3.1.9
npm warn   node_modules/@astrojs/mdx
npm warn     @astrojs/mdx@"^3.1.3" from @astrojs/starlight@0.29.3
npm warn     node_modules/@astrojs/starlight
npm warn     1 more (starlight-blog)
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @astrojs/starlight@0.29.3
npm error Found: astro@5.3.0
npm error node_modules/astro
npm error   astro@"5.3.0" from the root project
npm error   peer astro@"^4.0.0-beta || ^5.0.0-beta || ^3.3.0" from astro-expressive-code@0.38.3
npm error   node_modules/astro-expressive-code
npm error     astro-expressive-code@"^0.38.3" from @astrojs/starlight@0.29.3
npm error     node_modules/@astrojs/starlight
npm error       @astrojs/starlight@"0.29.3" from the root project
npm error       2 more (starlight-blog, starlight-links-validator)
npm error   1 more (starlight-links-validator)
npm error
npm error Could not resolve dependency:
npm error peer astro@"^4.14.0" from @astrojs/starlight@0.29.3
npm error node_modules/@astrojs/starlight
npm error   @astrojs/starlight@"0.29.3" from the root project
npm error   peer @astrojs/starlight@">=0.28.3" from starlight-blog@0.15.0
npm error   node_modules/starlight-blog
npm error     starlight-blog@"0.15.0" from the root project
npm error   1 more (starlight-links-validator)
npm error
npm error Conflicting peer dependency: astro@4.16.18
npm error node_modules/astro
npm error   peer astro@"^4.14.0" from @astrojs/starlight@0.29.3
npm error   node_modules/@astrojs/starlight
npm error     @astrojs/starlight@"0.29.3" from the root project
npm error     peer @astrojs/starlight@">=0.28.3" from starlight-blog@0.15.0
npm error     node_modules/starlight-blog
npm error       starlight-blog@"0.15.0" from the root project
npm error     1 more (starlight-links-validator)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-02-13T15_35_16_963Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-02-13T15_35_16_963Z-debug-0.log

@renovate renovate bot force-pushed the renovate/astro-5.x branch from fef22e6 to 2fa74b4 Compare December 9, 2024 21:00
@renovate renovate bot changed the title chore(deps): update astro to 5.0.3 chore(deps): update astro to 5.0.4 Dec 9, 2024
@renovate renovate bot force-pushed the renovate/astro-5.x branch from 2fa74b4 to 367da9c Compare December 11, 2024 14:16
@renovate renovate bot changed the title chore(deps): update astro to 5.0.4 chore(deps): update astro to 5.0.5 Dec 11, 2024
@renovate renovate bot force-pushed the renovate/astro-5.x branch 2 times, most recently from 9c5de82 to 49e937d Compare December 16, 2024 16:00
@renovate renovate bot changed the title chore(deps): update astro to 5.0.5 chore(deps): update astro to 5.0.6 Dec 16, 2024
@renovate renovate bot force-pushed the renovate/astro-5.x branch from 49e937d to 8e22580 Compare December 16, 2024 21:24
@renovate renovate bot changed the title chore(deps): update astro to 5.0.6 chore(deps): update astro to 5.0.8 Dec 16, 2024
@renovate renovate bot force-pushed the renovate/astro-5.x branch from 8e22580 to 2a471aa Compare December 17, 2024 06:48
@renovate renovate bot changed the title chore(deps): update astro to 5.0.8 chore(deps): update astro to 5.0.9 Dec 17, 2024
@renovate renovate bot force-pushed the renovate/astro-5.x branch from 2a471aa to 9b43443 Compare December 19, 2024 14:51
@renovate renovate bot changed the title chore(deps): update astro to 5.0.9 chore(deps): update astro to 5.1.0 Dec 19, 2024
@renovate renovate bot changed the title chore(deps): update astro to 5.1.0 chore(deps): update astro to 5.1.0 - autoclosed Dec 19, 2024
@renovate renovate bot closed this Dec 19, 2024
@renovate renovate bot deleted the renovate/astro-5.x branch December 19, 2024 15:53
@renovate renovate bot changed the title chore(deps): update astro to 5.1.0 - autoclosed chore(deps): update astro to 5.1.0 Dec 19, 2024
@renovate renovate bot reopened this Dec 19, 2024
@renovate renovate bot force-pushed the renovate/astro-5.x branch 3 times, most recently from 097fd75 to 8509c9a Compare December 20, 2024 13:59
@renovate renovate bot changed the title chore(deps): update astro to 5.1.0 chore(deps): update astro to 5.1.1 Dec 20, 2024
@renovate renovate bot force-pushed the renovate/astro-5.x branch from 8509c9a to e67ea2e Compare January 2, 2025 14:14
@renovate renovate bot changed the title chore(deps): update astro to 5.1.1 chore(deps): update astro to 5.1.2 Jan 2, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from e67ea2e to 2dbcd08 Compare January 8, 2025 13:35
@renovate renovate bot changed the title chore(deps): update astro to 5.1.2 chore(deps): update astro to 5.1.3 Jan 8, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from 2dbcd08 to 78927cc Compare January 9, 2025 11:15
@renovate renovate bot changed the title chore(deps): update astro to 5.1.3 chore(deps): update astro to 5.1.4 Jan 9, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from 78927cc to ee3602e Compare January 10, 2025 10:26
@renovate renovate bot changed the title chore(deps): update astro to 5.1.4 chore(deps): update astro to 5.1.5 Jan 10, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from ee3602e to ffc561c Compare January 13, 2025 17:17
@renovate renovate bot changed the title chore(deps): update astro to 5.1.5 chore(deps): update astro to 5.1.6 Jan 13, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from ffc561c to 92b2867 Compare January 15, 2025 11:01
@renovate renovate bot changed the title chore(deps): update astro to 5.1.6 chore(deps): update astro to 5.1.7 Jan 15, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from 92b2867 to c117e9e Compare January 20, 2025 21:52
@renovate renovate bot changed the title chore(deps): update astro to 5.1.7 chore(deps): update astro to 5.1.8 Jan 20, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from c117e9e to ea3a9ca Compare January 23, 2025 18:32
@renovate renovate bot changed the title chore(deps): update astro to 5.1.8 chore(deps): update astro to 5.1.9 Jan 23, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from ea3a9ca to 9b2ec56 Compare January 27, 2025 13:15
@renovate renovate bot changed the title chore(deps): update astro to 5.1.9 chore(deps): update astro to 5.1.10 Jan 27, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from 9b2ec56 to 90385ef Compare January 30, 2025 12:55
@renovate renovate bot changed the title chore(deps): update astro to 5.1.10 chore(deps): update astro to 5.2.0 Jan 30, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from 90385ef to e2335e9 Compare January 30, 2025 17:22
@renovate renovate bot changed the title chore(deps): update astro to 5.2.0 chore(deps): update astro to 5.2.1 Jan 30, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from e2335e9 to 7b9f782 Compare January 31, 2025 14:00
@renovate renovate bot changed the title chore(deps): update astro to 5.2.1 chore(deps): update astro to 5.2.2 Jan 31, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from 7b9f782 to 5a1d1ce Compare January 31, 2025 21:05
@renovate renovate bot changed the title chore(deps): update astro to 5.2.2 chore(deps): update astro to 5.2.3 Jan 31, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from 5a1d1ce to accf2bf Compare February 4, 2025 14:23
@renovate renovate bot changed the title chore(deps): update astro to 5.2.3 chore(deps): update astro to 5.2.4 Feb 4, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from accf2bf to 7146d8b Compare February 4, 2025 17:59
@renovate renovate bot changed the title chore(deps): update astro to 5.2.4 chore(deps): update astro to 5.2.5 Feb 4, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from 7146d8b to ce5ac7a Compare February 12, 2025 15:31
@renovate renovate bot changed the title chore(deps): update astro to 5.2.5 chore(deps): update astro to 5.2.6 Feb 12, 2025
@renovate renovate bot force-pushed the renovate/astro-5.x branch from ce5ac7a to 44cd81b Compare February 13, 2025 15:35
@renovate renovate bot changed the title chore(deps): update astro to 5.2.6 chore(deps): update astro to 5.3.0 Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants