:information_source: The changes are between v2.4.2 and e154a6809d85b067f384390bc236a10c5e5445ac

Breaking changes

• Partition().uuid now properly reports the UUID as reported by lsblk -o+UUID and not PARTUUID. A new Partition().part_uuid has been introduced where the PARTUUID is needed. This was required in order to get the FIDO2 support to work.

New features:

• FIDO2 support (https://github.com/archlinux/archinstall/pull/1196) when unlocking disk encryption (very early beta, will most likely break with PIN required devices. Only tested with an older blue Yubikey that does not support PIN entry)
• archinstall.general.JSON encoder now supports encoding pathlib.Path objects.
• --config, --disk-layout and --creds now all support remote loading thanks to the changes in json_stream_to_structure. A slight bug caused only --config to support this method of operation.
• archinstall.get_fido2_devices() returns a dict[/dev/path] = {"manufacturer" : ..., "product" : ...} of all available FIDO2 devices
• archinstall.fido2_enroll(hsm_device, partition, password) has been added to enroll FIDO2 devices as a unlocking mechanism to a partition. Password is required due to the workflow of archinstall who will enroll a master password first, this it to automate operations. Post configuration can remove this master password if needed.
• Different menu types have been added, such as MenuSelectionType.Selection, MenuSelectionType.Esc, MenuSelectionType.Ctrl_c. This in order to handle the different return types of menu selections.
• Ctrl+C now clears the current option, and Esc properly backs out without modifying changes - Thanks to @svartkanin
• Locale language and Locale encoding has been brought to the main menu as it should be ready for general use now.
• network-manager-applet will now be installed if a desktop profile was used, and NetworkManager was chosen as the network manager of choice. systemd-networkd will not for instance get this installed even under a desktop profile. Probably expected behavior but I felt like mentioning it anyway.
• Profile() has gotten a .name and a .is_desktop_profile property, name returns the basename of the profile path, and is_desktop_profile returns a boolean whether the profile belongs to the desktop group.
• General improvements to translations and more languages have been added.
  • Polish - Thanks to @MedzikUser
  • Portuguese - Thanks to @lucaspcamargo
  • Russian - Thanks to @Alexmelman88
  • Urdu - Thanks to @mfgbhatti

• archinstall.udevadm_info(path) has been added to return udevadm info /path information in a dict like fashion

Bug fixes / Tweaks

• Fixed a severe issue (https://github.com/archlinux/archinstall/issues/1197) where Mark as encrypted option in the guided partitioning tool would mark all partitions for encryption. This due to a function called select_encrypted_partitions() that was neglected and acted as a bit of a prototype function for future work, which would allow selecting which partitions to encrypt. This function is now developed as intended and an option to select one or more encrypted volumes will be presented - without additional partitions being encrypted.
• Fixed a bug where children wouldn't always exist in the lsblk report
• Menu.yes_no() was causing a bug, that has been fixed
• Added a warning when the selected disk is too low on space to suggest a automatic layout
• SysCommand* now properly changes directory only for the child process, previously both the parent and the forked process would change directory to the specified working_directory, and both would change back immediately. This has been corrected so only the parent changes back immediately after forking.
• SysCommand now supports working_directory parameter, and passes it to SysCommandWorker as expected.
• json_stream_to_structure now supports loading resources remotely.
• The menu system now only takes into account the visible menu entries when structuring the layout. Previously hidden items would also account for the layout dimensions.
• Save configuration -> All now properly saves all configurations, including disk configurations. There is still a small discrepancy between the automated save of configuration during installation and this save option. It's a known issue and will be fixed in the next release.