<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Aurora Blog</title>
        <link>https://docs.getaurora.dev/blog</link>
        <description>Updates and announcements from the Aurora project</description>
        <lastBuildDate>Wed, 25 Feb 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>Copyright © 2026 Aurora and Universal Blue</copyright>
        <item>
            <title><![CDATA[Removing freeipa-client from Aurora]]></title>
            <link>https://docs.getaurora.dev/blog/removing-freeipa</link>
            <guid>https://docs.getaurora.dev/blog/removing-freeipa</guid>
            <pubDate>Wed, 25 Feb 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[We are removing freeipa-client from Aurora due to SELinux issues.]]></description>
            <content:encoded><![CDATA[<p>Hello Stargazers!</p>
<p>We are removing <code>freeipa-client</code> permanently from Aurora because it is breaking our updates. Among other issues, there are multiple issues, in particular this <a href="https://bugzilla.redhat.com/show_bug.cgi?id=2332433" target="_blank" rel="noopener noreferrer" class="">upstream ostree/bootc bug</a> and <a href="https://bugzilla.redhat.com/show_bug.cgi?id=2332433" target="_blank" rel="noopener noreferrer" class="">this bug</a>. Our change is tracked in <a href="https://github.com/ublue-os/aurora/pull/1811" target="_blank" rel="noopener noreferrer" class="">this PR</a>, and the related SELinux policy discussion is on the <a href="https://github.com/fedora-selinux/selinux-policy/issues/3081" target="_blank" rel="noopener noreferrer" class="">Fedora SELinux issue tracker</a>.</p>
<p>If you depend on <code>freeipa-client</code>, you can build a custom image with the package re-added as a layer. New stable images with the package removed will be pushed out shortly. Thanks to RoyalOughtness for tracking this down!</p>
<p>Cheers ~Niklas</p>]]></content:encoded>
            <author>me@nhaiden.io (Niklas Haiden)</author>
        </item>
        <item>
            <title><![CDATA[KDE Plasma 6.6 now available]]></title>
            <link>https://docs.getaurora.dev/blog/plasma-66</link>
            <guid>https://docs.getaurora.dev/blog/plasma-66</guid>
            <pubDate>Thu, 19 Feb 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Plasma 6.6 is here]]></description>
            <content:encoded><![CDATA[<p>KDE has <a href="https://kde.org/announcements/plasma/6/6.6.0/" target="_blank" rel="noopener noreferrer" class="">released</a> Plasma 6.6, its next version of the Plasma desktop.</p>
<p>We have also released a new stable build for Aurora, which includes the new Plasma 6.6 update.</p>
<p>For us the bigger things that are included in Plasma 6.6 will be coming with the Fedora 44 release. With that we will say goodbye to SDDM and we will switch to the new <a href="https://invent.kde.org/plasma/plasma-login-manager" target="_blank" rel="noopener noreferrer" class="">Plasma Login Manager</a>.</p>
<p>There are still <a href="https://pagure.io/fedora-kde/SIG/issue/684" target="_blank" rel="noopener noreferrer" class="">issues</a> to iron out on the Fedora side so any help would be welcome.</p>
<p>Also with Fedora 44 we will also get the new <a href="https://invent.kde.org/plasma/plasma-setup" target="_blank" rel="noopener noreferrer" class="">Plasma Setup</a> (formerly Kiss) for the after install setup.</p>]]></content:encoded>
            <author>aurora@sl.loota.org (Juha Uotila)</author>
        </item>
        <item>
            <title><![CDATA[KDE Plasma 6.6 Beta builds now available]]></title>
            <link>https://docs.getaurora.dev/blog/plasma-6-6-beta</link>
            <guid>https://docs.getaurora.dev/blog/plasma-6-6-beta</guid>
            <pubDate>Sat, 17 Jan 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Plasma 6.6 Beta is here]]></description>
            <content:encoded><![CDATA[<p><img decoding="async" loading="lazy" alt="plasma 6.6 desktop" src="https://docs.getaurora.dev/assets/images/plasma66-beta-9f0ae62e0a4e5c51a20bf9cfbbe33b75.png" width="3440" height="1440" class="img_ev3q"></p>
<p>KDE has <a href="https://kde.org/announcements/plasma/6/6.5.90/" target="_blank" rel="noopener noreferrer" class="">released</a> its next version of the Plasma desktop as a first beta.</p>
<p>So we are going to join the fun too and today our <code>beta</code> stream is again activated and will be housing the Plasma 6.6 Betas.</p>
<p>We will be keeping these building daily until Plasma 6.6 hits the Fedora stable repos later next month.</p>
<p>These builds won't be containing the new <a href="https://invent.kde.org/plasma/plasma-login-manager" target="_blank" rel="noopener noreferrer" class="">Plasma Login Manager</a>, <a href="https://invent.kde.org/plasma/plasma-setup" target="_blank" rel="noopener noreferrer" class="">Plasma Setup</a> (formerly Kiss) or <a href="https://invent.kde.org/plasma/plasma-keyboard" target="_blank" rel="noopener noreferrer" class="">Plasma Keyboard</a>.</p>
<p>Other Plasma 6.6 important features are highlighted in <a href="https://community.kde.org/Plasma/Plasma_6#Plasma_6.6" target="_blank" rel="noopener noreferrer" class="">KDE Community Wiki</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="help-test-the-release">Help test the release<a href="https://docs.getaurora.dev/blog/plasma-6-6-beta#help-test-the-release" class="hash-link" aria-label="Direct link to Help test the release" title="Direct link to Help test the release" translate="no">​</a></h2>
<p>If you are interested on testing the latest Plasma release before it hits stable next month, you can just rebase to the beta builds:</p>
<p><code>sudo bootc switch --enforce-container-sigpolicy ghcr.io/ublue-os/aurora:beta</code></p>
<p>or if you want the -dx release:</p>
<p><code>sudo bootc switch --enforce-container-sigpolicy ghcr.io/ublue-os/aurora-dx:beta</code></p>]]></content:encoded>
            <author>aurora@sl.loota.org (Juha Uotila)</author>
        </item>
        <item>
            <title><![CDATA[Stargazer 5 - Year in review]]></title>
            <link>https://docs.getaurora.dev/blog/aurora-2025</link>
            <guid>https://docs.getaurora.dev/blog/aurora-2025</guid>
            <pubDate>Wed, 31 Dec 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Year 2025 for Aurora]]></description>
            <content:encoded><![CDATA[<p>Hello Stargazers, today we look back at the year 2025 for Aurora and also check in to year 2026. This article will contain most of the same material as the <a href="https://docs.projectbluefin.io/blog/bluefin-2025" target="_blank" rel="noopener noreferrer" class="">Bluefin Year End Wrapup</a> with some Aurora-specific updates added.</p>
<p>This article is going to be on the longer side, so grab your favorite drink and let's get on with it!</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="history-of-aurora">History of Aurora<a href="https://docs.getaurora.dev/blog/aurora-2025#history-of-aurora" class="hash-link" aria-label="Direct link to History of Aurora" title="Direct link to History of Aurora" translate="no">​</a></h2>
<p>A small history lesson for those who are new to Aurora.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="aurora-as-part-of-bluefin">Aurora as part of Bluefin<a href="https://docs.getaurora.dev/blog/aurora-2025#aurora-as-part-of-bluefin" class="hash-link" aria-label="Direct link to Aurora as part of Bluefin" title="Direct link to Aurora as part of Bluefin" translate="no">​</a></h3>
<p>Going back to the year 2024 and the month of April, Aurora got officially accepted as part of the Universal Blue Project. Legend <a href="https://github.com/m2giles" target="_blank" rel="noopener noreferrer" class="">M2</a> reworked the Bluefin repository to accommodate both Bluefin and Aurora and build them from the same code. Both products being built out of the same repository made sense at the time since they shared lots of similarities in configuration, preinstalled applications and other stuff.</p>
<p>This is where the visual identity, vision and idea for idea started to form. Over the course of the next few months, we spent time building out the identity for Aurora, including launching the first iteration of the website where you could discover and download the OS.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-split">The split<a href="https://docs.getaurora.dev/blog/aurora-2025#the-split" class="hash-link" aria-label="Direct link to The split" title="Direct link to The split" translate="no">​</a></h3>
<p>Fast forward to December 2024 and this is the time where the "split" happened. Jorge cloned the Bluefin repository and spun it off into its own repository. Maintaining both Aurora and Bluefin in the same repository was not really feasible anymore since the two were diverging and the effort to make sure one didn't break when something changed was getting out of hand. So Aurora got its own repository. This was also around the time when people from the community, notably <a href="https://github.com/inffy/" target="_blank" rel="noopener noreferrer" class="">inffy</a>, <a href="https://github.com/ledif/" target="_blank" rel="noopener noreferrer" class="">ledif</a> and <a href="https://github.com/renner0e/" target="_blank" rel="noopener noreferrer" class="">renner</a> started "showing up" and contributing to both Aurora and Universal-Blue. All 3 of them quickly became super awesome people to work with on maintaining Aurora and other parts of Universal Blue. I want to give a special shoutout to all 3 of them because without them, Aurora would not be maintainable and in its healthy, flourishing and best form it's ever been. Thank you so much.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="chandeleer-joining">Chandeleer joining<a href="https://docs.getaurora.dev/blog/aurora-2025#chandeleer-joining" class="hash-link" aria-label="Direct link to Chandeleer joining" title="Direct link to Chandeleer joining" translate="no">​</a></h3>
<p>In early 2025 we found our Art Director and Artist <a href="https://github.com/chandeleer1698" target="_blank" rel="noopener noreferrer" class="">Chandeleer</a>. Launching with his first wallpaper in May 2025, he went on to create a whole universe of characters and accompanying art for Aurora, the Coneheads. Out of basically nothing, he has been rocking the wallpaper game ever since and we can't be more grateful for having such a talented artist like him. Chandeleer has been rocking it with his wallpapers since May and you can find them all shipped on your Aurora installation, free to choose, with a new one every month. On a side note, you can check out all of the characters and wallpapers in our new <a href="https://getaurora.dev/en/art" target="_blank" rel="noopener noreferrer" class="">Art Gallery</a> over on our website.</p>
<p>Please support Chandeleer on his <a href="https://ko-fi.com/chandeleer" target="_blank" rel="noopener noreferrer" class="">Ko-Fi Page</a> so he can make even more art.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="our-new-logo">Our new logo<a href="https://docs.getaurora.dev/blog/aurora-2025#our-new-logo" class="hash-link" aria-label="Direct link to Our new logo" title="Direct link to Our new logo" translate="no">​</a></h3>
<p>In the summer of 2025, Aurora got a small but vital and important brand refresh by two awesome artists from the community, <a href="https://github.com/delphicmelody" target="_blank" rel="noopener noreferrer" class="">Delphic Melody</a> and <a href="https://github.com/zandrro" target="_blank" rel="noopener noreferrer" class="">zandrro</a>. They took the old logo which was AI generated (crucify me, but sadly I'm not an artist) and turned it into a human-made and the most awesome version ever. Also a huge thank you to both of them for their contributions.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="aurora-gets-its-own-mascot-scope">Aurora gets its own mascot, Scope<a href="https://docs.getaurora.dev/blog/aurora-2025#aurora-gets-its-own-mascot-scope" class="hash-link" aria-label="Direct link to Aurora gets its own mascot, Scope" title="Direct link to Aurora gets its own mascot, Scope" translate="no">​</a></h3>
<p>As part of the art that was created by Chandeleer, Aurora got its own identity and mascot, Scope. Representing a telescope in a living form (always working with the stargazer theme!), he is probably one of the cutest and best one's I've seen yet. He has since appeared in every wallpaper since the first one.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="2025-in-general">2025 in General<a href="https://docs.getaurora.dev/blog/aurora-2025#2025-in-general" class="hash-link" aria-label="Direct link to 2025 in General" title="Direct link to 2025 in General" translate="no">​</a></h2>
<p>For 2025, most of our work has been on the "backend" doing lots of refactoring and cleanup on the images. We considered Aurora mostly "feature complete" and didn't ship too many user-facing changes.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="architecture-overview">Architecture Overview<a href="https://docs.getaurora.dev/blog/aurora-2025#architecture-overview" class="hash-link" aria-label="Direct link to Architecture Overview" title="Direct link to Architecture Overview" translate="no">​</a></h2>
<p>As mentioned, we are currently refactoring how our images are made. We have been working with our <a href="https://projectbluefin.io/" target="_blank" rel="noopener noreferrer" class="">Bluefin friends</a> to streamline our builds. At some point, we noticed that we are mostly 1:1 in features, so why spend time duplicating every feature in both codebases.</p>
<p>Aurora and Bluefin are combinations of a set of configuration OCI containers which are then shipped on different images. Originally, the Aurora repository had everything we needed and was a result of organic growth.</p>
<p>We want to share as much of the general code with <a href="https://projectbluefin.io/" target="_blank" rel="noopener noreferrer" class="">Bluefin</a> and <a href="https://bazzite.gg/" target="_blank" rel="noopener noreferrer" class="">Bazzite</a> as possible. We share many things and we wanted a cleaner way to do this. So the new architecture looks like this:</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="oci-containers">OCI Containers<a href="https://docs.getaurora.dev/blog/aurora-2025#oci-containers" class="hash-link" aria-label="Direct link to OCI Containers" title="Direct link to OCI Containers" translate="no">​</a></h3>
<p>We refactored a large amount of our packaging to ship as OCI containers instead of rpms. This moves us away from classic distribution packaging and towards a more cloud native approach.</p>
<ul>
<li class=""><a href="https://github.com/get-aurora-dev/common" target="_blank" rel="noopener noreferrer" class="">get-aurora-dev/common</a> - Aurora specific things live here</li>
<li class=""><a href="https://github.com/projectbluefin/common" target="_blank" rel="noopener noreferrer" class="">projectbluefin/common</a> - Most of the opinions on distro experience is here<!-- -->
<ul>
<li class=""><code>ujust</code>, MOTD, service units, CLI configuration, application choices, etc. Most things that have to do with the workload should live in this repo</li>
<li class="">We share this with Bluefin, so we can have the shared things in one central repo</li>
</ul>
</li>
<li class=""><a href="https://github.com/ublue-os/artwork" target="_blank" rel="noopener noreferrer" class="">ublue-os/artwork</a> - Art assets repository, shared with Aurora and Bazzite</li>
<li class=""><a href="https://github.com/ublue-os/brew" target="_blank" rel="noopener noreferrer" class="">ublue-os/brew</a> and associated <a href="https://github.com/ublue-os/homebrew-tap" target="_blank" rel="noopener noreferrer" class="">ublue-os/homebrew-tap</a>
<ul>
<li class="">these provide Homebrew itself and our selection of custom brew packages. Thanks to those of you who have been helping homebrew be better on Linux, it's <strong>amazing</strong>!</li>
</ul>
</li>
</ul>
<p>These containers have the advantage of making consumption by other bootc projects trivial and are (mostly) distribution agnostic. Custom images now have a granular option to pick and choose the components they want to ship instead of dealing with one monolithic experience. The common repository is structured to be extensible; check out our <a href="https://github.com/get-aurora-dev/common/blob/main/Containerfile" target="_blank" rel="noopener noreferrer" class="">Containerfile</a> to get a flavor of how things are shipped. This allows the team to keep configuration centralized while providing customization points for downstream projects.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-streamlined-maintainable-set-of-images">A Streamlined, Maintainable Set of Images<a href="https://docs.getaurora.dev/blog/aurora-2025#a-streamlined-maintainable-set-of-images" class="hash-link" aria-label="Direct link to A Streamlined, Maintainable Set of Images" title="Direct link to A Streamlined, Maintainable Set of Images" translate="no">​</a></h3>
<p>Decoupling the images this way allows us a more streamlined development experience. It has already enabled us to delete a bunch of duplicated code and makes maintenance easier for the team, while allowing a simpler path for people to contribute and reconcile parity issues between the images. Maintaining Aurora happens in the common OCI layers and not as much in the image repositories.</p>
<p>This also gave us the opportunity to clean up a bunch of old justfiles and scripts that have not been looked at for <em>years</em>. We have been taking a less-is-more approach by shipping less customizations as <code>ujust</code> recipes.</p>
<p>Thanks for your patience with this transition. It did take longer than expected but we took our time because we're focusing on long-term maintenance.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="discord-server">Discord Server<a href="https://docs.getaurora.dev/blog/aurora-2025#discord-server" class="hash-link" aria-label="Direct link to Discord Server" title="Direct link to Discord Server" translate="no">​</a></h2>
<p>As Aurora and our sister projects Bluefin and Bazzite have grown, we have seen a huge uptick of users in our combined Universal Blue Discord server and things started to feel a little crowded. After discussing with our Bazzite friends, we decided a reorganization was in order and we now we have our own <a href="https://discord.getaurora.dev/" target="_blank" rel="noopener noreferrer" class="">Aurora Discord Server</a>. The original server has been rebranded as the Bazzite server, but all of the Universal Blue development channels will still remain the place for collaboration across all of the Universal Blue projects.</p>
<p>So if you are interested chatting about Linux and specifically Aurora stuff, please join us @ <a href="https://discord.getaurora.dev/" target="_blank" rel="noopener noreferrer" class="">https://discord.getaurora.dev</a></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="looking-forward-in-2026">Looking Forward In 2026<a href="https://docs.getaurora.dev/blog/aurora-2025#looking-forward-in-2026" class="hash-link" aria-label="Direct link to Looking Forward In 2026" title="Direct link to Looking Forward In 2026" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="release-channels">Release Channels<a href="https://docs.getaurora.dev/blog/aurora-2025#release-channels" class="hash-link" aria-label="Direct link to Release Channels" title="Direct link to Release Channels" translate="no">​</a></h3>
<p>Our images will still be based on Fedora, but we are looking into a CoreOS-inspired workflow for "releases". For what this could look like, check out <a href="https://docs.projectbluefin.io/blog/unifying-bluefin" target="_blank" rel="noopener noreferrer" class="">Bluefin's post</a> for an in depth discussion. Our current thinking is that the <code>:stable</code> stream would stay as it is, but we will add a <code>:testing</code> and <code>:next</code> stream, similar to CoreOS.</p>
<h4 class="anchor anchorTargetStickyNavbar_Vzrq" id="changes-and-rationale">Changes and Rationale<a href="https://docs.getaurora.dev/blog/aurora-2025#changes-and-rationale" class="hash-link" aria-label="Direct link to Changes and Rationale" title="Direct link to Changes and Rationale" translate="no">​</a></h4>
<p>At first this looks like a rename, so let's go over the changes:</p>
<ul>
<li class=""><code>aurora:next</code> - all changes will land here first. We make no stability guarantees. It will build daily. This will not replace <code>aurora:latest</code> because we will for sure break things in here. This will build at least daily and every time a change lands</li>
<li class=""><code>aurora:testing</code> - When changes in <code>:next</code> have been tested by at least one person they queue up to land in testing. We anticipate things to sit in here for a week or two at a minimum unless we need to fix a regression. This builds daily.</li>
<li class=""><code>aurora:stable</code> - This is effectively the current version of Fedora, except all changes going into this will have at least be vetted by the previous branches.</li>
</ul>
<p>We do NOT have this promotion process today. This is the goal. If you are on <code>aurora:latest</code> we will point you to <code>aurora:stable-daily</code> so that you are still getting daily builds. We purposely are not moving you to <code>next</code> because that will be volatile. Both the <code>next</code> and <code>testing</code> branches will be opt in.</p>
<p>So that is the plan. But we don't currently have any set date when (and if) this would be happening. Unfortunately we are a small team and we cannot commit to specific dates at the moment. Currently, we are targeting around the F44 release cycle or after.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-about-the-lts">What about the LTS?<a href="https://docs.getaurora.dev/blog/aurora-2025#what-about-the-lts" class="hash-link" aria-label="Direct link to What about the LTS?" title="Direct link to What about the LTS?" translate="no">​</a></h3>
<p>Do you remember the Aurora LTS version from way back? Well unfortunately that never happened because of technical hurdles. And once again, our resources were very limited and the current team at that time didn't have the time or "need" to actually create and maintain LTS version of Aurora.</p>
<p>Recently, friend of the project <a href="https://github.com/hanthor" target="_blank" rel="noopener noreferrer" class="">James</a> has been tinkering with the idea and has a working version of Aurora LTS based on CentOS, just like Bluefin LTS. We won't make any promises how this will pan out in the end, but hopefully we can at some point release it to live next to the current Fedora based images.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="bazaar-takes-over-with-f44">Bazaar Takes Over With F44<a href="https://docs.getaurora.dev/blog/aurora-2025#bazaar-takes-over-with-f44" class="hash-link" aria-label="Direct link to Bazaar Takes Over With F44" title="Direct link to Bazaar Takes Over With F44" translate="no">​</a></h3>
<p>With Fedora 44 coming up in Spring 2026 there will be a change regarding our application stores. We have allowed the use of Discover as a replacement but starting with F44, it is time to let it go and make Bazaar the only Flatpak store on Aurora.</p>
<p>Bazaar has seen great amount of development and we have a great relationship with the development team. Now that Aurora is using the Flatpak version of Bazaar (which is the only official version), we will get improvements and bugfixes immediately after they are released on Flathub instead of manually needing to sync and maintain our own rpm versions.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="developer-experience">Developer Experience<a href="https://docs.getaurora.dev/blog/aurora-2025#developer-experience" class="hash-link" aria-label="Direct link to Developer Experience" title="Direct link to Developer Experience" translate="no">​</a></h2>
<p>In 2026 we will be also looking into incorporating <code>aurora-dx</code> features without the need for a separate image and give you more flexibility moving forward:</p>
<ul>
<li class="">Our plan is to add <code>containerd</code> to the image, which will also bring in Docker so everything works out of the box, there will not be a need to do the adduser mumbo jumbo; we'll take care of that for you.</li>
<li class="">How we'll accomplish this transition is still a bit up in the air, so consider this one a slow burn.</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="curated-experiences">Curated Experiences<a href="https://docs.getaurora.dev/blog/aurora-2025#curated-experiences" class="hash-link" aria-label="Direct link to Curated Experiences" title="Direct link to Curated Experiences" translate="no">​</a></h3>
<p>We are putting in effort to have less stuff baked into the images and instead provide curated experiences through Bazaar for Flatpaks and <a href="https://github.com/Valkyrie00/bold-brew" target="_blank" rel="noopener noreferrer" class="">Bold Brew</a> for command-line apps. Shout out to <a href="https://github.com/Valkyrie00" target="_blank" rel="noopener noreferrer" class="">Vito Castellano</a> for continuing to improve the Linux brew experience with Bold Brew!</p>
<p><img decoding="async" loading="lazy" src="https://github.com/user-attachments/assets/59e24766-0885-4fc8-a6e9-87339672487c" alt="image" class="img_ev3q"></p>
<p>The first category of curated experiences is our <a href="https://github.com/projectbluefin/common/blob/main/system_files/shared/usr/share/ublue-os/homebrew/ide.Brewfile" target="_blank" rel="noopener noreferrer" class=""><code>ide</code></a> offerings, which provides a selection of VSCode, Codium, and Jetbrains toolbox for graphical IDEs, as well as <code>nvim</code>, <code>helix</code>, and <code>micro</code> for you CLI nerds.</p>
<p>The <a href="https://github.com/projectbluefin/common/blob/main/system_files/shared/usr/share/ublue-os/homebrew/experimental-ide.Brewfile" target="_blank" rel="noopener noreferrer" class=""><code>experimental-ide</code></a> selection includes the individual JetBrains products if you prefer to install those one-by-one, as well as <a href="https://antigravity.google/" target="_blank" rel="noopener noreferrer" class="">Antigravity</a> and <a href="https://cursor.com/" target="_blank" rel="noopener noreferrer" class="">Cursor</a>. These will be promoted to the production tap as we get more feedback. We've also started to add [Swift tools] into the list so that we can tap into this exciting open source community!</p>
<p>Thanks to the new <a href="https://docs.getaurora.dev/blog/consolidation" target="_blank" rel="noopener noreferrer" class="">Flatpak support in Brewfiles</a> we can ship all sorts of combinations now!</p>
<p>And finally, thanks to our <a href="https://github.com/ublue-os/homebrew-tap" target="_blank" rel="noopener noreferrer" class="">custom tap</a> we are investigating on how to bring <code>aurora-cli</code> to MacOS, so that you can have these same convenience tools on multiple operating systems. James <a href="https://github.com/hanthor/bluefin-cli" target="_blank" rel="noopener noreferrer" class="">has a prototype</a> that you can check out.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="aimachine-learning-tools">AI/Machine Learning Tools<a href="https://docs.getaurora.dev/blog/aurora-2025#aimachine-learning-tools" class="hash-link" aria-label="Direct link to AI/Machine Learning Tools" title="Direct link to AI/Machine Learning Tools" translate="no">​</a></h3>
<p>Our <a href="https://github.com/projectbluefin/common/blob/main/system_files/shared/usr/share/ublue-os/homebrew/ai-tools.Brewfile" target="_blank" rel="noopener noreferrer" class="">AI Toolset</a> continues to expand. I'd like to highlight <a href="https://block.github.io/goose/" target="_blank" rel="noopener noreferrer" class="">goose</a> as a tool that I have been really digging into lately. Its donation to the <a href="https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-agentic-ai-foundation" target="_blank" rel="noopener noreferrer" class="">Agentic AI Foundation</a> makes this a great choice for your local LLM/CLI needs.</p>
<p>We've also added <a href="https://developers.openai.com/codex/cli/" target="_blank" rel="noopener noreferrer" class="">Codex</a>, <a href="https://github.com/features/copilot/cli" target="_blank" rel="noopener noreferrer" class="">Copilot CLI</a>, <a href="https://github.com/google-gemini/gemini-cli" target="_blank" rel="noopener noreferrer" class="">Gemini</a>, <a href="https://lmstudio.ai/" target="_blank" rel="noopener noreferrer" class="">LM Studio</a>, <a href="https://github.com/mistralai/mistral-vibe" target="_blank" rel="noopener noreferrer" class="">Mistral Vibe</a> and <a href="https://qwenlm.github.io/qwen-code-docs/" target="_blank" rel="noopener noreferrer" class="">Qwen Code</a> to the list. Please continue to send us feedback on the tools you use.</p>
<div class="theme-admonition theme-admonition-info admonition_xJq3 alert alert--info"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 14 16"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 0 1 1.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"></path></svg></span>Thanks Docker!</div><div class="admonitionContent_BuS1"><p>You'll find the new <a href="https://www.docker.com/blog/docker-model-runner-universal-blue/" target="_blank" rel="noopener noreferrer" class="">Docker model plugin</a> included too. Huge shoutout to the folks at Docker for working with us!</p></div></div>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="other-goodies">Other Goodies<a href="https://docs.getaurora.dev/blog/aurora-2025#other-goodies" class="hash-link" aria-label="Direct link to Other Goodies" title="Direct link to Other Goodies" translate="no">​</a></h2>
<p>And here's the stuff that doesn't fit anywhere else in this report!</p>
<ul>
<li class="">Powerwash is here! - <code>ujust powerwash</code> is now in alpha and ready for testing - use this command if you want to blow away the data on your PC for donation. This wraps the <code>bootc install reset --experimental</code> command for convenience behind some confirmation dialogs. Be careful with this one! Check the <a href="https://bootc-dev.github.io/bootc/experimental-install-reset.html" target="_blank" rel="noopener noreferrer" class="">bootc documentation</a> for more info</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="metrics">Metrics<a href="https://docs.getaurora.dev/blog/aurora-2025#metrics" class="hash-link" aria-label="Direct link to Metrics" title="Direct link to Metrics" translate="no">​</a></h2>
<p>On to the numbers! First off let's look at our critical upstreams. This level of growth confirms our decision to trust in systems that prioritize application developers.</p>
<ul>
<li class=""><a href="https://flathub.org/en/year-in-review/2025" target="_blank" rel="noopener noreferrer" class="">Flathub 2025 year in review</a> - 20.3% Year over Year Growth, and [Bazaar] continues to get better all the time.</li>
<li class=""><a href="https://formulae.brew.sh/analytics/os-version/365d/" target="_blank" rel="noopener noreferrer" class="">Homebrew Yearly Statistics</a> - Bluefin (#11), Bazzite (#12), and Aurora (#15) have a strong showing in homebrew usage</li>
</ul>
<p>Aurora metrics can be found from <a href="https://insights.linuxfoundation.org/" target="_blank" rel="noopener noreferrer" class="">LFX Insights</a> which we started using this year. Here is our <a href="https://insights.linuxfoundation.org/project/aurora/contributors" target="_blank" rel="noopener noreferrer" class="">contributor metrics</a> and some charts. We have also crossed the 2k weekly users milestone.</p>
<p><img decoding="async" loading="lazy" src="https://github.com/user-attachments/assets/c1359b27-a04b-4ca4-82b7-ca669890c653" alt="aurora" class="img_ev3q"></p>
<p><img decoding="async" loading="lazy" src="https://github.com/user-attachments/assets/d096c0bf-4dea-4dca-a3d5-d41c8ac80bd9" alt="contributors" class="img_ev3q"> <img decoding="async" loading="lazy" src="https://github.com/user-attachments/assets/3d93c1f3-eb12-44c5-bd0f-08fef60e0c2b" alt="issues" class="img_ev3q"> <img decoding="async" loading="lazy" src="https://github.com/user-attachments/assets/611291de-4cea-4b20-8050-8f0dcc5b2109" alt="commits" class="img_ev3q"></p>
<p>Also don't forget to check out <a href="https://insights.linuxfoundation.org/project/ublue-os-bluefin" target="_blank" rel="noopener noreferrer" class="">Bluefin</a> and <a href="https://insights.linuxfoundation.org/project/ublue-os-bazzite" target="_blank" rel="noopener noreferrer" class="">Bazzite</a> too!</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="development-roadmapish">Development Roadmap(ish)<a href="https://docs.getaurora.dev/blog/aurora-2025#development-roadmapish" class="hash-link" aria-label="Direct link to Development Roadmap(ish)" title="Direct link to Development Roadmap(ish)" translate="no">​</a></h3>
<p>Here's some important dates (these are preliminary)</p>
<ul>
<li class="">January 2026 - Transition to the common OCI containers is complete</li>
<li class="">April 2026 - Upgraded to Fedora 44 base</li>
<li class="">Spring 2026 - Aurora LTS (tentatively, no promises!)</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="see-you-in-2026">See you in 2026<a href="https://docs.getaurora.dev/blog/aurora-2025#see-you-in-2026" class="hash-link" aria-label="Direct link to See you in 2026" title="Direct link to See you in 2026" translate="no">​</a></h2>
<p>This ended up longer than anticipated, thank you for joining us in 2025, and we look forward to working with you in 2026! And lastly if you've made it this far and still want more backstory, make sure you check out this interview with Michael Tunnell:</p>
<iframe width="560" height="315" src="https://www.youtube.com/embed/K6-GMTq2T7s?si=Z9Ivj6O3Fgcqh_zj" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin"></iframe>]]></content:encoded>
            <author>aurora@sl.loota.org (Juha Uotila)</author>
            <author>me@nhaiden.io (Niklas Haiden)</author>
        </item>
        <item>
            <title><![CDATA[Backend changes - flatpak support in brew and some other changes]]></title>
            <link>https://docs.getaurora.dev/blog/consolidation</link>
            <guid>https://docs.getaurora.dev/blog/consolidation</guid>
            <pubDate>Tue, 16 Dec 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Consolidating our builds]]></description>
            <content:encoded><![CDATA[<p>Just a quick update on the last few weeks. We have continued to streamline our build pipeline and today we have mostly finished the biggest parts of the work.</p>
<p>Our coneheads have always had a bond with dinosaurs so we have worked with the bluefin people on most of this stuff.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="flatpak-support-in-brewfiles">Flatpak support in Brewfiles<a href="https://docs.getaurora.dev/blog/consolidation#flatpak-support-in-brewfiles" class="hash-link" aria-label="Direct link to Flatpak support in Brewfiles" title="Direct link to Flatpak support in Brewfiles" translate="no">​</a></h2>
<p>I won't go over everything, there is a great post by Jorge on the <a href="https://docs.projectbluefin.io/blog/flatpak-support-in-brewfiles" target="_blank" rel="noopener noreferrer" class="">bluefin blog</a> about some of the things that have been in Bluefin for few weeks.</p>
<p>Flatpak support in Brewfiles is here! You can now manage your Flatpak applications alongside your Homebrew formulae, casks, and other dependencies in a single Brewfile.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="sharing-is-caring---consolidating-ujust-brew">Sharing is caring - Consolidating ujust, brew<a href="https://docs.getaurora.dev/blog/consolidation#sharing-is-caring---consolidating-ujust-brew" class="hash-link" aria-label="Direct link to Sharing is caring - Consolidating ujust, brew" title="Direct link to Sharing is caring - Consolidating ujust, brew" translate="no">​</a></h2>
<p>As Aurora and Bluefin are mostly 1:1 on features it kind of makes sense to consolidate parts of our images. There is no reason why we should do the same things twice in both projects</p>
<p>So coming next week to stable (<code>stable-daily</code> and <code>latest</code> are already enjoying these starting today), our ujust recipes, homebrew and also our artwork have been moved to a new <a href="https://github.com/get-aurora-dev/common" target="_blank" rel="noopener noreferrer" class="">repo</a>. Bluefin has done the same and has their own repo <a href="https://github.com/projectbluefin/common" target="_blank" rel="noopener noreferrer" class="">here</a>.</p>
<p>The idea here is that our ujust recipes, brew files and project artwork can be much more easily managed. From now on, we don't have to upkeep "a copy" of ujust recipes in our own repos, we can just streamline this and pull them from Bluefin.</p>
<p>Also all of the artwork from both projects can be now found in the <a href="https://github.com/ublue-os/artwork/" target="_blank" rel="noopener noreferrer" class="">artwork repo</a>. More info and installation instructions can be found <a href="https://docs.projectbluefin.io/blog/huntress-holiday-wallpapers" target="_blank" rel="noopener noreferrer" class="">here</a>.</p>
<p>Same thing with Homebrew, the common brewfiles that we would still use are maintained in the Bluefin repo and we pull them from there. So there is just one common place where we can maintain these and don't need to copy them over to our own files.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="easier-homebrew-installation-for-custom-images">Easier Homebrew installation for custom images<a href="https://docs.getaurora.dev/blog/consolidation#easier-homebrew-installation-for-custom-images" class="hash-link" aria-label="Direct link to Easier Homebrew installation for custom images" title="Direct link to Easier Homebrew installation for custom images" translate="no">​</a></h2>
<p>We've created a new repository to make it much easier to add Homebrew to your custom bootc images. <a href="https://github.com/projectbluefin/brew" target="_blank" rel="noopener noreferrer" class="">@projectbluefin/brew</a> repository provides a pre-packaged OCI container image that bundles everything you need to add Homebrew to your custom image-based systems. This is an evolution of a long journey to integrate homebrew better onto our Linux systems. Instead of manually setting up Homebrew, configuring services, and managing shell integrations, you can now include everything with a single line in your Containerfile.</p>
<div class="language-dockerfile codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-dockerfile codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token plain">COPY --from=ghcr.io/projectbluefin/brew:latest /system_files /</span><br></span></code></pre></div></div>
<p>On first boot, the <code>brew-setup.service</code> automatically extracts Homebrew to <code>/var/home/linuxbrew/.linuxbrew</code>, sets up proper permissions, and makes it ready to use. The image also includes timers for automatic updates and upgrades, keeping your Homebrew installation current.</p>
<p>This removes a bunch of the manual stuff you had to do in your template to get the full thing, now it's much easier and reliable for everyone. Once we're done the container will rebuild after a Homebrew release, keeping us up to date and safe!</p>
<p>Check out the repository at <a href="https://github.com/projectbluefin/brew" target="_blank" rel="noopener noreferrer" class="">github.com/projectbluefin/brew</a> for more information and examples.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="other-stuff">Other stuff<a href="https://docs.getaurora.dev/blog/consolidation#other-stuff" class="hash-link" aria-label="Direct link to Other stuff" title="Direct link to Other stuff" translate="no">​</a></h2>
<p>There are still updates happening and we keep working on in the following weeks with these.</p>
<p>We will have something "bigger" to announce a little bit later, hopefully maybe already next week but its still a secret ;)</p>
<p>Happy Holidays and we'll see you in the next one!</p>]]></content:encoded>
            <author>aurora@sl.loota.org (Juha Uotila)</author>
        </item>
        <item>
            <title><![CDATA[Stargazer 4 - Winter is coming (and F43 hits stable)]]></title>
            <link>https://docs.getaurora.dev/blog/stargazer-4</link>
            <guid>https://docs.getaurora.dev/blog/stargazer-4</guid>
            <pubDate>Wed, 12 Nov 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Stable F43 builds]]></description>
            <content:encoded><![CDATA[<p><img decoding="async" loading="lazy" src="https://github.com/user-attachments/assets/f36f5e8e-2b5d-4ef1-bb97-97da0d62e185" alt="stargazer4-banner" class="img_ev3q"></p>
<p>A couple of weeks have went by from our <a href="https://universal-blue.discourse.group/t/stargazer-3-aurora-october-update/10911/" target="_blank" rel="noopener noreferrer" class="">last update</a>. And Winter is indeed coming, atleast here in the North <!-- -->😄</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="fedora-43-based-images-are-now-available">Fedora 43 based images are now available<a href="https://docs.getaurora.dev/blog/stargazer-4#fedora-43-based-images-are-now-available" class="hash-link" aria-label="Direct link to Fedora 43 based images are now available" title="Direct link to Fedora 43 based images are now available" translate="no">​</a></h2>
<p><code>Aurora-stable</code> has today been updated and is now based on Fedora 43. Unfortunately this time the update took a little longer than we would have hoped, we had to wait for ZFS to get support for the new 6.17 kernel series.</p>
<p>Fedora 43 is a "minor" update and doesn't bring many big updates in itself but we have still done some backend work on the Aurora side. Changes are mostly uninvasive as KDE Plasma 6.5 has been here for a while already and just to make our source more light and easier to manage.</p>
<p>We also have a new fall wallpaper
<img decoding="async" loading="lazy" src="https://i.imgur.com/WY1eoLx.jpeg" alt="Yes we are very funny now by showing a fall wallpaper" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="refactoring-the-build-pipeline">Refactoring the build pipeline<a href="https://docs.getaurora.dev/blog/stargazer-4#refactoring-the-build-pipeline" class="hash-link" aria-label="Direct link to Refactoring the build pipeline" title="Direct link to Refactoring the build pipeline" translate="no">​</a></h2>
<p>Most of the work this cycle has been to our build pipeline. We have made some cleanup how we build our images. The work is mostly done but there are some small things that we still need to do, but this is mostly backend stuff so won't really show up for end users.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="bazaar-changes">Bazaar changes<a href="https://docs.getaurora.dev/blog/stargazer-4#bazaar-changes" class="hash-link" aria-label="Direct link to Bazaar changes" title="Direct link to Bazaar changes" translate="no">​</a></h2>
<p>As we mentioned in our <a href="https://universal-blue.discourse.group/t/stargazer-3-aurora-october-update/10911/" target="_blank" rel="noopener noreferrer" class="">last update</a>, one of the biggest changes is regarding Bazaar, the Flathub appstore.</p>
<p>We have now fully moved to the Flatpak version of Bazaar, which provides us more frequent updates as it is now decoupled from the image. Furthermore it is now easier to help upstream to get issues fixed for everyone.</p>
<p>This brings some changes how Bazaar is integrated into the system. On startup Bazaar will automatically be downloaded, it is only a couple MBs big. Depending on your installed applications it may also download the new GNOME 49 Flatpak Runtime, which is a bit larger in size (500MB). During the download you may notice a missing icon on the Panel where Bazaar used to be located. Do not worry, when the download has finished it will appear again and is ready to be used.</p>
<p>We tested this change extensively in our Beta Stream in cooperation with <a href="https://projectbluefin.io/" target="_blank" rel="noopener noreferrer" class="">Bluefin</a>.</p>
<p><img decoding="async" loading="lazy" src="https://i.imgur.com/Cr9pbR6.png" alt="Bazaar Dev Section" class="img_ev3q"></p>
<p>Nevertheless, if you notice any issues feel free to reach out to us. Thanks!</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="application-changes">Application changes<a href="https://docs.getaurora.dev/blog/stargazer-4#application-changes" class="hash-link" aria-label="Direct link to Application changes" title="Direct link to Application changes" translate="no">​</a></h2>
<p>We replaced <a href="https://flathub.org/en/apps/io.github.input_leap.input-leap" target="_blank" rel="noopener noreferrer" class="">InputLeap</a> with <a href="https://flathub.org/en/apps/org.deskflow.deskflow" target="_blank" rel="noopener noreferrer" class="">Deskflow</a> as it is more actively developed and is therefore better suited for our default set of applications.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="goodbye-to-nvidia-legacy-and-hwe">Goodbye to nvidia-legacy and HWE<a href="https://docs.getaurora.dev/blog/stargazer-4#goodbye-to-nvidia-legacy-and-hwe" class="hash-link" aria-label="Direct link to Goodbye to nvidia-legacy and HWE" title="Direct link to Goodbye to nvidia-legacy and HWE" translate="no">​</a></h2>
<p>As we progress and grow there are somethings that have to be deprecated and as stated <a href="https://universal-blue.discourse.group/t/aurora-stable-is-now-based-on-fedora-42/8463#p-22443-deprecation-notices-5" target="_blank" rel="noopener noreferrer" class="">previously this year</a>, the old "nvidia-legacy" images (<code>aurora-nvidia*</code>) and all HWE images (<code>aurora-hwe*</code>) are now deprecated and won't receive any more updates.</p>
<p>Depending on your hardware we recommend you to rebase to the -nvidia-open images (for current nvidia users - only Turing cards and newer) or to the base images (HWE users).</p>
<p>We will have a new tool created called <a href="https://github.com/ledif/eol-rebaser" target="_blank" rel="noopener noreferrer" class="">eol-rebaser</a> that will automatically rebase users that are on an end-of-life image to a supported image.</p>
<p>The tool itself will ship with an upcoming update, but it will be configured to perform the automated rebase 1 month after the images become end-of-life to allow plenty of time for users to manually intervene if they wish to rebase to a different OS (maybe Bazzite!).</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="vfio--kvmfr">vfio &amp; kvmfr<a href="https://docs.getaurora.dev/blog/stargazer-4#vfio--kvmfr" class="hash-link" aria-label="Direct link to vfio &amp; kvmfr" title="Direct link to vfio &amp; kvmfr" translate="no">​</a></h3>
<p>We have also removed the kvmfr module and the vfio ujust scripts. These were removed from our akmods repo when Bazzite moved to building them on their own infra.
These are also in "stale" state currently and Hikari is working on a new version of these, so they might come back if we deem them to be important (we are not making any promises though).</p>
<p>If you need these, we recommend you go with a custom image with these added, or rebase to Bazzite as that will keep supports them.</p>
<p>Someone from the community made <a href="https://github.com/dmhuisma/aurora-dmhuisma" target="_blank" rel="noopener noreferrer" class="">this custom image</a> for themselves that adds this functionality back. If you are interested then you might want to get in touch with them.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="font-changes">Font changes<a href="https://docs.getaurora.dev/blog/stargazer-4#font-changes" class="hash-link" aria-label="Direct link to Font changes" title="Direct link to Font changes" translate="no">​</a></h2>
<p>We have also made changes for font handling. Before we had few packages for fonts in the image, which are now removed. We recommend to get fonts from <a href="https://formulae.brew.sh/cask-font" target="_blank" rel="noopener noreferrer" class="">Brew</a> going forward.</p>
<p>You can use our recipe to get the fonts: <code>ujust aurora-fonts</code></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="live-isos-with-the-new-webui">Live ISOs with the new WebUI<a href="https://docs.getaurora.dev/blog/stargazer-4#live-isos-with-the-new-webui" class="hash-link" aria-label="Direct link to Live ISOs with the new WebUI" title="Direct link to Live ISOs with the new WebUI" translate="no">​</a></h2>
<p>With Fedora 43 we finally can build our Live ISO installer with the new Anaconda WebUI and have a working webUI installer in KDE Plasma. Previously there were issues with keyboard layout that couldn't be switched from US layout, which then caused issues with LUKS passwords for non-US layout users.</p>
<p>These new ISO images should make the install part more faster and it looks nicer too. Oh and they should be a little bit smaller in size as well.</p>
<p>Download the WebUI ISO:</p>
<p><a href="https://dl.getaurora.dev/aurora-stable-webui-x86_64.iso" target="_blank" rel="noopener noreferrer" class="">Intel/AMD</a></p>
<p><a href="https://dl.getaurora.dev/aurora-nvidia-open-stable-webui-x86_64.iso" target="_blank" rel="noopener noreferrer" class="">Nvidia-open</a></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="growth">Growth<a href="https://docs.getaurora.dev/blog/stargazer-4#growth" class="hash-link" aria-label="Direct link to Growth" title="Direct link to Growth" translate="no">​</a></h2>
<p><img decoding="async" loading="lazy" src="https://raw.githubusercontent.com/ublue-os/countme/refs/heads/main/growth_aurora.svg" alt="image" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="closing-words">Closing words<a href="https://docs.getaurora.dev/blog/stargazer-4#closing-words" class="hash-link" aria-label="Direct link to Closing words" title="Direct link to Closing words" translate="no">​</a></h2>
<p>We hope you enjoy your new shiny F43 based images. If you find bugs or issues, please always report them to our Github repo: <a href="https://github.com/ublue-os/aurora/issues" target="_blank" rel="noopener noreferrer" class="">https://github.com/ublue-os/aurora/issues</a></p>
<p>It doesn't matter how small they are. If you think there is an issue, let us know. Also if you think you have a good idea for a feature or enhancement for a current feature, report it there as well.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="support-aurora-by-donating-to-people-we-depend-on">Support Aurora by donating to people we depend on<a href="https://docs.getaurora.dev/blog/stargazer-4#support-aurora-by-donating-to-people-we-depend-on" class="hash-link" aria-label="Direct link to Support Aurora by donating to people we depend on" title="Direct link to Support Aurora by donating to people we depend on" translate="no">​</a></h2>
<p><a href="https://ko-fi.com/chandeleer" target="_blank" rel="noopener noreferrer" class="">@chandeleer</a> and <a href="https://ko-fi.com/kolunmi" target="_blank" rel="noopener noreferrer" class="">@kolunmi</a> have been doing spectacular work on the wallpapers and Bazaar for the past few months.</p>
<p>Please consider donating to both of them and of course all the <a href="https://docs.getaurora.dev/project-docs/credits/#upstream-projects-included-in-aurora" target="_blank" rel="noopener noreferrer" class="">other projects</a>!</p>]]></content:encoded>
            <author>aurora@sl.loota.org (Juha Uotila)</author>
        </item>
        <item>
            <title><![CDATA[Welcome to the Aurora Blog]]></title>
            <link>https://docs.getaurora.dev/blog/hello-aurora-blog</link>
            <guid>https://docs.getaurora.dev/blog/hello-aurora-blog</guid>
            <pubDate>Tue, 11 Nov 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[The first post on this blog!]]></description>
            <content:encoded><![CDATA[<p>Hello stargazers, welcome to this first post on the Aurora Blog!! Exciting things to follow.</p>
<p>We finally enabled the Blog Feature on Docusaurus and now we can better inform you all about our new things that happen in Aurora, so exciting!</p>
<p>Lots more to come!</p>
<p>Happy stargazing
~ Niklas</p>]]></content:encoded>
            <author>me@nhaiden.io (Niklas Haiden)</author>
        </item>
    </channel>
</rss>