Repository navigation
chore(deps): update astro - #501
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
vikunja-website | d67fed8 | Commit Preview URL Branch Preview URL |
Nov 20 2026, 02:41 AM |
renovate
Bot
force-pushed
the
renovate/astro
branch
from
November 18, 2026 19:50
1621e65 to
e480f70
Compare
renovate
Bot
force-pushed
the
renovate/astro
branch
from
November 20, 2026 02:37
e480f70 to
d67fed8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
14.4.8→14.4.97.3.9→7.3.1011.1.13→11.1.143.7.5→3.7.67.4.12→7.4.134.162.0→4.165.0Release Notes
withastro/astro (@astrojs/cloudflare)
v14.4.9Compare Source
Patch Changes
d116e3dThanks @astro-factory! - Fixes a spuriousNo environment found in configurationwarning for the prerender worker when building withCLOUDFLARE_ENVsetwithastro/astro (@astrojs/markdown-remark)
v7.3.10Compare Source
Patch Changes
387105bThanks @astro-factory! - FixesgetHeadings()andrender().headingsreporting{as${in Markdown heading text when using theunified()processorwithastro/astro (@astrojs/node)
v11.1.14Compare Source
Patch Changes
#18636
b4de3b5Thanks @umeraamir69! - Shares one processunhandledRejectionlistener across app handlers so standalone mode no longer treats in-request rejections as outside request context#18743
7c8dad5Thanks @EnesKartal! - AddsContent-Type: text/plain; charset=utf-8header to400responses for undecodable URLs in standalone mode.withastro/astro (@astrojs/sitemap)
v3.7.6Compare Source
Patch Changes
1dab71aThanks @Toyenzo! - Fixes i18n locale matching for pages whose first path segment is named like anObject.prototypeproperty, such as/constructor/or/toString/. These were treated as locales, producing invalid alternate links. Also rejects an i18ndefaultLocalethat is only an inherited object property rather than a configured locale.withastro/astro (astro)
v7.4.13Compare Source
Patch Changes
#18770
c850735Thanks @astro-factory! - Fixes the dev toolbar'sa11y-missing-contentaudit reporting anchors and headings that are hidden withvisibility: hiddenor are inside anaria-hidden="true"subtree#18536
d044365Thanks @KoenRijpstra! - Fixes server bundles including every renderable content collection entry when no server-rendered route callsrender()fromastro:content#18740
c7a2f1dThanks @astro-factory! - Fixesi18n.fallbackfailing withi18nNoLocaleFoundInPathwhen the fallback target is a locale defined with a custompath#18660
75ac226Thanks @NetBr3ak! - Fixes<Font preload>emitting no preload links when a requested weight range such as"400 700"sits inside a variable font file's range such as"400 900"#18758
273d7daThanks @astro-factory! - Fixesastro dev status,astro dev logs, and theastro previewequivalents treating a server started withASTRO_DEV_BACKGROUND=0orASTRO_PREVIEW_BACKGROUND=0as a background server#18658
33c931eThanks @hood! - Improves startup time of everyastrocommand for projects that don't configurefonts, by loading the font resolution dependencies only when fonts are used#18771
01c942dThanks @astro-factory! - Fixes the dev toolbar's audit fetchingloading="lazy"images again to measure them, which froze animated SVGs in Safari and downloaded images the page meant to load later#18711
bf5a170Thanks @astro-factory! - Fixes the dev server blocking cross-origin requests from an origin allowed by asecurity.allowedDomainsentry with a defaultport, such as{ hostname: 'staging.myapp.com', protocol: 'https', port: '443' }.BaseApp.validateForwardedHost()now applies the sameallowedDomainsrules as the rest of Astro.#18733
c6ab3c5Thanks @Marve10s! - Fixes hydration of framework components receiving sparse array props by serializing holes as undefinedUpdated dependencies [
c6ab3c5]:cloudflare/workers-sdk (wrangler)
v4.165.0Compare Source
Minor Changes
#10598
24bd3c3Thanks @Ehbraheem! - Add a new--forceflag tod1 migrations applywhich skips the interactive confirmation and applies any pending migrations non-interactively. This is useful for CI and automation.Usage example:
Fixes #5017
Patch Changes
#16019
8f26e90Thanks @penalosa! - Correct the dry-run setup message to say "exiting now" instead of "existing now".The previous wording contained a typo and appeared in Wrangler setup output and other consumers of shared autoconfig.
#17003
3595295Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-18Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#17003
3595295Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#16719
f833c8aThanks @jaeminbird! - Report.dev.varsand.envfiles that are not UTF-8 instead of silently loading no variablesBefore Wrangler would incorrectly read non UTF-8
.dev.varsand.envfiles as UTF-8. A.dev.varsfile that is not UTF-8 now stopswrangler devwith a message that says how to fix it, and a.envfile that is not UTF-8 is skipped with a warning. UTF-8 files, with or without a BOM, load as before.#14334
67d7c0aThanks @Divkix! - Replace the unmaintained asset hashing dependency withhash-wasmKeep asset hashes unchanged for Workers and Pages deployments and local Pages development while using a maintained WebAssembly implementation.
#16949
110c162Thanks @edmundhung! - Fail remote RPC binding requests on network errors instead of hangingRemote bindings that connect over RPC treated every network failure, such as being offline, a DNS or TLS error, as a preview reload. The request then waited silently for a reload that never came. These requests now fail with the error, while GET and HEAD requests interrupted by an actual reload are still retried.
#14578
6750663Thanks @penalosa! - Fix TypeScript errors when importing Wrangler's APIsProjects that import Wrangler's APIs, such as
getPlatformProxyordefineWranglerConfig, can now type-check withskipLibCheck: false. The published types no longer refer to missing internal packages, and their required type dependencies are installed automatically.Updated dependencies [
0a4315f,3595295,3595295,6750663,6750663,d04e667,6750663,5a6e450]:v4.164.0Compare Source
Minor Changes
#16450
5f05841Thanks @xortive! - Add custom CA and client certificate references to Workers VPC service TLS settingsWorkers VPC (open beta) service create and update commands accept
--certificate-authorityand--client-certificateUUIDs. Use either flag alone or both together. Whenever you supply either reference, explicitly choose--cert-verification-mode:verify_full: verify the origin certificate chain and hostname (the platform default).verify_ca: verify the chain but skip hostname verification, weakening origin identity checks.disabled: do not verify the origin certificate; this allows connections to impersonated origins and is unsafe for production.For HTTP services, these settings apply to HTTPS connections, not plaintext HTTP. TCP services can use them for upstream TLS, including PostgreSQL.
TLS settings are per-service only: host and resolver networks have no TLS settings or inheritance. Omitting TLS settings uses platform defaults (certificate chain and hostname verification). Explicit mode-only configuration, including
verify_full, is accepted. A custom CA cannot be combined withdisabled; a client certificate without a custom CA can.Upload certificates using the existing commands, then use the returned IDs below. Replace
<ca-uuid>,<client-uuid>,<tunnel-uuid>, and service IDs with your own values; certificate references must be valid UUIDs. Upload replacement certificates the same way before rotating their references.Create an HTTPS service with both a custom trust chain and an mTLS client certificate, or a PostgreSQL TCP service with only a custom CA:
For client-certificate-only configuration, use
--client-certificate <client-uuid> --cert-verification-mode verify_fullinstead of the certificate flags in either create command.Updates replace the complete service configuration, including TLS settings, in a single request, the same as
cf workers-vpc services update. Pass every TLS option the service should keep: certificate references and the verification mode that you omit are cleared, and an update without TLS options returns the service to the platform defaults. Removing a reference releases its backend certificate binding but does not delete the uploaded account certificate. For example, rotate the web service's client certificate while keeping its CA:To remove the CA while keeping the client certificate, repeat the update with only
--client-certificate <client-uuid>and a verification mode.Inspect the service's verification mode and CA/client certificate UUIDs (or
None), without exposing certificate or private-key contents:Patch Changes
#16974
77b5ca7Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-17Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16974
77b5ca7Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
Updated dependencies [
77b5ca7,77b5ca7,51064e6]:v4.163.0Compare Source
Minor Changes
#16917
d36b39dThanks @jamesopstad! - Write Build Output to.cloudflare/output/v1/and record the producervite buildand the experimentalwrangler build --experimental-cf-build-outputnow write Build Output v1, with account settings nested undersettingsin the rootconfig.json. They also record themselves as theproducer, so readers can name the tool that wrote the output in error messages. Previews from Build Output read the account settings from their new location.#16246
349fc4eThanks @leostera! - Start local Workflows from Artifacts eventsDeclare Artifacts events on
exports.workflow({ name, events })incloudflare.config.tsto start the owning Workflow locally incf, Vite, and Workers Vitest. Wrangler configurations continue to usetriggers.events. Native config conversion derives those targets from the Workflow export, andcf migrateattaches existing event subscriptions to their matching Workflow exports.Local Artifacts namespaces publish the documented
cf.artifacts.*messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions.Patch Changes
#16803
b219078Thanks @petebacondarwin! - Run experimental cf projects with their installed Vite or Vite+ commandscf dev,cf build, and deployments that build your project can use Vite or Vite+ even when no framework command is detected. This removes the need for the internalcf-vitedelegate and supports dependencies declared and hoisted at the root of a configured workspace. A workspace application using a custom-named Vite config should declare@cloudflare/vite-pluginin its own manifest, or addviteorvite-plusas a dependency or dev dependency to identify its tooling; this keeps shared root tools from selecting Vite for non-Vite siblings. Configs passed later via--configare evaluated by Vite when the command runs. Existing framework commands keep their priority. Consumers resolve bare executables using the detectednodeModulesPathsin order, adding.binto each directory. Lookup stops at the validated workspace root; standalone applications use only their ownnode_modules/.bin.Project inspection can recognize an existing Cloudflare configuration before dependencies are installed. Running a command provides guidance when the required tools are missing or the plugin version does not support cf profiles (
>=2.0.0-beta.v.13 <3). Vite evaluates the project configuration when the command runs, including dynamic configs and custom config files. Repair guidance uses the project’s detected package manager. Automatic setup asks users to convert CommonJS.cjsand.ctsVite configs to ESM imports and exports in.mjsor.mtsbefore adding the ESM-only Cloudflare plugin. Native builds also work with the Windows shell. Pages migration safeguards, unsupported-framework setup checks, and Wrangler command selection retain their existing behavior.#16944
db3c071Thanks @danlapid! - Stopwrangler devfrom missing config file changes made soon after a reloadwrangler devreplaced its config file watcher on every reload without waiting for the new one to start, so a change saved in that gap was never applied. It now keeps one watcher while the set of watched files is unchanged, and reports a config as applied only once its files are being watched. A second change saved within 50 ms of the previous one is no longer dropped either.#16920
81e56ddThanks @benbuzbee! - Use the effectivemax_instancesvalue when choosing the default container rollout stepsWhen
max_instanceswas omitted, Wrangler deployed 20 instances but chose rollout steps as if there were 0 instances, so the rollout used a single 100% step. Wrangler now uses[10, 100]for omittedmax_instances, while still using a single 100% step whenmax_instancesis 0 or 1.#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16946
e97c9f8Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#16874
4335eacThanks @petebacondarwin! - Avoid redundant OAuth refreshes after a sibling process updates credentialsCheck access-token expiry and select the refresh token from the same fresh credential snapshot. When a sibling has already saved a valid access token, reuse it without another exchange or write. This prevents an unnecessary rotation that can let an older response overwrite a newer refresh token.
#16917
d36b39dThanks @jamesopstad! - Detect Cloudflare Build Output of any version before deployingwrangler deploy,wrangler versions uploadandwrangler previewrefuse to run in a project that has Cloudflare Build Output, because that output belongs tocf. Detection now looks for any.cloudflare/output/v<N>/directory rather than only the root config of the current version, so output left by an older or newercfis still caught.Updated dependencies [
e97c9f8,e97c9f8,349fc4e,0bf81ac]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.