Update dependency @astrojs/cloudflare to v9.2.0 #79
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/astrojs-cloudflare-9.x-lockfile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
9.1.0
->9.2.0
Release Notes
withastro/adapters (@astrojs/cloudflare)
v9.2.0
Compare Source
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.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR has been generated by Renovate Bot.