Remove older bun version pins from workflows once bun v1.1.46 is out

[lgarron]

There's a really silly issue where making a directory with -p or "recursive": true results in an error:

cubing.js/script/build/lib/build-lib-js.ts

Line 27 in 9233708

await mkdir("./.temp", { recursive: true });

EEXIST: file already exists, mkdir './.temp'
    path: "./.temp",
 syscall: "mkdir",
   errno: -17,
    code: "EEXIST"

I've run into this in a few project already, and I don't know if the issue is with bun, with GitHub, or with Linux. It seems to be at least partially environment-specific, as I can't reproduce on macOS (notwithstanding the many, many times I run into similar errors due to a different issue).

[lgarron]

Oh:

• mkdir with recursive flag (regression since 1.1.42) throws error when directory exists oven-sh/bun#16466
• fs.mkdir already exists error is still hapenning oven-sh/bun#16536
• fs.mkdirSync() throws when the path already exists with recursive:true oven-sh/bun#16474

[lgarron]

I'm a little confused. https://bun.sh/blog/bun-v1.1.45#fixed-fs-mkdir-recursive-regression implies that this was fixed in bun 1.45.

But our CI was failing on this with 1.1.45+196621f25: oven-sh/bun@196621f25

[lgarron]

I'm a little confused. https://bun.sh/blog/bun-v1.1.45#fixed-fs-mkdir-recursive-regression implies that this was fixed in bun 1.45.

But our CI was failing on this with 1.1.45+196621f25: oven-sh/bun@196621f25

Ah. The changelog is a lie:

oven-sh/bun#16536 (comment)