This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
(Full documentation to help you migrate your project to the upgraded Cloudflare adapter will be provided with the release of v10.0.)
Deprecates the following adapter configuration options (to be removed entirely in v10):
mode: All projects will deploy to Cloudflare pages using advanced mode (the previous default setting). This is no longer a configurable option. Cloudflare Functions will no longer be supported. If you were using mode: 'directory', please migrate to Astro Endpoints.
functionPerRoute: Discontinued due to Cloudflare's single execution context approach. You will no longer have the option to compile a separate bundle for each page.
routes.strategy: Projects will use the auto-generated _route.json for route management unless you provide your own public/_routes.json. This change aims to eliminate confusion and promote consistency.
routes.include: Will be replaced by a new routes.extend.include option to allow you to include additional routes.
routes.exclude: Will be replaced by a new routes.extend.exclude option to allow you to exclude additional routes.
runtime: Local runtime bindings will be configured in wrangler.toml at the root of your project as described in the adapters documentation. You will no longer configure these directly in the adapter configuration. A new platformProxy setting will be introduced to enable and configure the platformProxy (local runtime) provided by wrangler.
These changes are part of ongoing efforts to streamline functionality, improve performance, and align with best practices and platform capabilities.
We strongly recommend upgrading to v10 upon its release. To ensure a smooth migration, we commit to at least 4 weeks of additional maintenance for v9 following the release of v10. During this period, we will actively assist with migration efforts to ensure that all users can transition without major issues.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@astrojs/cloudflare@9.2.0
Minor Changes
#192
256b7024624ab45d5087d774cb4c30b117f1636a
Thanks @alexanderniebuhr! - Prepares for major breaking changes to adapter configuration in the upcoming v10 release.(Full documentation to help you migrate your project to the upgraded Cloudflare adapter will be provided with the release of v10.0.)
Deprecates the following adapter configuration options (to be removed entirely in v10):
mode
: All projects will deploy to Cloudflare pages using advanced mode (the previous default setting). This is no longer a configurable option. Cloudflare Functions will no longer be supported. If you were usingmode: 'directory'
, please migrate to Astro Endpoints.functionPerRoute
: Discontinued due to Cloudflare's single execution context approach. You will no longer have the option to compile a separate bundle for each page.routes.strategy
: Projects will use the auto-generated_route.json
for route management unless you provide your ownpublic/_routes.json
. This change aims to eliminate confusion and promote consistency.routes.include
: Will be replaced by a newroutes.extend.include
option to allow you to include additional routes.routes.exclude
: Will be replaced by a newroutes.extend.exclude
option to allow you to exclude additional routes.runtime
: Local runtime bindings will be configured inwrangler.toml
at the root of your project as described in the adapters documentation. You will no longer configure these directly in the adapter configuration. A newplatformProxy
setting will be introduced to enable and configure the platformProxy (local runtime) provided by wrangler.These changes are part of ongoing efforts to streamline functionality, improve performance, and align with best practices and platform capabilities.
We strongly recommend upgrading to v10 upon its release. To ensure a smooth migration, we commit to at least 4 weeks of additional maintenance for v9 following the release of v10. During this period, we will actively assist with migration efforts to ensure that all users can transition without major issues.