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) #47

Merged
merged 4 commits into from
Sep 14, 2023
Merged

chore(deps): update astro (major) #47

merged 4 commits into from
Sep 14, 2023

Conversation

renovate[bot]
Copy link
Contributor

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

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@astrojs/cloudflare (source) 6.8.1 -> 7.1.0 age adoption passing confidence
@astrojs/netlify (source) 2.6.0 -> 3.0.1 age adoption passing confidence
@astrojs/node (source) 5.3.6 -> 6.0.0 age adoption passing confidence
@astrojs/vercel (source) 3.8.2 -> 5.0.0 age adoption passing confidence
astro (source) 2.10.15 -> 3.1.0 age adoption passing confidence
astro (source) ^2.0.4 -> ^2.0.4 || ^3.0.0 age adoption passing confidence

Release Notes

withastro/astro (@​astrojs/cloudflare)

v7.1.0

Compare Source

Minor Changes
Patch Changes

v7.0.2

Compare Source

Patch Changes

v7.0.1

Compare Source

Patch Changes

v7.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

  • #​8188 7511a4980 Thanks @​ematipico! - When using an adapter that supports neither Squoosh or Sharp, Astro will now automatically use an image service that does not support processing, but still provides the other benefits of astro:assets such as enforcing alt, no CLS etc to users

  • #​8078 2540feedb Thanks @​alexanderniebuhr! - The configuration build.split and build.excludeMiddleware are deprecated.

    You can now configure this behavior using functionPerRoute in your Cloudflare integration config:

    import {defineConfig} from "astro/config";
import cloudflare from '@​astrojs/cloudflare';

export default defineConfig({
-    build: {
-        split: true
-    },
-    adapter: cloudflare()
+    adapter: cloudflare({
+        mode: 'directory',
+        functionPerRoute: true
+    })
})
Minor Changes

  • #​8188 cd2d7e769 Thanks @​ematipico! - Introduced the concept of feature map. A feature map is a list of features that are built-in in Astro, and an Adapter
    can tell Astro if it can support it.

    import { AstroIntegration } from './astro';

function myIntegration(): AstroIntegration {
  return {
    name: 'astro-awesome-list',
    // new feature map
    supportedAstroFeatures: {
      hybridOutput: 'experimental',
      staticOutput: 'stable',
      serverOutput: 'stable',
      assets: {
        supportKind: 'stable',
        isSharpCompatible: false,
        isSquooshCompatible: false,
      },
    },
  };
}
Patch Changes
withastro/astro (@​astrojs/netlify)

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

  • #​8188 7511a4980 Thanks @​ematipico! - When using an adapter that supports neither Squoosh or Sharp, Astro will now automatically use an image service that does not support processing, but still provides the other benefits of astro:assets such as enforcing alt, no CLS etc to users

  • #​8188 148e61d24 Thanks @​ematipico! - Reduced the amount of polyfills provided by Astro. Astro will no longer provide (no-op) polyfills for several web apis such as HTMLElement, Image or Document. If you need access to those APIs on the server, we recommend using more proper polyfills available on npm.

  • #​8029 2ee418e06 Thanks @​matthewp! - Remove the Netlify Edge adapter

    @astrojs/netlify/functions now supports Edge middleware, so a separate adapter for Edge itself (deploying your entire app to the edge) is no longer necessary. Please update your Astro config to reflect this change:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
- import netlify from '@​astrojs/netlify/edge';
+ import netlify from '@​astrojs/netlify/functions';

export default defineConfig({
 output: 'server',
 adapter: netlify({
+    edgeMiddleware: true
 }),
});

    This adapter had several known limitations and compatibility issues that prevented many people from using it in production. To reduce maintenance costs and because we have a better story with Serveless + Edge Middleware, we are removing the Edge adapter.

Minor Changes

  • #​8188 cd2d7e769 Thanks @​ematipico! - Introduced the concept of feature map. A feature map is a list of features that are built-in in Astro, and an Adapter
    can tell Astro if it can support it.

    import { AstroIntegration } from './astro';

function myIntegration(): AstroIntegration {
  return {
    name: 'astro-awesome-list',
    // new feature map
    supportedAstroFeatures: {
      hybridOutput: 'experimental',
      staticOutput: 'stable',
      serverOutput: 'stable',
      assets: {
        supportKind: 'stable',
        isSharpCompatible: false,
        isSquooshCompatible: false,
      },
    },
  };
}

  • #​8188 80f1494cd Thanks @​ematipico! - The build.split and build.excludeMiddleware configuration options are deprecated and have been replaced by options in the adapter config.

    If your config includes the build.excludeMiddleware option, replace it with edgeMiddleware in your adapter options:

    import { defineConfig } from "astro/config";
