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.

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

chore(deps): update astro (major) - autoclosed #935

Closed
wants to merge 1 commit into from
Closed

chore(deps): update astro (major) - autoclosed #935

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 2, 2023 •
edited
Loading

Mend Renovate logo banner

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@astrojs/react (source) 2.3.2 -> 3.0.5 age adoption passing confidence
@astrojs/svelte (source) 3.1.1 -> 4.0.4 age adoption passing confidence
astro (source) 2.10.14 -> 3.5.5 age adoption passing confidence

Release Notes

withastro/astro (@​astrojs/react)

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

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.

  • #​8179 6011d52d3 Thanks @​matthewp! - Astro 3.0 Release Candidate

  • #​7924 519a1c4e8 Thanks @​matthewp! - Support for React Refresh

    The React integration now fully supports React Refresh and is backed by @vitejs/plugin-react.

    Also included in this change are new include and exclude config options. Use these if you want to use React alongside another JSX framework; include specifies files to be compiled for React and exclude does the opposite.

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

v4.0.4

Compare Source

Patch Changes

v4.0.3

Compare Source

Patch Changes

v4.0.2

Compare Source

Patch Changes

v4.0.1

Compare Source

Patch Changes

v4.0.0

Compare Source

Major Changes
Patch Changes
withastro/astro (astro)

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:

v3.4.4

Compare Source

Patch Changes

v3.4.3

Compare Source

Patch Changes

v3.4.2

Compare Source

Patch Changes

v3.4.1

Compare Source

Patch Changes

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

Configuration

📅 Schedule: Branch creation - "on the first saturday of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

@vercel
Copy link

vercel bot commented Sep 2, 2023 •
edited
Loading

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

Name Status Preview Comments Updated (UTC)
zustand-rx ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 20, 2023 5:25pm

@renovate renovate bot assigned patdx Sep 2, 2023
@renovate renovate bot force-pushed the renovate/major-astro branch from 1829630 to 9338747 Compare September 4, 2023 09:29
@renovate renovate bot force-pushed the renovate/major-astro branch from 9338747 to ff25432 Compare September 6, 2023 14:53
@renovate renovate bot force-pushed the renovate/major-astro branch from ff25432 to 3bbd77b Compare September 7, 2023 00:21
@renovate renovate bot force-pushed the renovate/major-astro branch from 3bbd77b to d3ec3e3 Compare September 8, 2023 14:23
@renovate renovate bot force-pushed the renovate/major-astro branch from d3ec3e3 to 88d9174 Compare September 12, 2023 19:06
@renovate renovate bot force-pushed the renovate/major-astro branch from 88d9174 to 1df1b1d Compare September 14, 2023 17:42
@renovate renovate bot force-pushed the renovate/major-astro branch from 1df1b1d to 1584a68 Compare September 19, 2023 14:07
@renovate renovate bot force-pushed the renovate/major-astro branch from 1584a68 to 345b712 Compare September 21, 2023 22:12
@renovate renovate bot force-pushed the renovate/major-astro branch from 345b712 to f317053 Compare September 25, 2023 11:16
@renovate renovate bot force-pushed the renovate/major-astro branch from f317053 to 8ca7818 Compare September 25, 2023 22:46
@renovate renovate bot force-pushed the renovate/major-astro branch from 8ca7818 to 7bc84e3 Compare September 28, 2023 22:50
@renovate renovate bot force-pushed the renovate/major-astro branch from 7bc84e3 to a0d9df3 Compare October 2, 2023 09:56
@renovate renovate bot force-pushed the renovate/major-astro branch from a0d9df3 to a5decce Compare October 2, 2023 16:59
@renovate renovate bot force-pushed the renovate/major-astro branch from a5decce to 4b9e819 Compare October 5, 2023 12:41
@renovate renovate bot force-pushed the renovate/major-astro branch from 2ec6286 to 62b670a Compare October 24, 2023 17:34
@renovate renovate bot force-pushed the renovate/major-astro branch from 62b670a to d991e4e Compare October 26, 2023 16:59
@renovate renovate bot force-pushed the renovate/major-astro branch from d991e4e to 4b4f525 Compare October 28, 2023 04:04
@renovate renovate bot force-pushed the renovate/major-astro branch from 4b4f525 to 5a71f54 Compare November 1, 2023 17:00
@renovate renovate bot force-pushed the renovate/major-astro branch from 5a71f54 to 37ae731 Compare November 1, 2023 20:03
@renovate renovate bot force-pushed the renovate/major-astro branch from 37ae731 to 97f1516 Compare November 2, 2023 20:01
@renovate renovate bot force-pushed the renovate/major-astro branch from 97f1516 to c511c0e Compare November 8, 2023 10:14
@renovate renovate bot force-pushed the renovate/major-astro branch from c511c0e to 3b8d630 Compare November 9, 2023 19:06
@renovate renovate bot force-pushed the renovate/major-astro branch from 3b8d630 to 4e2f0d1 Compare November 10, 2023 17:11
@renovate renovate bot force-pushed the renovate/major-astro branch from 4e2f0d1 to af14ff2 Compare November 12, 2023 07:22
@renovate renovate bot force-pushed the renovate/major-astro branch from af14ff2 to 36af14e Compare November 14, 2023 19:52
@renovate renovate bot force-pushed the renovate/major-astro branch from 36af14e to 0d292de Compare November 16, 2023 17:36
@renovate renovate bot force-pushed the renovate/major-astro branch from 0d292de to 8f36b0c Compare November 20, 2023 17:23
@renovate renovate bot changed the title chore(deps): update astro (major) chore(deps): update astro (major) - autoclosed Nov 20, 2023
@renovate renovate bot closed this Nov 20, 2023
@renovate renovate bot deleted the renovate/major-astro branch November 20, 2023 17:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@patdx patdx

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@patdx