docs: add Rstest 0.11 release blog

website/AGENTS.md

@@ -14,34 +14,38 @@ This is the documentation website for Rstest, built with [Rspress](https://rspre
 pnpm dev      # Start dev server
 pnpm build    # Build for production
 pnpm preview  # Preview production build
-pnpm gen:og   # Generate a release Open Graph image (see below)
+pnpm gen:release-image  # Generate a release's banner + og image (see below)
 ```
 
-## Open Graph image generation
+## Release image generation
 
-Per-release og images live in [rstackjs/rstack-design-resources](https://github.com/rstackjs/rstack-design-resources) and are served by the `assets.rspack.rs` CDN. The template lives **in this repo** to keep design-resources as a passive PNG store.
+Each release blog needs **two** images, generated together so they share one gradient:
 
-- `scripts/og-image/cli.mts` — entry, parses `--version`/`--description`/`--out`
-- `scripts/og-image/render.mts` — fetches the Rstest logo SVG → rasterizes → composes with [satori](https://github.com/vercel/satori) → renders with [@resvg/resvg-js](https://github.com/yisibl/resvg-js) at 2x zoom for retina
-- `scripts/og-image/template.mts` — [satori-html](https://github.com/natemoo-re/satori-html) template, modeled after the `Rsbuild og image 1.0` artboard in design-resources
+- **banner** — `4096x1152`, no tagline, the in-page `<img>` at the top of the post. Committed to `docs/public/` and referenced by a site-relative path (`/rstest-banner-v<ver>.png`).
+- **og image** — `2400x1260`, optional tagline, the social-share card. Committed to [rstackjs/rstack-design-resources](https://github.com/rstackjs/rstack-design-resources) under `rstest/` and served by the `assets.rspack.rs` CDN. `rspress.config.ts` wires `og:image` per blog route: `blog/announcing-<major>-<minor>` → `assets.rspack.rs/rstest/rstest-og-image-v<major>-<minor>.png`.
+
+The templates live **in this repo**; design-resources stays a passive PNG store.
+
+- `scripts/release-image/cli.mts` — entry, parses `--version`/`--description`/`--out-dir`; rolls one background and renders both images
+- `scripts/release-image/render.mts` — fetches the Rstest logo SVG → rasterizes → composes with [satori](https://github.com/vercel/satori) → renders with [@resvg/resvg-js](https://github.com/yisibl/resvg-js) at 2x zoom for retina; `randomBackground()` re-rolls the gradient every run (no seed flag)
+- `scripts/release-image/template.mts` — [satori-html](https://github.com/natemoo-re/satori-html) template driven by the `LAYOUTS.banner` / `LAYOUTS.og` presets
 
 ### Release workflow
 
-1. Run `pnpm gen:og --version <ver> --description "<tagline>"` from `website/`. Use `--out` to write directly into a local clone of the design-resources repo at `rstest/assets/rstest-og-image-v{version-with-hyphens}.png` (e.g. `v0-5.png`). The background gradient is randomized (color scheme, blob count, placement) on every run and there is no seed flag — re-run until you get a composition you like before committing.
-2. Commit the PNG in the design-resources repo and open a PR — that repo is the only place release PNGs are stored.
-3. After CDN deploy, the PNG is reachable at `assets.rspack.rs/rstest/assets/rstest-og-image-v0-5.png`. Wiring it up per blog `routePath` in `rspress.config.ts` is a separate follow-up — the site currently sets a single static `og:image` via `pluginOpenGraph`.
+1. Run `pnpm gen:release-image --version <ver> [--description "<tagline>"] --out-dir <dir>` from `website/`. The gradient is randomized every run — re-run until both images look good.
+2. Compress both PNGs with [TinyPNG](https://tinypng.com) (or Squoosh / ImageOptim / `pngquant`) — the raw resvg output is ~200 KB and palette quantization typically drops it to ~1/4 the size with no visible loss.
+3. Put the banner in `docs/public/`. Commit the og image to the design-resources repo under `rstest/` and open a PR — that repo is the only place og images are stored. After CDN deploy it is reachable at `assets.rspack.rs/rstest/rstest-og-image-v<ver>.png`.
 
 ### Do
 
-- Use Space Grotesk (committed under `scripts/og-image/assets/fonts/` with SIL OFL license)
+- Use Space Grotesk (committed under `scripts/release-image/assets/fonts/` with SIL OFL license)
 - Render at 2x via `Resvg({ fitTo: { mode: 'zoom', value: 2 } })` so the PNG stays crisp on retina displays
-- Before committing the PNG to design-resources, run it through [TinyPNG](https://tinypng.com) (or Squoosh / ImageOptim / `pngquant`) — the raw resvg output is ~300 KB and palette quantization typically drops it to ~1/4 the size with no visible loss
 - Fetch the logo from the canonical CDN URL at generation time, not from a committed copy
 
 ### Don't
 
 - Don't depend on packages like `geist` that pull in framework peer deps (`next>=13.2`); commit raw `.ttf` files directly instead
-- Don't write generated PNGs into this repo; they belong in design-resources
+- Don't commit og images into this repo; they belong in design-resources (the banner is the one exception — it lives in `docs/public/`)
 - Don't bake the logo into a static asset; always fetch the SVG so logo updates propagate automatically
 
 ## Writing style guidelines

website/README.md

@@ -16,6 +16,6 @@ For images you use in the document, it's better to upload them to the [rstackjs/
 
 After you upload the images there, they will be automatically deployed under the <https://assets.rspack.rs/>.
 
-## Open Graph images
+## Release images
 
-`scripts/og-image/` generates per-release Open Graph images used by the `og:image` and `twitter:image` meta tags on each release blog post. See [AGENTS.md](./AGENTS.md#open-graph-image-generation) for the template architecture and release workflow.
+`scripts/release-image/` generates each release's banner and Open Graph image (the latter used by the `og:image` / `twitter:image` meta tags on the release blog post). See [AGENTS.md](./AGENTS.md#release-image-generation) for the template architecture and release workflow.

website/docs/en/api/runtime-api/rstest/fake-timers.mdx

@@ -167,7 +167,7 @@ Advances the timers to the next animation frame.
 
 ## rs.jumpTimersByTime
 
-<ApiMeta addedVersion="0.10.7" />
+<ApiMeta addedVersion="0.11.0" />
 
 - **Alias:** `rstest.jumpTimersByTime`
 - **Type:** `(ms: number | string | Temporal.Duration) => RstestUtilities`
@@ -187,7 +187,7 @@ expect(cb).toHaveBeenCalledTimes(1);
 
 ## rs.setTickMode
 
-<ApiMeta addedVersion="0.10.7" />
+<ApiMeta addedVersion="0.11.0" />
 
 - **Alias:** `rstest.setTickMode`
 - **Type:** `(mode: { mode: 'manual' | 'nextAsync' } | { mode: 'interval'; delta?: number }) => RstestUtilities`

website/docs/en/blog/_meta.json

@@ -1 +1 @@
-["index", "announcing-0-10"]
+["index", "announcing-0-11", "announcing-0-10"]

website/docs/en/blog/announcing-0-11.mdx

@@ -0,0 +1,136 @@
+---
+description: 'Rstest 0.11 is a transitional release on the way to 1.0: it breaks and settles the test options, mock, pool, and shard APIs, and also makes V8 coverage faster and aligns fake timers with the latest @sinonjs/fake-timers.'
+date: 2026-07-06 16:00:00
+sidebar: false
+authors:
+  - name: 9aoy
+    avatar: 'https://github.com/9aoy.png'
+    github: '9aoy'
+  - name: fi3ework
+    avatar: 'https://github.com/fi3ework.png'
+    github: 'fi3ework'
+---
+
+import { BlogAuthors } from '@rstack-dev/doc-ui/blog-authors';
+
+# Announcing Rstest 0.11
+
+_July 6, 2026_
+
+<BlogAuthors />
+
+<img
+  src="https://assets.rspack.rs/rstest/rstest-banner-v0-11.png"
+  alt="Rstest 0.11"
+  style={{
+    boxShadow: '0 2px 6px rgba(0, 0, 0, 0.08)',
+  }}
+/>
+
+Rstest 0.11 is a transitional release on the road to 1.0. Its focus is to settle several public APIs through breaking changes ahead of the stable release; alongside that, it also brings faster V8 coverage and updated fake timers.
+
+Notable changes:
+
+- [API changes on the road to 1.0](#api-changes)
+- [Faster V8 coverage](#coverage-v8)
+- [Fake timers aligned with `@sinonjs/fake-timers` 15](#fake-timers)
+- [Other improvements](#other-improvements)
+
+## API changes on the road to 1.0 \{#api-changes}
+
+To stabilize the public API before 1.0, Rstest 0.11 adjusts a few surfaces. These are breaking changes, but the migrations are straightforward.
+
+### `TestOptions` moves to the second argument
+
+The [`TestOptions`](/api/runtime-api/test-api/test#testoptions) object (`retry` / `repeats` / `timeout`) for `test` / `it` / `test.each` / `test.for` was previously accepted as the **last** argument, after the test function. With a long test body it was easy to miss, and formatters tended to push it onto a separate trailing line. It now goes in the **second** position, before the test function, matching the shape used by Vitest and Node.js' built-in test runner (`node:test`).
+
+```diff
+- test('name', () => {}, { retry: 2 });
++ test('name', { retry: 2 }, () => {});
+```
+
+The numeric timeout shorthand is unchanged — the Jest-style `test('name', fn, 1000)` still works as the last argument. `describe` now accepts a `TestOptions` object in the same second-argument position.
+
+### Mock factories are synchronous-only
+
+The `rs.mock` / `rs.doMock` factory type is now synchronous-only. Async factories are prone to hoisting and module-initialization issues, so TypeScript no longer suggests them. For partial mocks, keep the real module via a synchronous `importActual` import attribute and override only the exports you need:
+
+```ts
+import * as actual from './date-utils' with { rstest: 'importActual' };
+
+rs.mock('./date-utils', () => ({
+  ...actual,
+  formatDate: rs.fn().mockReturnValue('2026-03-19'),
+}));
+```
+
+See [Partially mock modules](/guide/basic/mock#partially-mock-modules) for more details.
+
+### `pool.minWorkers` is removed
+
+`pool.minWorkers` set a floor on retained idle workers, but it only applied under `isolate: false` — the default `isolate: true` never reuses workers, so the option had no effect. It is removed so that `pool` settles on the flat `{ type?, maxWorkers?, execArgv? }` shape; use `pool.maxWorkers` to control file-level parallelism. The internal floor still defaults to `min(maxWorkers, recommended)`, so default warm-worker behavior is unchanged.
+
+### `shard` is CLI-only
+
+Sharding is inherently per-invocation — every CI runner passes a different index, which a value committed to a shared config file cannot express. The `shard` config field is removed from `RstestConfig`; use the [`--shard <index>/<count>`](/guide/basic/cli#sharding-tests) CLI flag instead. The flag and its behavior are unchanged.
+
+```bash
+npx rstest run --shard=1/3
+```
+
+## Faster V8 coverage \{#coverage-v8}
+
+On a large bundled project, collecting V8 coverage could spend tens of seconds turning raw V8 data into Istanbul coverage. Rstest 0.11 reworks the conversion path.
+
+Previously, the provider ran every raw V8 entry through the generic `ast-v8-to-istanbul` converter, including many that never reach the final report. Rstest 0.11 uses a converter tailored for Rstest's output, filters out irrelevant entries before converting, and moves the conversion from each worker into the main process.
+
+Measured on the [Rsbuild](https://github.com/web-infra-dev/rsbuild) repository's own test suite (`pnpm test --coverage --coverage.provider=v8`):
+
+| Version                         | Wall span | Phase sum |
+| ------------------------------- | --------: | --------: |
+| baseline (`ast-v8-to-istanbul`) |     6.05s |    60.11s |
+| Rstest 0.11                     |     1.81s |    10.28s |
+
+Compared with the baseline, the reworked path is about **3.34x faster**, and the summed per-file phase time drops **5.85x**. Resolving raw coverage in the main process further cuts Rstest's own processing time (about **2x** on the same project) and lowers CPU usage. The coverage output is unchanged.
+
+There is no configuration change — projects using `coverage.provider: 'v8'` get the speedup automatically.
+
+## Fake timers aligned with `@sinonjs/fake-timers` 15 \{#fake-timers}
+
+Rstest 0.11 upgrades to `@sinonjs/fake-timers@15.4.0` and aligns the fake timers runtime with its API. Two methods are now available:
+
+- `rstest.jumpTimersByTime(ms)` jumps the clock forward by `ms` without running the timers in between, so any timer scheduled within that span fires at most once, at the destination.
+- `rstest.setTickMode({ mode })` switches the clock between manual and auto-advancing modes.
+
+```ts title="example.test.ts"
+import { expect, rstest, test } from '@rstest/core';
+
+test('jump without running intermediate timers', () => {
+  rstest.useFakeTimers();
+  const fn = rstest.fn();
+
+  setInterval(fn, 1000);
+  rstest.jumpTimersByTime(5000);
+
+  expect(fn).toHaveBeenCalledTimes(1);
+});
+```
+
+`rstest.setSystemTime(date)` also works on its own now — without a prior `rstest.useFakeTimers()` call it pins only the global `Date` and leaves the real timers intact, so you can freeze the system clock without taking over `setTimeout` / `setInterval`.
+
+This release also closes a Browser Mode gap. Browser Mode previously aliased `@sinonjs/fake-timers` to a minimal stub that kept a clock-shaped object but did not actually fake browser globals such as `setTimeout` or `Date`. Rstest 0.11 removes that stub and bundles the real implementation, so fake timers behave consistently across Node mode and Browser Mode — including `Date` / `performance`, animation frames, microtasks, and string durations. See [Fake Timers](/api/runtime-api/rstest/fake-timers) for more details.
+
+## Other improvements \{#other-improvements}
+
+- **Clearer error for `rs.spyOn` on ESM namespace exports.** Previously, spying on a read-only ESM namespace export produced an opaque failure; it now produces an actionable error explaining why the binding cannot be reassigned.
+- **`new URL()` and Wasm resolve from on-disk source.** Assets referenced via `new URL(..., import.meta.url)` and Wasm modules now resolve from the original source location, matching runtime behavior.
+- **Shared module state under `isolate: false`.** Imported module state is now shared and context-bound APIs stay live across files when `isolate: false`, so cross-file singletons behave as expected.
+- **Browser Mode project isolation.** Each project now runs in its own Rsbuild instance, fixing cross-project module resolution in multi-project browser runs.
+- **OS-native `testPath`.** `testPath` is now surfaced with the platform's native path separators.
+- **Custom `runCLI` argv.** Programmatic callers can pass a custom `argv` array to `runCLI`, while `process.argv` remains the default.
+
+## Upgrade
+
+Upgrade the `@rstest/*` packages to version 0.11 to get these improvements. Rstest 0.11 includes a few breaking API changes — see [API changes on the road to 1.0](#api-changes) for the migration steps.
+
+For a full list of changes, see the [v0.11.0 release notes](https://github.com/web-infra-dev/rstest/releases/tag/v0.11.0).

website/docs/zh/api/runtime-api/rstest/fake-timers.mdx

@@ -167,7 +167,7 @@ const realTime = rs.getRealSystemTime();
 
 ## rs.jumpTimersByTime
 
-<ApiMeta addedVersion="0.10.7" />
+<ApiMeta addedVersion="0.11.0" />
 
 - **别名：** `rstest.jumpTimersByTime`
 - **类型：** `(ms: number | string | Temporal.Duration) => RstestUtilities`
@@ -187,7 +187,7 @@ expect(cb).toHaveBeenCalledTimes(1);
 
 ## rs.setTickMode
 
-<ApiMeta addedVersion="0.10.7" />
+<ApiMeta addedVersion="0.11.0" />
 
 - **别名：** `rstest.setTickMode`
 - **类型：** `(mode: { mode: 'manual' | 'nextAsync' } | { mode: 'interval'; delta?: number }) => RstestUtilities`

website/docs/zh/blog/_meta.json

@@ -1 +1 @@
-["index", "announcing-0-10"]
+["index", "announcing-0-11", "announcing-0-10"]