import netlify from "@​astrojs/netlify/functions";

export default defineConfig({
     build: {
-        excludeMiddleware: true
     },
     adapter: netlify({
+        edgeMiddleware: true
     }),
});

    If your config includes the build.split option, replace it with functionPerRoute in your adapter options:

    import { defineConfig } from "astro/config";
import netlify from "@​astrojs/netlify/functions";

export default defineConfig({
     build: {
-        split: true
     },
     adapter: netlify({
+        functionPerRoute: true
     }),
});
Patch Changes
withastro/astro (@​astrojs/node)

v6.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

  • #​8188 148e61d24 Thanks @​ematipico! - Reduced the amount of polyfills provided by Astro. Astro will no longer provide (no-op) polyfills for several web apis such as HTMLElement, Image or Document. If you need access to those APIs on the server, we recommend using more proper polyfills available on npm.

Minor Changes

  • #​8188 cd2d7e769 Thanks @​ematipico! - Introduced the concept of feature map. A feature map is a list of features that are built-in in Astro, and an Adapter
    can tell Astro if it can support it.

    import { AstroIntegration } from './astro';

function myIntegration(): AstroIntegration {
  return {
    name: 'astro-awesome-list',
    // new feature map
    supportedAstroFeatures: {
      hybridOutput: 'experimental',
      staticOutput: 'stable',
      serverOutput: 'stable',
      assets: {
        supportKind: 'stable',
        isSharpCompatible: false,
        isSquooshCompatible: false,
      },
    },
  };
}
Patch Changes
withastro/astro (@​astrojs/vercel)

v5.0.0

Compare Source

Major Changes

  • #​8445 91380378c Thanks @​Princesseuh! - Adds a configuration option devImageService to choose which of the built-in image services to use in development. Defaults to sharp.

  • #​8546 b79e11f3c Thanks @​matthewp! - Turn off functionPerRoute by default

    In the previous version of @astrojs/vercel, the default for functionPerRoute was changed to true. While this option has several advantages, if you're a free tier user you are likely to run into the limit of 12 functions per deployment. This will result in an error when you attempt to deploy.

    For this reason, the functionPerRoute option is now back to defaulting to false. It's still a useful option if you have a paid plan and have previously run into issues with your single function exceeding the size limits.

Minor Changes

  • #​8021 2e8726fee Thanks @​chriswdmr! - Enable Vercel Speed Insights and Vercel Web Analytics individually.
    Deprecates the analytics property in astro.config.mjs in favor of speedInsights and webAnalytics.

    If you're using the analytics property, you'll need to update your config to use the new properties:

    // astro.config.mjs
export default defineConfig({
	adapter: vercel({
-		analytics: true,
+		webAnalytics: {
+			enabled: true
+		},
+		speedInsights: {
+			enabled: true
+		}
	})
});

    Allow configuration of Web Analytics with all available configuration options.
    Bumps @​vercel/analytics package to the latest version.

Patch Changes

v4.0.5

Compare Source

Patch Changes

v4.0.4

Compare Source

Patch Changes

v4.0.3

Compare Source

Patch Changes

  • #​8348 5f2c55bb5 Thanks @​ematipico! - - Cache result during bundling, to speed up the process of multiple functions;

    • Avoid creating multiple symbolic links of the dependencies when building the project with functionPerRoute enabled;

  • #​8354 0eb09dbab Thanks @​Princesseuh! - Fix unnecessary warning about Sharp showing while building

  • Updated dependencies [d3a6f9f83, f21599671]:

    • astro@3.0.6

v4.0.2

Compare Source

Patch Changes

v4.0.1

Compare Source

Patch Changes

v4.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

  • #​8188 7511a4980 Thanks @​ematipico! - When using an adapter that supports neither Squoosh or Sharp, Astro will now automatically use an image service that does not support processing, but still provides the other benefits of astro:assets such as enforcing alt, no CLS etc to users

  • #​8015 9cc4e48e6 Thanks @​matthewp! - Remove the Vercel Edge adapter

    @astrojs/vercel/serverless now supports Edge middleware, so a separate adapter for Edge itself (deploying your entire app to the edge) is no longer necessary. Please update your Astro config to reflect this change:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
- import vercel from '@​astrojs/vercel/edge';
+ import vercel from '@​astrojs/vercel/serverless';

