Posted on Leave a comment

Fedora Linux 43 is here!

I’m excited to announce my very first Fedora Linux release as the new Fedora Project Leader. Fedora Linux 43 is here! 43 releases! Wow that’s a lot. I was thinking about proposing special tetracontakaitrigon stickers to celebrate this release, but I’m not sure anyone would notice they weren’t circles.

Thank you and congrats to everyone who has contributed to Fedora to this release, and in all the releases leading up to this one. I’m grateful to be back with a chance to take stewardship of the collaboration as the Fedora Project leader. I’ve been getting my feet under me as much as I can in these first few months. I’m looking forward to writing up some longer missives about where I want to steer this ship, but for right now I just want to highlight some of the changes you should expect to encounter in the latest release of Fedora Linux. Read the highlights below to find out more. Or if you are ready just jump right in!

Upgrade

If you have an existing system, Upgrading Fedora Linux to a New Release is easy. In most cases, it’s not very different from just rebooting for regular updates, except you’ll have a little more time to grab a coffee.

Fresh Install

If this is your first time running Fedora Linux, or if you just want to start fresh with Fedora, download the install media for our flagship Editions (Workstation, KDE Plasma Desktop, Cloud, Server, CoreOS, IoT),  for one of our Atomic Desktops (Silverblue, Kinoite, Cosmic, Budgie, Sway), or for alternate desktop options (like Cinnamon, Xfce, Sway, or others).

What’s new?

As usual, with Fedora, there are just too many individual changes and improvements to go over in detail. You’ll want to take a look at the release notes for that.

Notable User Visible Changes

There are, however, a few notable user visible changes in this release. For those of you installing fresh Fedora Linux 43 Spins, you may be greeted with the new Anaconda WebUI. This was the default installer interface for Fedora Workstation 42, and now it’s the default installer UI for the Spins as well.

If you are a GNOME desktop user, you’ll also notice that the GNOME is now Wayland-only in Fedora Linux 43. GNOME upstream has deprecated X11 support, and has disabled it as a compile time default in GNOME 49. Upstream GNOME plans to fully remove X11 support in GNOME 50.

Plumbing Upgrades

Beyond the user-visible changes, there are a couple of significant bits of plumbing that should go unnoticed for most users but are a big deal, nonetheless.

Fedora Linux 43 will be the first release with RPM 6.0. Like I said, this should go unnoticed to end-users, but it is a significant change. RPM 6.0 provides some interesting security enhancements, like multiple key signing of packages. This should help future-proof package signing as we transition to post-quantum-crypto OpenPGP keys in future releases.

We’re also moving forward with our bootc enablement story. Fedora CoreOS is now buildable from a Fedora base bootc image using a Containerfile, instead of needing to be composed with a custom tool. That means anyone with podman can build the Fedora CoreOS image, whether manually or via CI/CD automation.

Fedora CoreOS (FCOS) is also changing how it’s issuing updates to users in Fedora 43. Instead of using an OSTree repository, FCOS updates will be delivered exclusively as OCI images. FCOS 42 provided both OSTree repository and OCI registry as a transition for users. In FCOS 43, the OSTree updates are disabled entirely.

Save the Date: Fedora Linux 43 Release Party!

To celebrate all this incredible community work, we’ll be hosting a virtual Fedora Linux 43 Release Party! Please save the date for Friday, 21 November. We’re still finalizing the schedule and speakers, so registration isn’t open just yet, but more details will be shared soon. You can keep an eye on the Fedora Linux 43 Release Party Schedule wiki page for the latest updates!

If you hit a snag

If you run into a problem, visit our Ask Fedora user support forum. This forum includes a category where we collect common issues and solutions or work-arounds.

Just drop by and say “hello”

Drop by our “virtual watercooler” on Fedora Discussion and join a conversation, share something interesting, and introduce yourself. We’re always glad to see new people!

Posted on Leave a comment

What’s New in Fedora Workstation 43

Below are a few noteworthy changes in the latest release of Fedora Workstation that we think you will love. Upgrade today from the official website, or upgrade your existing install using GNOME Software or through the terminal with dnf system-upgrade.

GNOME 49

