v2.5

UEFI:NTFS v2.5

• This version fixes unloading of the native file system driver for some platforms/media [eed6de8].
• This is needed because on some platforms (e.g. Intel NUCs) MBR based media may present more than one disk instance for the disk where the target bootloader resides, including some driverless disk instances, whereas we previously assumed that there could only ever be one disk instance.
• We also ensure that, if UEFI:NTFS is being chainloaded, SetPathCase() will be able to perform its job regardless of whether the directory has already been opened [ee57bd9].
• This release was build from GitHub Actions on Linux/Ubuntu using gcc and the latest EDK2 (https://github.com/pbatard/uefi-ntfs/actions/runs/8557379470).
• The _signed binaries are the Secure Boot signed versions (In a Secure Boot enabled environment, these should be used with the _signed versions of the NTFS drivers found here)
• Note that the 32-bit ARM version is not Secure Boot signed, as Microsoft's current policies require additional validation for the signing of 32-bit ARM UEFI binaries.

v2.4

UEFI:NTFS v2.4

• This version adds unloading of any native file system driver servicing the target partition so that is replaced by our own [ae74e6a].
• This is done in lights of issues raised in the commonly used AMI NTFS driver (see https://github.com/pbatard/AmiNtfsBug) as well as other reports that indicate potential issues arising from attempting to use native file system drivers.
• Doing so also allows the user to have choice in the driver they use for UEFI boot as, if there already exists a native file system driver, they will be able to pick between 2 boot options for the same media, with each one using a different file system driver.
• All other changes since v2.3 are external to the bootloader code.
• This release was build from GitHub Actions on Linux/Ubuntu using gcc and the latest EDK2 (https://github.com/pbatard/uefi-ntfs/actions/runs/8270940512).
• The _signed binaries are the Secure Boot signed versions (In a Secure Boot enabled environment, these should be used with the _signed versions of the NTFS drivers found here)
• Note that the 32-bit ARM version is not Secure Boot signed, as Microsoft's current policies require additional validation for the signing of 32-bit ARM UEFI binaries.

v2.3

UEFI:NTFS v2.3

• This version adds detection of Microsoft bootloaders to report a more explicit error on boot failure [b9adb76].
• All other changes since v2.2 are either minor variable renaming/reordering or changes that are external to the bootloader code.
• This release was build on Linux/Ubuntu using gcc and the latest EDK2.
• The _signed binaries are the Secure Boot signed versions (In a Secure Boot enabled environment, these should be used with the _signed versions of the NTFS drivers found here)
• Note that the 32-bit ARM version is not Secure Boot signed, as Microsoft's current policies require additional validation for the signing of 32-bit ARM UEFI binaries.

v2.2

UEFI:NTFS v2.2

• This release was build on Linux/Ubuntu using gcc and the latest EDK2.
• The _signed binaries are the Secure Boot signed versions (In a Secure Boot enabled environment, these should be used with the _signed versions of the NTFS drivers found here)
• Note that the 32-bit ARM version is not Secure Boot signed, as Microsoft's current policies require additional validation for the signing of 32-bit ARM UEFI binaries.

v2.1

UEFI:NTFS v2.1

• This release was build on Linux/Ubuntu using gcc and the latest EDK2.

v2.0

add automated release creation

* Also update gnu-efi to latest