Workers DevProd

This commit executes a **versioning operation** across numerous packages, signifying a new release cycle for the project. It updates the `package.json` versions and `CHANGELOG.md` files for **core developer tools and libraries** such as `cli`, `wrangler`, `miniflare`, `create-cloudflare`, and `vitest-pool-workers`. As a standard **maintenance** step, all pending `.changeset` files were processed and removed, integrating their described changes into the respective package changelogs. This ensures that all recent developments and fixes are officially released and documented, making updated versions of these **critical components** available to users.

This commit performs **maintenance updates** to the **Workerd I/O subsystem**'s internal versioning and compatibility metadata. It updates the `src/workerd/io/maximum-compatibility-date.txt` file to `2026-04-07`, defining the latest compatibility date supported by `workerd`. Concurrently, the `src/workerd/io/release-version.txt` file is updated to `2026-03-31`, marking the current release version. This **chore** ensures `workerd` correctly identifies its own version and manages feature compatibility for upcoming deployments.

This commit performs a **maintenance update** by upgrading various project dependencies to their latest versions. It updates numerous **Rust crate dependencies**, including `zerocopy`, `capnp`, `itoa`, `uuid`, and `rustc-hash`, across the `deps/rust/crates` module, along with their associated Bazel build definitions. Additionally, the **CI/CD workflows** (`.github/workflows/*.yml`) are updated to utilize `opencode_version` 1.3.8. This comprehensive update ensures the project benefits from the latest features, bug fixes, and security patches provided by these updated libraries and tools, enhancing overall stability and performance.

This commit performs routine **maintenance** by updating the **`workerd` runtime's internal versioning and compatibility markers**. Specifically, it advances the **maximum compatibility date** in `src/workerd/io/maximum-compatibility-date.txt`, which dictates the oldest supported compatibility date for worker scripts and features. Concurrently, the `release-version.txt` file is updated to reflect the new **release version** of `2026-03-29`. This **release-related chore** ensures that the runtime correctly identifies its current version and manages compatibility behavior for deployed applications.

This commit performs **routine maintenance** by updating internal versioning metadata for the `workerd` I/O system. It advances the **maximum compatibility date** in `src/workerd/io/maximum-compatibility-date.txt` from 2026-04-03 to 2026-04-04. Additionally, the **release version date** in `src/workerd/io/release-version.txt` is updated from 2026-03-27 to 2026-03-28. This work is part of the standard **release preparation process**, ensuring that the project's internal dates reflect the current release cycle and are aligned for the 2026-03-28 release.

This commit performs a **routine versioning operation**, releasing new versions for several core packages including **`wrangler`**, **`miniflare`**, and **`create-cloudflare`**, as well as various utility libraries like `@cloudflare/vitest-pool-workers` and `@cloudflare/workers-utils`. As part of this **maintenance** task, it updates the `package.json` and `CHANGELOG.md` files for each affected package to reflect their new versions. The deletion of numerous `.changeset` files indicates that the previously staged features, bug fixes, and improvements described in those files have now been officially incorporated and released to users.

This commit performs essential **maintenance** by updating the **Workerd I/O system**'s release metadata. Specifically, it sets the `maximum-compatibility-date.txt` to `2026-03-27` and updates the `release-version.txt` to `2026-03-27`. This ensures that the Workerd runtime correctly reflects the current **release version** and establishes the new **maximum compatibility date** for future deployments. This is a standard part of the release process, impacting how Workerd handles versioning and compatibility for the `2026-03-27` release.

This commit performs essential **release preparation** for the 2026-03-26 release. It updates internal versioning and compatibility markers within the **Workerd I/O subsystem** by modifying `src/workerd/io/maximum-compatibility-date.txt` and `src/workerd/io/release-version.txt`. This **maintenance chore** ensures the `workerd` runtime correctly reflects the new **release version** and sets the official **maximum compatibility date**. This update is crucial for managing future feature rollouts and how compatibility flags are interpreted across the system.

This commit performs **routine maintenance** for the `workerd` runtime, specifically updating core release metadata within the **`workerd/io` subsystem**. It **advances the project's official release version to `2026-03-25`** by modifying `src/workerd/io/release-version.txt`. Concurrently, it updates the **maximum compatibility date** in `src/workerd/io/maximum-compatibility-date.txt`, establishing the new compatibility baseline for this release. This ensures accurate version reporting and defines the compatibility window for services running on the `workerd` platform.

This commit performs a **versioning release** for multiple packages within the monorepo. It updates the `package.json` and `CHANGELOG.md` files for **numerous packages**, including `wrangler`, `miniflare`, `create-cloudflare`, and various other development tools and libraries. This **maintenance** task consumes existing `.changeset` files to automatically increment package versions and generate comprehensive release notes. The primary impact is to make the latest features, bug fixes, and improvements available to users across these **core project components**.