export default defineConfig({
 output: 'server',
 adapter: vercel({
+    edgeMiddleware: true
 }),
});

    This adapter had several known limitations and compatibility issues that prevented many people from using it in production. To reduce maintenance costs and because we have a better story with Serveless + Edge Middleware, we are removing the Edge adapter.

  • #​8239 52f0837bd Thanks @​matthewp! - Vercel adapter now defaults to functionPerRoute.

    With this change, @astrojs/vercel/serverless now splits each route into its own function. By doing this, the size of each function is reduced and startup time is faster.

    You can disable this option, which will cause the code to be bundled into a single function, by setting functionPerRoute to false.

  • #​8188 148e61d24 Thanks @​ematipico! - Reduced the amount of polyfills provided by Astro. Astro will no longer provide (no-op) polyfills for several web apis such as HTMLElement, Image or Document. If you need access to those APIs on the server, we recommend using more proper polyfills available on npm.

Minor Changes

  • #​8188 cd2d7e769 Thanks @​ematipico! - Introduced the concept of feature map. A feature map is a list of features that are built-in in Astro, and an Adapter
    can tell Astro if it can support it.

    import { AstroIntegration } from './astro';

function myIntegration(): AstroIntegration {
  return {
    name: 'astro-awesome-list',
    // new feature map
    supportedAstroFeatures: {
      hybridOutput: 'experimental',
      staticOutput: 'stable',
      serverOutput: 'stable',
      assets: {
        supportKind: 'stable',
        isSharpCompatible: false,
        isSquooshCompatible: false,
      },
    },
  };
}

  • #​8188 80f1494cd Thanks @​ematipico! - The build.split and build.excludeMiddleware configuration options are deprecated and have been replaced by options in the adapter config.

    If your config includes the build.excludeMiddleware option, replace it with edgeMiddleware in your adapter options:

    import { defineConfig } from "astro/config";
import vercel from "@​astrojs/vercel/serverless";

export default defineConfig({
     build: {
-        excludeMiddleware: true
     },
     adapter: vercel({
+        edgeMiddleware: true
     }),
});

    If your config includes the build.split option, replace it with functionPerRoute in your adapter options:

    import { defineConfig } from "astro/config";
import vercel from "@​astrojs/vercel/serverless";

export default defineConfig({
     build: {
-        split: true
     },
     adapter: vercel({
+        functionPerRoute: true
     }),
});
Patch Changes

Configuration

📅 Schedule: Branch creation - "every weekend on the 3rd week of the month" in timezone Europe/Berlin, 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.

@renovate
Copy link
Contributor Author

renovate bot commented Sep 10, 2023

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

  • Branch has one or more failed status checks

@shishkin shishkin mentioned this pull request Sep 10, 2023
Closed
@Robin-Wils
Copy link

Is there a way to help with this? Or should we just wait on more Astro 3 adoption?

Certain things in Astro 3 are not backwards compatible. The linked guide could help, but you likely have seen that one already. This is the only package that blocks me from upgrading at the moment. I understand the decision to not merge it yet, but Astro 3 also has many benefits.

https://docs.astro.build/en/guides/upgrade-to/v3/

@shishkin
Copy link
Owner

Thanks for asking @Robin-Wils. If you can look into the CI issues and help resolve them, it would really help. I don't have capacity to troubleshoot them now unfortunately.

Also, it would help to test the plugin setup logic on various adapters to see that the output directory is derived correctly.

@Robin-Wils
Copy link

I am not sure how to run this project yet, as I have not worked with creating integrations before. Maybe I find some time to look deeper into how to do that.

This might fix the pipeline:
Astro check is no longer included within astro, but requires a package. The build step may need npm install @astrojs/check.
https://docs.astro.build/en/guides/upgrade-to/v3/#moved-astro-check-now-requires-an-external-package

It might be good to wait for now. I saw some CSS issues in my project if I excluded this package. Astro 3 seems to have some minor issues. The upgrade guide is pretty straightforward. But it are quiet some changes. I am not sure how backwards compatible they are. It may make it hard to maintain lower versions of this package.

@renovate
Copy link
Contributor Author

renovate bot commented Sep 14, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

@shishkin shishkin merged commit 4442717 into main Sep 14, 2023
2 checks passed
@shishkin shishkin deleted the renovate/major-astro branch September 14, 2023 18:57
@github-actions
Copy link

🎉 This PR is included in version 1.2.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

@shishkin shishkin mentioned this pull request Sep 14, 2023
Closed
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
released
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@Robin-Wils @shishkin