Fedora Linux 43 Workstation also ships with the brand-new GNOME 49 release, bringing a host of refinements to your desktop. This update introduces significant enhancements for multiple display setups, an improved and streamlined workflow for taking screenshots and screen recordings, and a new “Focus Mode” to help you minimize distractions. Under the hood, resource-smart background throttling improves performance and battery life, while the Settings app has been polished with a refined UI. These are just the highlights. Check out the official GNOME 49 release notes to find more information about all the new features.

Wayland-only GNOME

One significant change we want to forewarn you about is that Fedora Linux 43 is removing the GNOME X11 packages from the Fedora repositories. All users of the GNOME X11 session will be migrated to the GNOME Wayland session with the upgrade to Fedora Workstation 43.

The transition to the GNOME Wayland session in Fedora Workstation 43 has been in the works for nearly a decade. There have been several prior steps toward this goal, such as the work in Fedora Linux 41 to remove legacy X11 dependencies from core media components.

Wayland has been the default GNOME session on Fedora Workstation for many years, but this release completes the change. The legacy gnome-session-xsession packages have been removed from the Fedora Linux 43 repositories.

This change will unlock a new level of performance and hardware compatibility. You’ll immediately notice smoother, cleaner visuals thanks to triple buffering, which dramatically reduces screen tearing. This change also improves support for a range of hardware, including enhanced drivers for Intel Xe graphics and improvements for systems using NVIDIA Optimus and Hybrid Mode.

A new default video player — Showtime

The default video player has been changed from Totem to Showtime. Showtime is built on the newer GTK 4 and Libadwaita libraries.

Use COLR for Noto Color Emoji

The Noto Color Emoji fonts have released some new files with the COLRv1 format. The COLRv1 format is a color scalable font compared with the previous color bitmap fonts. This new scalable font format should have better or similar rendering results compared to the old bitmap font format. See the change notes for more details.

Peas 2.0

If you are an app developer, you might be interested in the upgrade to Peas 2. Peas is a gobject-based plugins engine that is used by several GNOME applications.

Wrap-up

Be sure to check out the Fedora Linux 43 Change Set wiki for even more details about all the features and changes that went into Fedora Linux 43. Use the Fedora Discussion forum or Fedora’s Matrix chat server if you want to converse with the Fedora community about this new release!

Posted on Leave a comment

PHP 8.4.14 Released

