Skip to content

chore(deps): update astro monorepo #113

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update astro monorepo #113

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 1, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
@astrojs/mdx (source) 1.1.0 -> 1.1.5 age confidence
@astrojs/sitemap (source) 3.0.0 -> 3.6.0 age confidence
@astrojs/tailwind (source) 5.0.0 -> 5.1.5 age confidence
astro (source) 3.1.3 -> 3.6.5 age confidence

Release Notes

withastro/astro (@​astrojs/mdx)

v1.1.5

Compare Source

Patch Changes

v1.1.4

Compare Source

Patch Changes

v1.1.3

Compare Source

Patch Changes

v1.1.2

Compare Source

Patch Changes

v1.1.1

Compare Source

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

v3.6.0

Compare Source

Minor Changes

  • #​14285 bedc31b Thanks @​jdcolombo! - Adds a new configuration option namespaces for more control over XML namespaces used in sitemap generation

    Excluding unused namespaces can help create cleaner, more focused sitemaps that are faster for search engines to parse and use less bandwidth. If your site doesn't have news content, videos, or multiple languages, you can exclude those namespaces to reduce XML bloat.

    The namespaces option allows you to configure news, xhtml, image, and video namespaces independently. All namespaces are enabled by default for backward compatibility and no change to existing projects is necessary. But now, you can choose to streamline your XML and avoid unnecessary code.

    For example, to exclude the video namespace from your sitemap, set video: false in your configuration:

    // astro.config.mjs
import { sitemap } from '@​astrojs/sitemap';

export default {
  integrations: [
    sitemap({
      namespaces: {
        video: false,
        // other namespaces remain enabled by default
      }
    })
  ]
};

    The generated XML will not include the xmlns:video namespace:

    <?xml version="1.0" encoding="UTF-8"?>
<urlset
  xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
  xmlns:news="http://www.google.com/schemas/sitemap-news/0.9"
  xmlns:xhtml="http://www.w3.org/1999/xhtml"
  xmlns:image="http://www.google.com/schemas/sitemap-image/1.1"
>
  <!-- ... -->
</urlset>

v3.5.1

Compare Source

Patch Changes
  • #​14233 896886c Thanks @​gouravkhunger! - Fixes the issue with the option lastmod where if it is defined it applies correctly to <url> entries in each sitemap-${i}.xml file but not the <sitemap> entries in the root sitemap-index.xml file.

v3.5.0

Compare Source

Minor Changes

  • #​13682 5824b32 Thanks @​gouravkhunger! - Adds a customSitemaps option to include extra sitemaps in the sitemap-index.xml file generated by Astro.

    This is useful for multi-framework setups on the same domain as your Astro site (example.com), such as a blog at example.com/blog whose sitemap is generated by another framework.

    The following example shows configuring your Astro site to include sitemaps for an externally-generated blog and help center along with the generated sitemap entries in sitemap-index.xml:

    Example:

    import { defineConfig } from 'astro/config';
import sitemap from '@&#8203;astrojs/sitemap';

export default defineConfig({
  site: 'https://example.com',
  integrations: [
    sitemap({
      customSitemaps: [
        'https://example.com/blog/sitemap.xml',
        'https://example.com/helpcenter/sitemap.xml',
      ],
    }),
  ],
});

    Learn more in the @astrojs/sitemap configuration documentation.

v3.4.2

Compare Source

Patch Changes

v3.4.1

Compare Source

Patch Changes

v3.4.0

Compare Source

Minor Changes

  • #​13753 90293de Thanks @​mattyoho! - Customize the filenames of sitemap XML files generated by the @astro/sitemap integration by setting filenameBase in the integration configuration settings. This may be useful when deploying an Astro site at a path on a domain with preexisting sitemap files.

    Generated sitemap files will appear at /sitemap-0.xml and /sitemap-index.xml by default, which may conflict with preexisting files. Set filenameBase to a custom value to avoid that if so:

    import { defineConfig } from 'astro/config';
import sitemap from '@&#8203;astrojs/sitemap';

export default defineConfig({
  site: 'https://example.com',
  integrations: [
    sitemap({
      filenameBase: 'astronomy-sitemap',
    }),
  ],
});

    This will yield sitemap and index files as https://example.com/astronomy-sitemap-0.xml and https://example.com/astronomy-sitemap-index.xml.

v3.3.1

Patch Changes

v3.3.0

Minor Changes

v3.2.1

Compare Source

Patch Changes

v3.2.0

Compare Source

Minor Changes

v3.1.6

Compare Source

Patch Changes

v3.1.5

Compare Source

Patch Changes

v3.1.4

Compare Source

Patch Changes

v3.1.3

Compare Source

Patch Changes

v3.1.2

Compare Source

Patch Changes

v3.1.1

Compare Source

Patch Changes

v3.1.0

Compare Source

Minor Changes

  • #​9846 9b78c992750cdb99c40a89a00ea2a0d1c00877d7 Thanks @​ktym4a! - Adds a new configuration option prefix that allows you to change the default sitemap-*.xml file name.

    By default, running astro build creates both sitemap-index.xml and sitemap-0.xml in your output directory.

    To change the names of these files (e.g. to astrosite-index.xml and astrosite-0.xml), set the prefix option in your sitemap integration configuration:

    import { defineConfig } from 'astro/config';
