@endevco/aube-win32-arm64 1.0.0-beta.2 → 1.0.0-beta.3

package/README.md

@@ -23,7 +23,7 @@
 
 ## Why Try It
 
-**[Fast installs](https://aube.en.dev/benchmarks).** Warm CI is about 9x faster than pnpm and 3x faster than Bun in the current benchmarks. Across the fixture set, aube runs roughly 2-21x faster than pnpm and 1-3x faster than Bun.
+**[Fast installs](https://aube.en.dev/benchmarks).** Warm CI is about 6x faster than pnpm and 2x faster than Bun in the current benchmarks. Across the fixture set, aube runs roughly 2-21x faster than pnpm and 1-2x faster than Bun.
 
 **[Existing lockfiles](https://aube.en.dev/package-manager/lockfiles).** Reads and writes `pnpm-lock.yaml`, `package-lock.json`, `npm-shrinkwrap.json`, `yarn.lock`, and `bun.lock` in place.
 
@@ -154,10 +154,10 @@ If a project already uses `pnpm-workspace.yaml`, aube can read and write it. New
 | `pnpm-lock.yaml` v9 | yes | yes |
 | `package-lock.json` v2/v3 | yes | yes |
 | `npm-shrinkwrap.json` | yes | yes |
-| `yarn.lock` v1 | yes | yes |
+| `yarn.lock` (v1 classic + v2+ berry) | yes | yes |
 | `bun.lock` | yes | yes |
 
-aube is not compatible with every historical lockfile shape. Older pnpm v5/v6 lockfiles should be upgraded with pnpm before switching, and Yarn Berry/PnP projects may need to stay on Yarn or migrate first.
+aube is not compatible with every historical lockfile shape. Older pnpm v5/v6 lockfiles should be upgraded with pnpm before switching. Yarn PnP projects need to move to a `node_modules` linker first — aube writes `node_modules`, not `.pnp.cjs`.
 
 When more than one lockfile exists, prefer keeping one canonical lockfile for the project so teammates and CI do not fight over dependency state.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@endevco/aube-win32-arm64",
-  "version": "1.0.0-beta.2",
+  "version": "1.0.0-beta.3",
   "description": "Platform binaries for aube — do not install directly, see @endevco/aube.",
   "homepage": "https://aube.en.dev",
   "repository": {