This commit performs essential **release preparation** by updating internal metadata within the `workerd` project. It specifically updates the **maximum compatibility date** in `src/workerd/io/maximum-compatibility-date.txt` and the **release version number** in `src/workerd/io/release-version.txt`. This **maintenance** task ensures that the `workerd/io` subsystem's internal tracking reflects the new `2026-03-24` release. The update to the compatibility date is crucial as it defines the window for applications to remain compatible with the runtime.

This commit performs **maintenance updates** for the **Workerd I/O system** as part of the 2026-03-22 release. It updates the `src/workerd/io/release-version.txt` file to reflect the new official release version. Additionally, it sets the `src/workerd/io/maximum-compatibility-date.txt`, which dictates the highest compatibility date supported by this release. This ensures that the runtime correctly identifies its version and enforces compatibility rules for deployed services.

This commit performs **routine maintenance** for the 2026-03-21 release of Workerd. It updates the **Workerd I/O subsystem's** maximum compatibility date, extending it from `2026-03-27` to `2026-03-28` within `src/workerd/io/maximum-compatibility-date.txt`. Concurrently, the current release version is incremented from `2026-03-20` to `2026-03-21` in `src/workerd/io/release-version.txt`. This ensures that **Workerd applications** can continue to operate with the latest compatibility settings and accurately reflects the project's current release status.

This commit performs an **automated versioning update** across numerous packages, including **`wrangler`**, **`miniflare`**, `containers-shared`, `local-explorer-ui`, `pages-shared`, `unenv-preset`, `vite-plugin-cloudflare`, `vitest-pool-workers`, `workers-utils`, and `workflows-shared`. It **bumps the version numbers** in their respective `package.json` files and **updates their `CHANGELOG.md` files** to reflect all accumulated changes. This **maintenance task** prepares these core modules for a new release, incorporating various features, bug fixes, and chores documented in the individual `.changeset` files.

This commit performs **maintenance** by updating the **`workerd` runtime's release metadata** as part of the `2026-03-20` release cycle. It updates the official **release version** to `2026-03-20` within `src/workerd/io/release-version.txt`. Concurrently, the **maximum compatibility date** is also set to `2026-03-20` in `src/workerd/io/maximum-compatibility-date.txt`. This ensures the runtime correctly reflects its current version and establishes the compatibility baseline for future deployments and feature rollouts.

This commit performs **routine maintenance** to update the **release metadata** for the `workerd` project. It increments the **release version** to `2026-03-19` in `src/workerd/io/release-version.txt` and extends the **maximum compatibility date** to `2026-03-26` in `src/workerd/io/maximum-compatibility-date.txt`. This **maintenance chore** ensures that internal versioning and the compatibility window are correctly aligned with the latest release, potentially affecting how older Workers interact with the system.

This commit performs **maintenance updates** for the **`workerd` project's release process**. It specifically updates the **`workerd/io`** subsystem by setting the current release version to `2026-03-18` in `release-version.txt`. Concurrently, it adjusts the maximum supported compatibility date to `2026-03-18` in `maximum-compatibility-date.txt`. This **chore** ensures that the system correctly reflects the latest official release and its associated compatibility baseline, impacting how `workerd` identifies its own version and supported features.

This commit performs a **routine package versioning and release preparation** across multiple internal packages. It **updates the versions** for `chrome-devtools-patches`, `create-cloudflare`, `miniflare`, `pages-shared`, `vite-plugin-cloudflare`, `vitest-pool-workers`, and `wrangler`. This **maintenance chore** involves updating the `version` field in each package's `package.json` and generating corresponding entries in their `CHANGELOG.md` files. The addition of several `.changeset/*.md` files indicates the specific changes that are being bundled and released, ensuring proper tracking and communication of updates to consumers of these packages.

This commit performs **routine maintenance** to update the project's release metadata within the **`workerd/io` subsystem**. It advances the **official release version** from `2026-03-16` to `2026-03-17` in `src/workerd/io/release-version.txt`. Concurrently, the **maximum compatibility date** is extended by one day, from `2026-03-23` to `2026-03-24`, as recorded in `src/workerd/io/maximum-compatibility-date.txt`. This ensures that the project's current version and its **backward compatibility window** are accurately reflected for the new release.

This commit performs a **routine maintenance update** by upgrading numerous **Rust dependencies** to their latest available versions. It specifically modifies the Bazel build configurations within the `deps/rust/crates/` directory for a wide array of crates, including `clap`, `swc_common`, `wasm-bindgen`, and `capnp` related libraries. This **dependency management** effort ensures the project benefits from the latest features, performance enhancements, and security patches provided by these upstream libraries. The update primarily impacts the **internal build system** and the underlying libraries used by the project's Rust components, aiming to keep the codebase current and robust.