Self-Contained Changes
A self-contained change is a change to isolated package(s), or a general change with limited scope and impact on the rest of the distribution/project. Examples include addition of a group of leaf packages, or a coordinated effort within a Special Interest Group (SIG) with limited impact outside the SIG’s functional area.
AspellDeprecation
Deprecating aspell package because there are better-supported spell checkers like hunspell/enchant2 which could be used instead. It also has an upstream with almost 4 years of no action.
Read more information about this change.
Automatic Cloud Reboot On Updates
Fedora cloud instances now automatically reboot when a user requests package updates followed by a reboot on the first boot of the instance. The reboot only occurs if an updated package requires a reboot to go into effect (such as a kernel or critical system library).
Read more information about this change.
BiggerESP
Fedora now defaults to a larger EFI System Partition which allows firmware updates to work on newer hardware, and allows future bootloader and kernel modernizations.
Read more information about this change.
CloudEC2gp3
In Amazon EC2, Elastic Block Store (EBS) volumes can be one of several types. These can be specified at volume creation time, including for the default volumes that are created on instance launch. An AMI will have default volumes and volume types configured. Fedora currently defaults to the gp2 volume type. This proposal is to switch to gp3 as the default volume type for Fedora. The gp3 volume type is both more flexible than gp2, and can be up to 20% cheaper per GB.
Read more information about this change.
CloudEC2ImagesNoStandardStorage
Fedora AMIs for EC2 now default to the latest gp2/3
storage option.
Read more information about this change.
CloudEC2IMDSv2Only
In November 2019, AWS launched IMDSv2 (Instance Meta-Data Store version 2 - see https://aws.amazon.com/blogs/security/defense-in-depth-open-firewalls-reverse-proxies-ssrf-vulnerabilities-ec2-instance-metadata-service/ ) which provides "belt and suspenders" protections for four types of vulnerabilities that could be used to try to access the Instance Meta-Data Store available to EC2 instances. In that announcement, AWS recommended adopting IMDSv2 and restricting access to IMDSv2 only for added security. This can be done at instance launch time, or ([https://aws.amazon.com/about-aws/whats-new/2022/10/amazon-machine-images-support-instance-metadata-service-version-2-default/ more recently in October 2022]) by providing a flag when registering an AMI to indicate that the AMI should by default launch with IMDSv1 disabled, and thus require IMDSv2.
By enabling this flag for Fedora, we provide a better security posture for Fedora users running in EC2.
When an AMI is registered for IMDSv2 it is still possible to launch instances with IMDSv1 enabled by providing the right option to the RunInstances EC2 API call. The flag merely switches the default.
Read more information about this change.
CloudEC2UEFIPreferred
EC2 images are now registered with the uefi-preferred
boot mode, thus boot in UEFI mode where possible.
Read more information about this change.
F39-Lazarus-repackaging
The lazarus
package has been split into multiple sub-packages. Apart from GTK2, the IDE now supports building programs using the GTK3, Qt4 and Qt5 widget sets - available by installing lazarus-lcl-*
packages.
Read more information about this change.
Fedora Images On Azure
Fedora Cloud Edition is now available for use in Microsoft Azure.
Read more information about this change.
Fedora Onyx
Fedora Onyx has been introduced as a new immutable variant of Fedora Linux / Fedora Budgie Spin, featuring the Budgie Desktop environment and the same robust technologies as our other variants such as Kinoite, Sericia, and Silverblue (flatpak, rpm-ostree, podman, toolbx).
Read more information about this change.
FedoraSilverblueBootupd
Will have to be written.
Read more information about this change.
FedoraSilverblueUnifiedCore
N/A
Read more information about this change.
FontAwesome6
The fontawesome-fonts package has been upgraded to version 6.3.0, and a compatibility fontawesome4-fonts package has been introduced for applications that still require FontAwesome 4.7.0. For packages that can use the FontAwesome 6.x icons, the changes described in [https://fontawesome.com/docs/changelog/ the FontAwesome changelog] are now available. Packages that use the FontAwesome 4.x icons do not have any user-visible changes.
Read more information about this change.
LXQt image for aarch64
Generate LXQt image (both iso and disk image) for aarch64 architecture.
Read more information about this change.
ManPagesRuRetirement
Retiring man-pages-ru because it is already part of the man-pages-l10n.
Read more information about this change.
Mass Retire Golang Leaves
Remove unused Golang libraries from the repositories. These packages are not meant for end user consumption to begin with. We will not Obsolete these packages, so they won’t be removed from existing systems.
Read more information about this change.
mkosi-initrd
Simplified initrds built with mkosi-initrd
are available for testing.
Read more information about this change.
ModularGnomeKeyring
The monolithic daemon provided by GNOME Keyring will be split into dedicated sub-daemons, so that they can be consistently managed by systemd.
Read more information about this change.
Vagrant 2.3
See the upstream CHANGELOG.md file for full release notes: https://github.com/hashicorp/vagrant/blob/986a01734f008d62897bb66085381090e4fcabfc/CHANGELOG.md
Read more information about this change.
Want to help? Learn how to contribute to Fedora Docs ›