import sitemap from '@&#8203;astrojs/sitemap';
export default defineConfig({
  site: 'https://example.com',
  integrations: [
    sitemap({
      prefix: 'astrosite-',
    }),
  ],
});

    This option is useful when Google Search Console is unable to fetch your default sitemap files, but can read renamed files.

v3.0.5

Compare Source

Patch Changes

v3.0.4

Compare Source

Patch Changes

v3.0.3

Compare Source

Patch Changes

v3.0.2

Compare Source

Patch Changes

v3.0.1

Compare Source

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

v5.1.5

Compare Source

Patch Changes

v5.1.4

Compare Source

Patch Changes

v5.1.3

Compare Source

Patch Changes

v5.1.2

Compare Source

Patch Changes

v5.1.1

Compare Source

Patch Changes

v5.1.0

Compare Source

Minor Changes
Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes
withastro/astro (astro)

v3.6.5

Compare Source

Patch Changes

  • #​10287 a90d685d7 Thanks @​ematipico! - Fixes an issue where in Node SSR, the image endpoint could be used maliciously to reveal unintended information about the underlying system.

    Thanks to Google Security Team for reporting this issue.

v3.6.4

Compare Source

Patch Changes

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

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

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

  • #​9236 27d3e86e4 Thanks @​ematipico! - The configuration i18n.routingStrategy has been replaced with an object called routing.

    export default defineConfig({
  experimental: {
      i18n: {
-          routingStrategy: "prefix-always",
+          routing: {
+              prefixDefaultLocale: true,
+          }
      }
  }
})
    export default defineConfig({
  experimental: {
      i18n: {
-          routingStrategy: "prefix-other-locales",
+          routing: {
+              prefixDefaultLocale: false,
+          }
      }
  }
})

v3.6.3

Compare Source

Patch Changes

v3.6.2

Compare Source

Patch Changes

v3.6.1

Compare Source

Patch Changes

v3.6.0

Compare Source

Minor Changes

  • #​9090 c87223c21 Thanks @​martrapp! - Take full control over the behavior of view transitions!

    Three new events now complement the existing astro:after-swap and astro:page-load events:

    astro: before - preparation; // Control how the DOM and other resources of the target page are loaded
astro: after - preparation; // Last changes before taking off? Remove that loading indicator? Here you go!
astro: before - swap; // Control how the DOM is updated to match the new page

    The astro:before-* events allow you to change properties and strategies of the view transition implementation.
    The astro:after-* events are notifications that a phase is complete.
    Head over to docs to see the full view transitions lifecycle including these new events!

  • #​9092 0ea4bd47e Thanks @​smitbarmase! - Changes the fallback prefetch behavior on slow connections and when data saver mode is enabled. Instead of disabling prefetch entirely, the tap strategy will be used.

  • #​9166 cba6cf32d Thanks @​matthewp! - The Picture component is no longer experimental

    The <Picture /> component, part of astro:assets, has exited experimental status and is now recommended for use. There are no code changes to the component, and no upgrade to your project is necessary.

    This is only a change in documentation/recommendation. If you were waiting to use the <Picture /> component until it had exited the experimental stage, wait no more!

  • #​9092 0ea4bd47e Thanks @​smitbarmase! - Adds a ignoreSlowConnection option to the prefetch() API to prefetch even on data saver mode or slow connection.

v3.5.7

Compare Source

Patch Changes

v3.5.6

Compare Source

Patch Changes

v3.5.5

Compare Source

Patch Changes

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

  • #​9102 60e8210b0 Thanks @​Princesseuh! - In the dev overlay, when there's too many plugins enabled at once, some of the plugins will now be hidden in a separate sub menu to avoid the bar becoming too long

v3.5.4

Compare Source

Patch Changes

v3.5.3

Compare Source

Patch Changes

v3.5.2

Compare Source

Patch Changes

v3.5.1

Compare Source

Patch Changes

v3.5.0

Compare Source

Minor Changes

  • #​8869 f5bdfa272 Thanks @​matthewp! - ## Integration Hooks to add Middleware

    It's now possible in Astro for an integration to add middleware on behalf of the user. Previously when a third party wanted to provide middleware, the user would need to create a src/middleware.ts file themselves. Now, adding third-party middleware is as easy as adding a new integration.

    For integration authors, there is a new addMiddleware function in the astro:config:setup hook. This function allows you to specify a middleware module and the order in which it should be applied:

    // my-package/middleware.js
import { defineMiddleware } from 'astro:middleware';

export const onRequest = defineMiddleware(async (context, next) => {
  const response = await next();

  if (response.headers.get('content-type') === 'text/html') {
    let html = await response.text();
    html = minify(html);
    return new Response(html, {
      status: response.status,
      headers: response.headers,
    });
  }

  return response;
});

    You can now add your integration's middleware and specify that it runs either before or after the application's own defined middleware (defined in src/middleware.{js,ts})

    // my-package/integration.js
