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 dependency astro to v3 - autoclosed #77

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 2, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
astro (source) ^2.9.7 -> ^3.0.0 age adoption passing confidence

Release Notes

withastro/astro (astro)

v3.4.0

Compare Source

Minor Changes
  • #​8755 fe4079f05 Thanks @​matthewp! - Page Partials

    A page component can now be identified as a partial page, which will render its HTML content without including a <! DOCTYPE html> declaration nor any <head> content.

    A rendering library, like htmx or Stimulus or even just jQuery can access partial content on the client to dynamically update only parts of a page.

    Pages marked as partials do not have a doctype or any head content included in the rendered result. You can mark any page as a partial by setting this option:

v3.3.4

Compare Source

Patch Changes

v3.3.3

Compare Source

Patch Changes

v3.3.2

Compare Source

Patch Changes

v3.3.1

Compare Source

Patch Changes

v3.3.0

Compare Source

Minor Changes
  • #​8808 2993055be Thanks @​delucis! - Adds support for an --outDir CLI flag to astro build

  • #​8502 c4270e476 Thanks @​bluwy! - Updates the internal shiki syntax highlighter to shikiji, an ESM-focused alternative that simplifies bundling and maintenance.

    There are no new options and no changes to how you author code blocks and syntax highlighting.

    Potentially breaking change: While this refactor should be transparent for most projects, the transition to shikiji now produces a smaller HTML markup by attaching a fallback color style to the pre or code element, instead of to the line span directly. For example:

    Before:

    <code class="astro-code" style="background-color: #&#8203;24292e">
      <pre>
        <span class="line" style="color: #e1e4e8">my code</span>
      </pre>
    </code>

    After:

    <code class="astro-code" style="background-color: #&#8203;24292e; color: #e1e4e8">
      <pre>
        <span class="line">my code<span>
      </pre>
    </code>

    This does not affect the colors as the span will inherit the color from the parent, but if you're relying on a specific HTML markup, please check your site carefully after upgrading to verify the styles.

  • #​8798 f369fa250 Thanks @​Princesseuh! - Fixed tsconfig.json's new array format for extends not working. This was done by migrating Astro to use tsconfck instead of tsconfig-resolver to find and parse tsconfig.json files.

  • #​8620 b2ae9ee0c Thanks @​Princesseuh! - Adds experimental support for generating srcset attributes and a new <Picture /> component.

v3.2.4

Compare Source

Patch Changes

v3.2.3

Compare Source

Patch Changes

v3.2.2

Compare Source

Patch Changes

v3.2.1

Compare Source

Patch Changes

v3.2.0

Compare Source

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 '@&#8203;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 === '@&#8203;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 />

    The View Transitions router now does route announcement. When transitioning between pages with a traditional MPA approach, assistive technologies will announce the page title when the page finishes loading. This does not automatically happen during client-side routing, so visitors relying on these technologies to announce routes are not aware when a page has changed.

    The view transitions route announcer runs after the astro:page-load event, looking for the page <title> to announce. If one cannot be found, the announcer falls back to the first <h1> it finds, or otherwise announces the pathname. We recommend you always include a <title> in each page for accessibility.

    See the View Transitions docs for more on how accessibility is handled.

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
  • #​8467 ecc65abbf Thanks @​Princesseuh! - Add a new image.endpoint setting to allow using a custom endpoint in dev and SSR

  • #​8518 2c4fc878b Thanks @​Princesseuh! - Adds support for using AVIF (.avif) files with the Image component. Importing an AVIF file will now correctly return the same object shape as other image file types. See the Image docs for more information on the different properties available on the returned object.

  • #​8464 c92e0acd7 Thanks @​Princesseuh! - Add types for the object syntax for style (ex: style={{color: 'red'}})

Patch Changes

v3.0.13

Compare Source

Patch Changes

v3.0.12

Compare Source

Patch Changes

v3.0.11

Compare Source

Patch Changes

v3.0.10

Compare Source

Patch Changes

v3.0.9

Compare Source

Patch Changes

v3.0.8

Compare Source

Patch Changes

v3.0.7

Compare Source

Patch Changes

v3.0.6

Compare Source

Patch Changes

v3.0.5

Compare Source

Patch Changes

v3.0.4

Compare Source

Patch Changes
  • #​8324 0752cf368 Thanks @​matthewp! - Prevent React hook call warnings when used with MDX

    When React and MDX are used in the same project, if the MDX integration is added before React, previously you'd get a warning about hook calls.

    This makes it so that the MDX integration's JSX renderer is last in order.

v3.0.3

Compare Source

Patch Changes

v3.0.2

Compare Source

Patch Changes

v3.0.1

Compare Source

Patch Changes

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.

  • #​8188 364d861bd Thanks @​ematipico! - Removed automatic flattening of getStaticPaths result. .flatMap and .flat should now be used to ensure that you're returning a flat array.

  • #​8113 2484dc408 Thanks @​Princesseuh! - This import alias is no longer included by default with astro:assets. If you were using this alias with experimental assets, you must convert them to relative file paths, or create your own import aliases.

v2.10.15

Compare Source

Patch Changes

v2.10.14

Compare Source

Patch Changes

v2.10.13

Compare Source