The PHP development team announces the immediate availability of PHP
8.4.14. This is a bugfix release. All PHP 8.4 users are encouraged to upgrade to this version. For source downloads of PHP 8.4.14 please visit our downloads page.
Windows binaries can be found on the PHP for Windows site.
The list of changes is recorded in the ChangeLog. Release Announcement: <https://php.net/releases/8_4_14.php>
Downloads: <https://php.net/downloads>
Windows downloads: <https://windows.php.net/download#php-8.4>
Changelog: <https://php.net/ChangeLog-8.php#8.4.14>
Release Manifest: <https://gist.github.com/SakiTakamachi/2ed9bfd20c0cc87772d26fa08aa2e6e4> Many thanks to all the contributors and supporters! Regards,
Saki Takamachi, Calvin Buckley, and Eric Mann php-8.4.14.tar.bz2
SHA256 hash: f2139ce4cb7a6c5643ee98caa34e5c32ba841c2ba293e34a3d0357faa84bb3e7
PGP signature:
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEBhbpPZWvRxJD4mdhdwQm4X67s90FAmj33ywACgkQdwQm4X67
s91nvQ//fPdJ2I02nczyPavmDx/PPq34y8PObZZ740dG2bAVFjWBYNtPRLX2SFcT
SxQeDIicCT6INesZUVfP4UZQNNnku4mfkm8n6811jsBTiOcPHEFIp8mdUpPl50T2
C3D+18wemJrCwzSYLWK23WrqAhWwHuAIVCOfLhFKmHJhiiaUyykhQNaeQica6pz6
hNVnqgxUY5vxiNrmUr1oQn0DYhYBixY8mufho3xIhXHHktKBDujY6yqk3nLjYEOI
iPIiiVG9lKESvATHy9nBSl36gBm+rg6ee+lJRCaVA96Jtvl18p1SI7QU9JGLAs/V
V4vrElk7BYwvlubUH9XAcaZMoWMFIbbNYYvwbrYWJ0FWjgCmM/jK/alzOqoTc5ds
4xgKQI4vlMvjKjPnaZWFXzsWdEX8zqoWoTCmjnJyByZPl1PlVDxcXyW9NcysFXCX
UWIdFZcBYQ9NRcKuXRgTa07GMqIpLNycaQLqljVJ9cOGAfpgVMWk/Yhtroz+xAZU
/u3wpmxcWcD4gWbHllED0dzNwGmdhrU5PiDpQ6uKKyFZ6EejbbV3EGSAnGjWodDw
rdFC90Aym7RBXVV+dzG0FGrHDqiQNBMAm/cA6bVY1qOPsH4nyAcy7CCmMUmbcGEd
ANLYx3I+bDYxQfvtE/JtO69vkzQvEiOMqFIi3cbHsdoAgpmFBNs=
=aZjS
-----END PGP SIGNATURE----- php-8.4.14.tar.gz
SHA256 hash: 40341f3e03a36d48facdb6cc2ec600ff887a1af9a5e5fee0b40f40b61488afae
PGP signature:
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEBhbpPZWvRxJD4mdhdwQm4X67s90FAmj33ywACgkQdwQm4X67
s91s3A/9GdIvW8df0azX4xeGWMyeSOLwRvp6gQgQcJ2lCDVrA07coXL+6YxqaVkD
+6KqBL/RHsp84FQbl0JztlAQ+4g7Z4hUzwlfs7s382AlsWxEoM/hiEXarSX0hvCZ
Ys68WtekcUFqtqbBIaMaCRJ0aor/rwrqOVnsV2qstWG4s/SmRoq1UogmTsR3IksV
XhMTXKDPluoPanpbC9idgY8ekKckzCj+ucwoYULdzoPsUUueXXkRwoy7lLxf5FW8
O/bDzkyOQeA5sn0hiHx+FqW08qVP1KvtkH8lom+OS+qo4hWkb3w4X3q3mwTqS9On
juibQDVpM5sC/ZcFfG/nT81Xp1I+G+lgTTUwY0juOHdO6x1V59Jj1uUUZBPpe2s4
+0aAW252vpPHm3DfZ0cYSTUERtocCauUP8PDy+Jq6xMmbnoVa8//F6D/J6eSgu9n
uwhE1y+uYiaSvXHLpb5Jp7/6DZKaRIvCMg5VD1LL44YBn2EnmeG/uft+tyQ9Tg5X
HuYETif7/dPh9U6/4tFNgZo/q5A20oV25ya02NyZ8ro+Dub5zvTpg4i8ik1toFVJ
LqzD/yChWSNbYqseiLuR+QFdVfhvLC12GJt3T5G5+fZI0r1Y1wc3x0du4k/jfKur
pXn20OCUHZt+512Cs3DOJUWEi3C65cPfkX9fO366pEadlVt+BAQ=
=qIO3
-----END PGP SIGNATURE----- php-8.4.14.tar.xz
SHA256 hash: bac90ee7cf738e814c89b6b27d4d2c4b70e50942a420837e1a22f5fd5f9867a3
PGP signature:
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEBhbpPZWvRxJD4mdhdwQm4X67s90FAmj33ywACgkQdwQm4X67
s90gbhAAhJ80lJLAHeW8tVIxh2cbqE49km1NecjwWMSgxpmjT/U5h4vQ1m72vHT6
MtgHXZtkw+LXoNV4NzUJ41AjT9pLA7LjoAmmdAjG3GIimBej+p1Iba6O6WNLN0LQ
XPlX1vawObb1dFuuQLqKwkbbiTDWht6oIX6gb+SL8UDmsfevWEJj4Yshq8tjMSqo
1+ECQcf8ZRBUDITMFA5ZZVXJpGqLVKfoy9Spx9yPcek3RXkTU4x1n7iQkGWY8Yu+
INod4PDzAmc67Uq9cLkBDd3gJUQGlNti7L6c8azJAGKDZ01jOetveGMgsm9St0DW
4lJVN59r2T0lj8k4KLnM7vltmrSWimvVRTGKjNKFQQtdnG5nrq5x6tEAcVob1Q0R
2iXoD60iz+15U5XeKgHrJWGKHTc3zzjcA1B89Bkxi8QWh68v0i9GidS9Mn3BPkA/
6BtvciUuWfWM2+ycrBA7FiiDcdqh7JliA9dQn7G0r88EDcPw4MGYcEmkv2ZdC9P1
+M05jRzNSgzozSKseT5LVN8cy54fxT3YKHvoYuNJW23z15GVC1kKIJ/+06KphGwV
0KwRR26wu35Nu2eQ84a9qcL/VzXAYH24CbiQB7hH0R/6sxtsjzF0ucYpdEwr0Yb7
4Uvtz4DL1qB4dzKVs7jJjQm7A3qK0DNiVf7OpnkCSOPXont8UFw=
=BmEj
-----END PGP SIGNATURE-----

