Daniel Walsh

This commit **fixes** a **bug** in the `workerd` runtime where the `cloudflare.ray_id` was incorrectly captured for **subrequests**, leading to inaccurate tracing. Previously, the `ray_id` was mistakenly derived from the *request* `cf-ray` header and only when a request body was present. The change in `src/workerd/api/http.c++` now correctly extracts the `cloudflare.ray_id` from the *response* headers, ensuring it is **always set properly** on the trace span for all subrequests. This significantly improves the **observability and tracing** of subrequests by providing the correct Cloudflare Ray ID, with new **test cases** added to validate this behavior.

This commit **re-fixes an incorrect URL** for the **Dynamic Workers starter template** across multiple documentation pages. It updates the external link within the `src/content/docs/dynamic-workers/examples/dynamic-workers-starter.mdx` example, the `src/content/docs/dynamic-workers/getting-started.mdx` guide, and the `src/content/changelog/workers/2026-03-24-dynamic-workers-open-beta.mdx` changelog entry. This **documentation fix** ensures that users are correctly directed to the starter template, significantly improving the onboarding experience for the **Dynamic Workers** feature by preventing broken links.

This commit introduces a **new capability** to **Wrangler**, enabling **Cloudflare Access Service Token support** for **CI/non-interactive environments**. It allows `wrangler` to authenticate with Access-protected resources using `CLOUDFLARE_ACCESS_CLIENT_ID` and `CLOUDFLARE_ACCESS_CLIENT_SECRET` environment variables, eliminating the need for interactive login in automated workflows. The **authentication system** has been **refactored** in `packages/wrangler/src/user/access.ts` and `packages/wrangler/src/user/auth-variables.ts` to prioritize these service tokens, with new functions like `getAccessHeaders` and `getCloudflareAccessHeaders` handling the retrieval and application of access headers. This change significantly enhances **CI/CD integration** for Workers that interact with Access, ensuring seamless operation in automated deployment and development pipelines. Extensive **testing** was added to cover service token authentication, non-interactive error handling, and interactive environment fallbacks.

This commit **updates the documentation** for the **Workers runtime API**, specifically the `waitUntil` function within `src/content/docs/workers/runtime-apis/context.mdx`. It now explicitly **cautions developers about the 30-second execution limit** for `waitUntil`, which is crucial for understanding its behavior. Furthermore, the update **recommends using Queues** as an alternative for tasks that require guaranteed completion beyond this time constraint, thereby improving developer guidance and preventing potential issues in **Workers applications**.

This is an isolated refactor within `workerd`'s I/O context to improve a cancellation message. It has no functional impact on users or other systems, primarily enhancing clarity for debugging.

This commit introduces a **new feature** to the **sitemap generation** process within the **Astro configuration**, specifically enhancing how `lastmod` dates are determined. It now dynamically sets the sitemap's `lastmod` date by retrieving the **last Git modification date** of the corresponding source file. This logic, implemented in `astro.config.ts` and utilizing functions like `getGitLastModified` and `urlToFilePath`, ensures more accurate and up-to-date sitemap information. If Git modification data is unavailable, the system gracefully falls back to using the current date for the `lastmod` entry. This **enhancement** improves the overall quality and SEO relevance of the generated sitemaps by providing more precise content freshness indicators.

This commit introduces a **new capability** to the **Wrangler configuration generation** process by adding the `$schema` property to the generated JSON output. Specifically, the `src/components/WranglerConfig.astro` component now ensures that when TOML configurations are converted, the resulting `wrangler.jsonc` includes the schema reference. This **enhancement** significantly improves the **developer experience** by enabling **JSON Schema validation** and providing robust **IDE auto-completion** for configuration files, making them easier to author and validate.

This commit addresses a **documentation formatting error** within the **account permissions table**. It specifically **corrects the layout** of the table in `src/content/partials/fundamentals/account-permissions-table.mdx` by removing an extraneous column header and an incorrectly placed cell. This **maintenance fix** ensures the **user-facing documentation** accurately and clearly presents account permission details. The change improves the readability and comprehension of the **account permissions** section for users.

This commit **updates the documentation** for **Workers runtime API rate limit bindings**, specifically within the `src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx` file. It performs a **documentation maintenance** task by revising the minimum required **Wrangler CLI version** from `3.45.0` to `4.36.0`. This ensures that users following the guide for implementing rate limit bindings are provided with the most current and accurate tool version, preventing potential setup or compatibility issues due to outdated information.

