tewaro

This commit introduces a **new capability** to **Workerd's JavaScript API** by adding a `ctx.cache` object with a `purge` method, enabling **cache-enabled workers** to programmatically clear their caches. It establishes the necessary **API infrastructure** within the `ExecutionContext` and `Worker::Api` interface, including new types like `CachePurgeError` and `CachePurgeResult`. While the default implementation is a stub, returning `kj::none` for `ctx.cache` when not explicitly overridden, this **API extension** provides the foundation for embedding applications to supply concrete cache purging functionality. The change also updates **TypeScript type definitions** for `experimental` and `latest` snapshots to expose this new `CacheContext` and its associated purge methods.

This commit introduces a **new capability** by extending the **`ThreadContext::HeaderIdBundle`** within the `workerd/io` module. It adds an `origin` member of type `kj::HttpHeaderId` to the `HeaderIdBundle` struct and initializes it, enabling the system to explicitly track and manage the **`Origin` HTTP header** internally. This enhancement prepares the `ThreadContext` for more robust handling of origin-related logic, potentially for security, CORS, or other HTTP request processing within `workerd`. The change is primarily for **internal use**, improving the framework's ability to access and utilize this critical header.

This commit introduces a **new capability** to facilitate **HTTP header identification and retrieval** across the C++ and Rust FFI boundary within the **`kj` library**. It defines `HttpHeaderId` as an opaque type, enabling C++ code to pass these identifiers to Rust and receive corresponding header values back. Specifically, the FFI layer now includes a C++ function `get_header_by_id` that leverages Rust's `get_by_id` implementation for `HttpHeadersRef` to fetch header values. This establishes a robust **C++ to Rust to C++ pass-through mechanism** for `HttpHeaderId`, significantly enhancing interoperability for HTTP header management. Comprehensive tests have been added in both C++ and Rust to validate this round-trip functionality.

Isolated style change to `src/workerd/io/worker.h`; no functional impact on Workerd's I/O worker.

This revert removes recent changes to the `workerd` runtime's queue API and I/O context, effectively rolling back the introduction of more detailed queue binding error information. Any systems expecting enhanced error reporting for queue bindings will now experience the previous behavior.

This is an isolated, preparatory change to Workerd's Node.js crypto API, adding necessary headers for an upcoming `ncrypto` update. It has no immediate production impact.

This is an isolated internal refactoring within `workerd`'s filesystem API, removing an `Rc Ref`. It has no user-facing impact or functional changes.

This commit reapplies an internal maintenance fix to the `workerd` JavaScript engine's V8 integration, specifically to avoid warnings related to external allocated memory. It is an isolated internal change with no impact on external functionality or user-facing features.

This commit reverts a previous change related to V8 external memory allocation, resolving a build issue in `workerd`. It's a temporary fix to unblock the `workerd` build process, reintroducing a warning that was previously addressed.

This is an isolated, internal maintenance change within Workerd's V8 integration, updating the usage of deprecated V8 APIs with current tag-based mechanisms. It has no direct impact on external functionality or user-facing behavior.

This commit fixes a resource consumption issue in the `workerd` JSON parameter extractor tool, enabling it to handle large Clang ASTs more efficiently. This is an internal tool improvement with no direct production impact.

This commit fixes a critical issue in `workerd`'s internal HTTP client, enabling proper websocket functionality by adding a necessary entropy source. This ensures that services relying on `newInternalHttpClient` for websockets will now operate as expected.

This commit introduces an experimental `cache: reload` capability to `workerd`'s HTTP API. This is a new feature that is not yet stable and likely requires explicit opt-in, with no immediate impact on existing production systems.

This commit simplifies `workerd`'s JavaScript setup by removing an obsolete V8 version check. This is an internal cleanup, reflecting an updated dependency, with no user-facing impact.

This commit updates the core V8 JavaScript engine to version 14.0.345.4, affecting all systems that embed or interact with V8. This is a significant dependency upgrade that introduces new V8 capabilities, build system improvements, and potential performance changes, requiring thorough testing for compatibility and to leverage new features.

This commit fixes a bug in `workerd`'s core HTTP and socket handling, allowing for proper processing of multiple fetches and ensuring all data is read during HTTP redirects. This improves the reliability and correctness of HTTP requests within the runtime.

This commit fixes a bug in the `workerd` sockets API, preventing interference from previous protocol data during `socket2fetcher` conversions. This ensures the robust and correct operation of socket-to-fetcher functionality within the `workerd` runtime.

This foundational update to the V8 JavaScript engine within `workerd` could introduce new JavaScript features and performance improvements, potentially affecting all JavaScript execution environments.

This commit **adds comprehensive documentation** for the newly supported `cache: no-cache` option within **Cloudflare Workers** subrequests. It includes a **changelog entry**, details for the `cache_no_cache_enabled` **compatibility flag**, and updates to the `fetch` API and `Request` interface documentation to reflect this new caching mode. The `cache-using-fetch` example is also updated to demonstrate its usage, providing developers with clear guidance on how to leverage `no-cache` for more granular control over caching behavior in their Worker applications. This **documentation update** supports a **feature release** that enhances the clarity and usability of the Workers platform.

This commit adds new test coverage for `starttls` functionality within the `workerd` API, specifically for Node.js and Cloudflare sockets. It is an isolated change to the test suite with no direct impact on production code or user-facing features.