export function myIntegration() {
  return {
    name: 'my-integration',
    hooks: {
      'astro:config:setup': ({ addMiddleware }) => {
        addMiddleware({
          entrypoint: 'my-package/middleware',
          order: 'pre',
        });
      },
    },
  };
}

  • #​8854 3e1239e42 Thanks @​natemoo-re! - Provides a new, experimental build cache for Content Collections as part of the Incremental Build RFC. This includes multiple refactors to Astro's build process to optimize how Content Collections are handled, which should provide significant performance improvements for users with many collections.

    Users building a static site can opt-in to preview the new build cache by adding the following flag to your Astro config:

    // astro.config.mjs
export default {
  experimental: {
    contentCollectionCache: true,
  },
};

    When this experimental feature is enabled, the files generated from your content collections will be stored in the cacheDir (by default, node_modules/.astro) and reused between builds. Most CI environments automatically restore files in node_modules/ by default.

    In our internal testing on the real world Astro Docs project, this feature reduces the bundling step of astro build from 133.20s to 10.46s, about 92% faster. The end-to-end astro build process used to take 4min 58s and now takes just over 1min for a total reduction of 80%.

    If you run into any issues with this experimental feature, please let us know!

    You can always bypass the cache for a single build by passing the --force flag to astro build.

    astro build --force

  • #​8963 fda3a0213 Thanks @​matthewp! - Form support in View Transitions router

    The <ViewTransitions /> router can now handle form submissions, allowing the same animated transitions and stateful UI retention on form posts that are already available on <a> links. With this addition, your Astro project can have animations in all of these scenarios:

    • Clicking links between pages.
    • Making stateful changes in forms (e.g. updating site preferences).
    • Manually triggering navigation via the navigate() API.

    This feature is opt-in for semver reasons and can be enabled by adding the handleForms prop to the ` component:

    ---
// src/layouts/MainLayout.astro
import { ViewTransitions } from 'astro:transitions';
---

<html>
  <head>
    <!-- ... -->
    <ViewTransitions handleForms />
  </head>
  <body>
    <!-- ... -->
  </body>
</html>

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

    ---
// src/components/Contact.astro
---

<form class="contact-form" action="/request" method="post" data-astro-reload>
  <!-- ...-->
</form>

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

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

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

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

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

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

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

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

export default defineConfig({
  experimental: {
    i18n: {
      defaultLocale: 'en',
      locales: ['en', 'es', 'pt-br'],
    },
  },
});

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

    ├──

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.

@codesandbox
Copy link

codesandbox bot commented May 1, 2024

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

@netlify
Copy link

netlify bot commented May 1, 2024 •
edited
Loading

❌ Deploy Preview for bosf2023 failed.

Name Link
🔨 Latest commit 0288271
🔍 Latest deploy log https://app.netlify.com/sites/bosf2023/deploys/663210690e04ba00087c117f

@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 0288271 to 575f2a9 Compare January 20, 2025 17:24
@netlify
Copy link

netlify bot commented Jan 20, 2025 •
edited
Loading

❌ Deploy Preview for bosf2023 failed. Why did it fail? →

Name Link
🔨 Latest commit eb30256
🔍 Latest deploy log https://app.netlify.com/projects/bosf2023/deploys/68f7b8b4cb7b100008d671f6

@renovate renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from 35b6e1e to 73428d7 Compare January 30, 2025 17:54
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 73428d7 to 21ebc92 Compare February 9, 2025 13:32
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 21ebc92 to e89e3df Compare March 3, 2025 15:52
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 3 times, most recently from d2148d4 to 3406b12 Compare March 17, 2025 16:40
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 3406b12 to f9b0895 Compare March 18, 2025 16:23
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from a83b1aa to 356803f Compare April 8, 2025 11:15
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from 65a8c56 to 88d534d Compare April 24, 2025 08:45
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 88d534d to 3e87f6b Compare May 12, 2025 11:44
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 3e87f6b to 16baf77 Compare May 19, 2025 17:35
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 16baf77 to 5013e2e Compare May 28, 2025 08:27
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 5013e2e to 5ebf11d Compare June 4, 2025 10:29
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 5ebf11d to ebf6658 Compare June 22, 2025 13:12
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from ebf6658 to 87a4800 Compare July 2, 2025 16:15
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 87a4800 to 8bc44d2 Compare July 28, 2025 11:53
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 3 times, most recently from 0a4386e to 4bf1c72 Compare August 14, 2025 11:58
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from 7ec0672 to ea836ab Compare August 22, 2025 17:08
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from ea836ab to e02aaca Compare August 31, 2025 10:00
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from e02aaca to e4dfc5f Compare September 19, 2025 16:07
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from e4dfc5f to 56be4c8 Compare September 25, 2025 16:48
@renovate renovate bot changed the title fix(deps): update astro monorepo chore(deps): update astro monorepo Sep 25, 2025
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 56be4c8 to eb30256 Compare October 21, 2025 16:45
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.

1 participant