Thread (1 message)

  • Saki Takamachi
Posted on Leave a comment

New requirement for apps using Sign in with Apple for account creation

Starting January 1, 2026, developers based in the Republic of Korea must provide a server‑to‑server notification endpoint when registering a new Services ID, or updating an existing Services ID, to associate their website with an app using Sign in with Apple.

As a reminder, registering a notification endpoint allows Apple to send you important updates about the people who use your app and their account status, including:

  • Changes in email forwarding preferences.
  • Account deletions in your app.
  • Permanent Apple Account deletions.

To learn more about server-to-server notifications, see WWDC20 session 10173: Get the most out of Sign in with Apple.

When you receive these notifications, you should immediately update any data associated with the account change in the app, as well as any necessary server infrastructure, to give people more control of the personal data they’ve shared. For more information, see Processing changes for Sign in with Apple accounts.

Before submitting a new app to the App Store, or updating an existing app configuration to register a new Services ID or modify an existing Services ID, please read the guidance below.

Account change guidance

Account changes are directly related to privacy and control for the user and their personal data, and confirming account changes should be straightforward and transparent.

For account email forwarding changes:

  • Ensure any displayed user data affected by the account change matches the change event in the notification payload. Typically, this data is displayed in the app’s account settings or user profile.
  • If people need to visit a website to finish changing or verifying their email address, include a link directly to the page on your website where they can complete the process.
  • Keep users informed. If the email forwarding change affects other services you offer, let them know. If your app supports In-App Purchases, help people understand how billing, order tracking, and cancellations will be handled with the new email address.

For account deletions:

Note: Always follow applicable legal requirements for storing and retaining user account information and for handling account changes and deletions. This includes complying with local laws where your apps are available. If you have questions regarding your legal obligations, check with your legal counsel.

Resources

Posted on Leave a comment

New requirements for apps available in Texas

Beginning January 1, 2026, a new state law in Texas — SB2420 — introduces age assurance requirements for app marketplaces and developers. While we share the goal of strengthening kids’ online safety, we are concerned that SB2420 impacts the privacy of users by requiring the collection of sensitive, personally identifiable information to download any app, even if a user simply wants to check the weather or sports scores. Apple will continue to provide parents and developers with industry-leading tools that help enhance child safety while safeguarding privacy within the constraints of the law.

Once this law goes into effect, users located in Texas who create a new Apple Account will be required to confirm whether they are 18 years or older. All new Apple Accounts for users under the age of 18 will be required to join a Family Sharing group, and parents or guardians will need to provide consent for all App Store downloads, app purchases, and transactions using Apple’s In-App Purchase system by the minor. This will also impact developers, who will need to adopt new capabilities and modify behavior within their apps to meet their obligations under the law. Similar requirements will come into effect later next year in Utah and Louisiana.

Today we’re sharing details about updates that we’re making and the tools we’ll provide to help developers meet these new requirements.

To assist developers in meeting their obligations in a privacy-preserving way, we’ll introduce capabilities to help them obtain users’ age categories and manage significant changes as required by Texas state law. The Declared Age Range API is available to implement now, and will be updated in the coming months to provide the required age categories for new account users in Texas. And new APIs launching later this year will enable developers, when they determine a significant change is made to their app, to invoke a system experience to allow the user to request that parental consent be re-obtained. Additionally, parents will be able to revoke consent for a minor continuing to use an app. More details, including additional technical documentation, will be released later this fall.

We know protecting kids from online threats requires constant vigilance and effort. That’s why we will continue to create industry-leading features to help developers provide age-appropriate experiences and safeguard privacy in their apps and games, and empower parents with a comprehensive set of tools to help keep their kids safe online.