Patch Changes

v2.10.12

Compare Source

Patch Changes
  • #​8144 04caa99c4 Thanks @​lilnasy! - Fixed an issue where data entries' id included backslashes instead of forward slashes on Windows.

v2.10.11

Compare Source

Patch Changes

v2.10.10

Compare Source

Patch Changes
  • #​8127 b12c8471f Thanks @​natemoo-re! - Do not throw Error when users pass an object with a "type" property

  • #​8092 7177f7579 Thanks @​natemoo-re! - Ensure dotfiles are cleaned during static builds

  • #​8122 fa6b68a77 Thanks @​natemoo-re! - Improve fidelity of time stats when running astro build

  • #​8070 097a8e4e9 Thanks @​lilnasy! - Fix a handful of edge cases with prerendered 404/500 pages

  • #​8123 1f6497c33 Thanks @​natemoo-re! - Open to configured base when astro dev --open runs

  • #​8105 0e0fa605d Thanks @​martrapp! - ViewTransition: bug fix for lost scroll position in browser history

  • #​8116 b290f0a99 Thanks @​martrapp! - On back navigation only animate view transitions that were animated going forward.

  • #​7778 d6b494376 Thanks @​y-nk! - Added support for optimizing remote images from authorized sources when using astro:assets. This comes with two new parameters to specify which domains (image.domains) and host patterns (image.remotePatterns) are authorized for remote images.

    For example, the following configuration will only allow remote images from astro.build to be optimized:

    // astro.config.mjs
    export default defineConfig({
      image: {
        domains: ['astro.build'],
      },
    });

    The following configuration will only allow remote images from HTTPS hosts:

    // astro.config.mjs
    export default defineConfig({
      image: {
        remotePatterns: [{ protocol: 'https' }],
      },
    });
  • #​8109 da6e3da1c Thanks @​martrapp! - fix: reinsert attribute to specify direction of ViewTransition (forward / back)

v2.10.9

Compare Source

Patch Changes

v2.10.8

Compare Source

Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 has been generated by Mend Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented Sep 2, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
joshuakgoldberg-dot-com ❌ Failed (Inspect) Oct 30, 2023 4:38pm

@renovate renovate bot added the dependencies label Sep 2, 2023
@renovate renovate bot force-pushed the renovate/astro-3.x branch from ab58d69 to 283d0f8 Compare September 2, 2023 23:06
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 283d0f8 to c4b101a Compare September 3, 2023 01:27
@renovate renovate bot force-pushed the renovate/astro-3.x branch from c4b101a to 58df9f7 Compare September 3, 2023 03:54
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 58df9f7 to f35528d Compare September 3, 2023 19:01
@renovate renovate bot force-pushed the renovate/astro-3.x branch from f35528d to 935f70a Compare September 5, 2023 08:03
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 935f70a to 6bc3153 Compare September 7, 2023 16:59
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 6bc3153 to d80c772 Compare September 7, 2023 18:13
@renovate renovate bot force-pushed the renovate/astro-3.x branch from d80c772 to 580a9d7 Compare September 9, 2023 01:00
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 580a9d7 to 5ece2ae Compare September 11, 2023 14:18
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 5ece2ae to 8b92f5c Compare September 20, 2023 15:40
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 8b92f5c to 6f6966a Compare September 23, 2023 15:35
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 6f6966a to 578ab69 Compare September 23, 2023 18:35
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 578ab69 to a18741c Compare September 24, 2023 21:52
@renovate renovate bot force-pushed the renovate/astro-3.x branch from a18741c to 803ecb0 Compare September 26, 2023 11:31
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 803ecb0 to ba4e925 Compare October 3, 2023 12:56
@renovate renovate bot force-pushed the renovate/astro-3.x branch from ba4e925 to a02ddc9 Compare October 5, 2023 07:58
@renovate renovate bot force-pushed the renovate/astro-3.x branch from a02ddc9 to 77db357 Compare October 5, 2023 22:21
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 77db357 to ca59aa1 Compare October 10, 2023 12:12
@renovate renovate bot force-pushed the renovate/astro-3.x branch from ca59aa1 to 4b894f9 Compare October 13, 2023 18:06
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 4b894f9 to 68f51b0 Compare October 17, 2023 22:14
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 68f51b0 to f6f743a Compare October 18, 2023 02:16
@renovate renovate bot force-pushed the renovate/astro-3.x branch from f6f743a to 6bfbf15 Compare October 20, 2023 14:30
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 6bfbf15 to 3821010 Compare October 25, 2023 08:32
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 3821010 to 2a8c6c0 Compare October 26, 2023 10:40
@renovate renovate bot force-pushed the renovate/astro-3.x branch from 2a8c6c0 to ac3cbc8 Compare October 27, 2023 22:25
@renovate renovate bot force-pushed the renovate/astro-3.x branch from ac3cbc8 to 9a8e795 Compare October 30, 2023 16:37
@renovate renovate bot changed the title chore(deps): update dependency astro to v3 chore(deps): update dependency astro to v3 - autoclosed Nov 2, 2023
@renovate renovate bot closed this Nov 2, 2023
@renovate renovate bot deleted the renovate/astro-3.x branch November 2, 2023 15:47
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