Sourced from astro's releases.

@​astrojs/markdown-remark@​3.2.0

Minor Changes

• #8475 d93987824 Thanks @​webpro! - feat(markdown): Add support for imageReference paths when collecting images

• #8532 7522bb491 Thanks @​bluwy! - Export createMarkdownProcessor and deprecate renderMarkdown API

Patch Changes

• Updated dependencies [7522bb491, ecc65abbf, 2c4fc878b, c92e0acd7, f95febf96, b85c8a78a, 45364c345]:
  • [email protected]

[email protected]

Minor Changes

• #8696 2167ffd72 Thanks @​matthewp! - Support adding integrations dynamically

  Astro integrations can now themselves dynamically add and configure additional integrations during set-up. This makes it possible for integration authors to bundle integrations more intelligently for their users.

  In the following example, a custom integration checks whether @astrojs/sitemap is already configured. If not, the integration adds Astro’s sitemap integration, passing any desired configuration options:

  import sitemap from '@astrojs/sitemap';
  import type { AstroIntegration } from 'astro';
  const MyIntegration = (): AstroIntegration => {
  return {
  name: 'my-integration',
  'astro:config:setup': ({ config, updateConfig }) => {
    // Look for sitemap in user-configured integrations.
    const userSitemap = config.integrations.find(
      ({ name }) => name === '@astrojs/sitemap'
    );
  if (!userSitemap) {
  // If sitemap wasn’t found, add it.
  updateConfig({
  integrations: [sitemap({ /* opts */ }],
  });
  }
  },
  
  };
  };

• #8696 2167ffd72 Thanks @​matthewp! - View transitions can now be triggered from JavaScript!

  Import the client-side router from "astro:transitions/client" and enjoy your new remote control for navigation:

... (truncated)

Sourced from astro's changelog.

3.2.0

Minor Changes

• #8696 2167ffd72 Thanks @​matthewp! - Support adding integrations dynamically

  Astro integrations can now themselves dynamically add and configure additional integrations during set-up. This makes it possible for integration authors to bundle integrations more intelligently for their users.

  In the following example, a custom integration checks whether @astrojs/sitemap is already configured. If not, the integration adds Astro’s sitemap integration, passing any desired configuration options:

  import sitemap from '@astrojs/sitemap';
  import type { AstroIntegration } from 'astro';
  const MyIntegration = (): AstroIntegration => {
  return {
  name: 'my-integration',
  'astro:config:setup': ({ config, updateConfig }) => {
    // Look for sitemap in user-configured integrations.
    const userSitemap = config.integrations.find(
      ({ name }) => name === '@astrojs/sitemap'
    );
  if (!userSitemap) {
  // If sitemap wasn’t found, add it.
  updateConfig({
  integrations: [sitemap({ /* opts */ }],
  });
  }
  },
  
  };
  };

• #8696 2167ffd72 Thanks @​matthewp! - View transitions can now be triggered from JavaScript!

  Import the client-side router from "astro:transitions/client" and enjoy your new remote control for navigation:

  import { navigate } from 'astro:transitions/client';
  // Navigate to the selected option automatically.
  document.querySelector('select').onchange = (ev) => {
  let href = ev.target.value;
  navigate(href);
  };

• #8696 2167ffd72 Thanks @​matthewp! - Route Announcer in <ViewTransitions />

... (truncated)

• 2d33b93 [ci] release (#8695)
• 2167ffd Revert "[ci] release (#8671)" (#8696)
• c4c616c [ci] format
• cfd895d fix(rerouting): check that the new route is different (#8648)
• eada8ab [ci] release (#8671)
• 3c93476 [ci] format
• 824dd46 Support content collections with % in filename (#8684)
• c0708c9 [ci] format
• 408b50c fix(redirects): attempt to get only params in dev mode (#8647)
• e797b68 Fix assets not getting optimized when outDir is outside the CWD (#8670)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)