This commit introduces a **new feature** that enables the system to render Markdown content dynamically based on client preferences. It **enhances content negotiation** by modifying the **markdown rendering middleware** and the **worker's rendering logic** to recognize and respond to an `Accept: text/markdown` HTTP header. Specifically, the `onRequest` function in `src/middleware/index.ts` and the `fetch` logic within `worker/index.ts` are updated to incorporate this new condition. This change provides greater flexibility for clients to explicitly request Markdown output, improving API adaptability for various content consumers.

This commit **refactors** the **rate limiting** subsystem by removing the `type` field from the mechanism responsible for binding rate limits. The removal of this field streamlines the configuration and application of rate limits, ensuring a more **proper and simplified binding process**. This change likely addresses redundancy or unnecessary complexity in how rate limits are defined, improving the overall clarity and robustness of the rate limiter's internal logic.

This commit **disables tracing** for the project by modifying the `wrangler.toml` configuration file. Specifically, it sets the `enabled` flag to `false` within the `observability.traces` section, affecting the **observability** subsystem. This **configuration change** is a **maintenance task** that will prevent the collection and reporting of trace data, potentially reducing overhead but also impacting debugging and monitoring capabilities.

This commit provides a **documentation update** for **Cloudflare Workers**, reflecting a significant **increase in static asset limits**. It introduces a new `changelog` entry to formally announce this enhancement and updates the `platform limits` documentation (`src/content/docs/workers/platform/limits.mdx`) with the new values. The updated documentation also includes crucial information regarding required `Wrangler` versions for users to fully utilize these expanded capabilities. This ensures users are well-informed about the **platform's enhanced capacity**.

This change increases the maximum asset count allowed for deployment via Wrangler to 100,000, directly impacting users with large asset bundles. While currently a hardcoded limit, it provides a new capability for asset-heavy projects.

This commit **updates the documentation** for **Cloudflare Pages** to clarify the essential DNS requirements for **custom branch aliases**. It explicitly states that these aliases necessitate a **proxied Cloudflare DNS record** for proper functionality. The updated content in `src/content/docs/pages/how-to/custom-branch-aliases.mdx` also explains the expected behavior when DNS records are unproxied or managed externally. This **documentation improvement** aims to prevent user configuration errors and enhance the user experience when setting up custom domains for Pages branches.

This commit **updates the documentation** for **Workers configuration previews** to reflect a significant increase in the **retained alias limit**. Specifically, the maximum number of aliases that can be retained has been raised from 20 to 1000. This **documentation update** ensures that users are aware of the expanded capacity, providing accurate information regarding the system's current capabilities for managing aliases within the `previews.mdx` file.

This commit **updates the documentation** for the **Cloudflare China Network**, specifically enhancing the `src/content/docs/china-network/reference/available-products.mdx` file. It **expands the table of available developer services**, adding more products and their current availability status within the China Network, along with explanatory footnotes. This **documentation update** provides clearer and more comprehensive information for users, helping them understand the supported developer platform offerings and their regional availability.

This commit **updates the documentation** for **Workers platform limits** to provide crucial clarification regarding static asset management. It explicitly states that the static asset file limit is applied **per Worker version**, rather than globally or per account. This **documentation improvement** ensures users have an accurate understanding of resource constraints when deploying Workers. The change in `src/content/docs/workers/platform/limits.mdx` helps prevent potential misunderstandings about how asset counts are calculated and enforced.

This commit implements a **bug fix** by correcting an invalid URL within the **documentation** for **Cloudflare 1015 errors**. Specifically, it updates the link to the **Workers documentation** on the `error-1015.mdx` page by adding a necessary trailing slash. This **maintenance** change ensures that users encountering a 1015 error can correctly navigate to the relevant Workers help resources, significantly improving the user experience and the accuracy of the support documentation.

This commit provides a crucial **documentation update** for **Workers previews**, clarifying a significant operational detail. It adds a new bullet point to `src/content/docs/workers/configuration/previews.mdx`, explicitly stating that logs are not available for Preview URLs. This **maintenance work** enhances the accuracy and completeness of the **Workers configuration** guide, preventing potential user confusion or wasted effort when debugging preview environments. The change directly impacts users relying on the documentation for understanding **Workers preview** capabilities and limitations.