Bun v1.1.5

[Jarred-Sumner]

To install Bun v1.1.5:

curl -fsSL https://bun.sh/install | bash
# or you can use npm
# npm install -g bun

Windows:

powershell -c "irm bun.sh/install.ps1|iex"

To upgrade to Bun v1.1.5:

bun upgrade

Read Bun v1.1.5's release notes on Bun's blog

Thank you to 16 contributors!

• @boyer-victor
• @cirospaciari
• @Deckluhm
• @dylan-conway
• @Electroid
• @erikbrinkman
• @gvilums
• @Jarred-Sumner
• @jwigert
• @lafkpages
• @liudonghua123
• @nektro
• @paperdave
• @tuttarealstep
• @welfuture
• @zackradisic

Full Changelog: bun-v1.1.4...bun-v1.1.5

---

This discussion was created from the release Bun v1.1.5.

[liudonghua123]

I tried to update bun from 1.1.4 to the latest 1.1.5 using bun upgrade, but it failed with the following errors.

From the error NOT_SAME_DEVICE info, maybe it is because the downloaded bun (maybe in temp C:) is not the same disk driver as the original bun (D:\apps\bun.exe).

If I use npm i -g bun, it works.

[liudonghua123]

I found some code related to this problem.

bun/src/cli/upgrade_command.zig

Lines 888 to 900 in dfcbe09

	Output.errGeneric(
	\\Failed to move new version of Bun to {s} to {s}
	\\
	\\Please reinstall Bun manually with the following command:
	\\ {s}
	\\
	,
	.{
	destination_executable,
	@errorName(err),
	manual_upgrade_command,
	},
	);

bun/src/c.zig

Lines 105 to 126 in dfcbe09

	// renameatZ fails when renaming across mount points
	// we assume that this is relatively uncommon
	// TODO: change types to use `bun.FileDescriptor`
	pub fn moveFileZ(from_dir: bun.FileDescriptor, filename: [:0]const u8, to_dir: bun.FileDescriptor, destination: [:0]const u8) !void {
	switch (bun.sys.renameat(from_dir, filename, to_dir, destination)) {
	.err => |err| {
	// allow over-writing an empty directory
	if (err.getErrno() == .ISDIR) {
	_ = bun.sys.rmdirat(to_dir, destination.ptr);
	try bun.sys.renameat(from_dir, filename, to_dir, destination).unwrap();
	return;
	}
	if (err.getErrno() == .XDEV) {
	try moveFileZSlow(from_dir, filename, to_dir, destination);
	} else {
	return bun.errnoToZigErr(err.errno);
	}
	},
	.result => {},
	}
	}

Also maybe related to ziglang/zig#17049.

If the std.os.windows.renameAtW do not support move files across different mounts, can we just replaced to copy-then-remove?

I tested the following code, std.fs.renameAbsolute could not move files across different mounts/drivers indeed.

// src/main.zig
const std = @import("std");

const w = std.os.windows;

pub fn main() !void {
    // move file test across devices
    const src = "C:/Users/Liu.D.H/Desktop/test.txt";
    const dst = "D:/test.txt";
    // try std.fs.renameAbsolute(src, dst); // error.Unexpected: GetLastError(17): The system cannot move the file to a different disk drive.

    // this works!
    try std.fs.copyFileAbsolute(src, dst, .{});
    try std.fs.deleteFileAbsolute(src);
    return;
}