v1.1 was just released 🥳
Time for a new dev diary, with the hopes of making this a bit more active than the last one 👍️

v1.1.0 - Platypus

---

• ‼️ New spoiler and strike-through buttons for Markdown
• 🦶 Post footers are now hidden when empty, reducing whitespace
• 🗜️ Code blocks now have a maximum height
• 🤖 Accessibility improvements for search, checkboxes, and icons
• 🎨 New theme extenders to override entire Less files
• ⏱️ New frontend asset preloading extender, used by default to preload FontAwesome, JS and CSS
• 🙈 New no-JS admin dashboard, for when that pesky extension breaks everything
• 🙆 Replaced usernames with display names in more places
• 💻️ Various frontend typing improvements for developers
• ℹ️ php flarum info now shows your forum MySQL version
• 🐛 Loads more bug fixes
• 🆕 ...and much more!

📣 The release

---

Woah, how time flies! It feels like just last week that we hit Flarum's 1.0 stable milestone. But now another release cycle has passed, and we're happy to welcome to the stage (trumpet noises)... Flarum 1.1! 🎺 🎉
A fair bit has changed with Flarum in 1.1. We've been mainly focusing on bugfixes, extensibility and developer improvements, along with a sprinkling of accessibility.
Most extensions should face no breaking changes, but those with deep integration into the frontend may have some slight hiccups before they're updated for 1.1.
For a full list of changes, check out our changelog and upgrade guide.

👨‍💻 For Developers

---

Most extensions should be ready-to-go on Flarum 1.1 out of the box. If you're overriding component views, or directly manipulating the DOM, you might need to implement some minor changes in some areas.
For theming, we have switched to CSS custom properties wherever possible. You can finally remove your horrible !important properties from your colour modifications, and switch to the applicable custom property overrides. Check out the pull request for more info.

⤴️ Upgrading

---

Before you upgrade, make sure to create a backup of your public/assets directory, your composer.json and your database!

Before starting the upgrade process, ensure you are on Flarum 1.0.0 or above in your Admin Dashboard or by typing php flarum info. If you're not, use the previous release notes for upgrading from an earlier version.
To upgrade from 1.0 to 1.1, take a look at our upgrade guide documentation. The process should be much easier compared to previous major version upgrades, due to the lack of breaking changes.

If you run into any issues, please open a new discussion under the Support tag. Ignore similar discussions, and open a new one anyhow. Make sure to mention the output of php flarum info, composer why-not flarum/core v1.1.0 and any errors in their fullest.

🙇‍♀️ Acknowledgements

---

Flarum wouldn't be the same without our over one hundred contributors, along with their generous time commitments! For this release we specifically thank these wonderful people:

• Contributors: @lhs_azevedo @ornanovitch @pierres @Kylo @iPurpl3x @clarkwinkelmann @ianm @Ralkage @rafaucau (contributions list)
• Documentation contributions: yibum nexxai @iPurpl3x @Justoverclock @clarkwinkelmann @Jorc0 NeroBlackstone @matteocontrini BaseMax SkyShi123 @GreXXL @Cadiducho corydozen @Dizy (contributions list)
• Core Developers: @askvortsov @SychO @davwheat @datitisev @tankerkiller125 @luceos
• Quality Assurance: @katos @Deebug @ianm
• Community Staff: @jordanjay29 @meetdilip @Prosperous @Pollux @Kyrne
• Translation team: @GreXXL @Justoverclock @rob006
• Everyone who's submitted carefully described issues and suggestions.
• And the whole community sharing their passion for Flarum, urging us on!

🆘 Support the Project

---

We need your support to:

• Guarantee continued development on the software.
• Create a valuable ecosystem around the project.
• Ensure healthy extensions are available.

You can support us:

• 👕 By getting some swag from our merchandise store!
• 💵 By backing us on Open Collective or on GitHub.
• 👩‍💻 By contributing to the source code, hop onto any of our open issues.
• 📈 By creating your own Flarum extensions and sharing them with the world!
• 🌎 By translating Flarum and extensions into your own language.
• 💝 By sharing your love for Flarum with friends, family and on the internet.
• 💬 By hanging out with us, here on discuss!

If you're looking to get coding, make sure to check out our documentation.

🔮 What now?

---

We're currently planning our kick-off meeting for build 19 (v1.2), as well as discussing future roadmaps and strategy ready for v2. Hopefully, we'll have a roadmap for v2.0 up soon!
There might be a couple of minor patches between v1.1 and v1.2 where we address minor bugs, so keep an eye out for those.

Please note that discuss has recently undergone maintenance, as such some images and files may not be loading or may be missing while they get moved.
Further real-time WebSocket's may not be working properly and there may be some delays in emails and/or other queued notifications.
Edit: Maintenance is complete and everything is working as expected as far as we are aware.

This discussion acts as a way for people to subscribe to announcements on releases. Before stable we would announce releases as separate discussions, because all changes were bundled and released as one beta.
Having passed that milestone we have already released several patch releases for v1.0. These releases were announced either in the v1.0 release announcement or in the Dev Diary. We felt this is not the right place.
From now on we will announce ALL releases, no matter the size, in this discussion. 🔔 So make sure to follow.

• ⏰ Releases for Flarum and all bundled extensions are announced here and/or linked to.
• 🔇 Comments are disabled. Please open a discussion for feedback or support.

Previous Release Announcements

• Flarum 1.0.0 Released
• Flarum 1.0.1 Released - minor patches
• Critical security update to Flarum core, with new incident write-up (v1.0.2)

Hello everyone,
As you are probably all aware, we're currently in our v1.2 development cycle, and have started planning for v2.0. As part of this process we hosted our usual "kick off" meeting with our core developers and team members, where we discussed plans for the next release, as well as procedural challenges that are blocking and slowing down progress.
During the past several releases, one of our biggest challenges has been managing the issue backlog on GitHub. There's quite a few reasons for this:

• Basing our milestones on this backlog makes it difficult for us to develop and implement our own vision for the future of the project; instead, we're following the plans of past community members and contributors, many of whom are no longer involved with the project. This is both demotivating for us, and bad for the project, since the issues we're solving aren't necessarily the most important ones at the moment.
• The current state of our milestones are somewhat arbitrary, more a result of "this used to be on milestone n - 1, so we moved it to milestone n" than because those issues are actually high priority.
• A lot of issues are partially complete, or have had conversation devolve into weird tangents and rabbit holes. As a result, starting work on an issue is much more difficult than it needs to be.
• Many issues that have been open for years are no longer relevant. Triaging them to know which ones are and aren't takes up a lot of time.
• Ideally, issues would be use-case driven, such as solving a bug for users, improving some aspect of developer experience, or building a safer API for some feature. Quite a few of our current issues are about obscure technical changes, without a clear use case.
• With ₃₅₀ open issues, even choosing which issues to work on takes up a lot of time and decision paralysis.

And if these issues are causing so much of a headache for our team, which is pretty familiar with Flarum, you can imagine that it's probably much more confusing for new contributors.
We've been talking about improving this situation for a while, and have spent a lot of time closing outdated issues, cleaning up open PRs, and keeping an eye on new issues. Unfortunately, the impact has been minimal, so we have decided to shut down the Flarum project. It's been a pleasure, folks.
That's a joke, of course, but we will be making some drastic changes to our current work organization setup. The main goal here is to ensure that all issues on the GitHub repo are actionable, use-case driven, relevant, and approachable.

• All existing issues will be moved to an archive repo and then closed in core.
  • Archive repo will be closed/deleted in roughly a year after we've pulled issues we feel are important or otherwise needed.
• Documentation on what we consider good issues and PRs will be created and put on our new Internal Docs.
  • Issues and PRs not following our new standards will be closed without further response.
• We will release a roadmap for v2.0 and beyond. Having a roadmap in the past was great for helping both team members and our community remember our long-term vision. We want to bring this back.
• We will create a new tag here on Discuss where "wishlist" / far-off / unconfirmed / unverified bugs, suggestions, and feature proposals can be discussed. The tag will support voting, so the community will be able to indicate which issues matter the most to them. Some of these will be moved to GitHub issues as we decide to work on them / confirm ideas for a technical implementation.
• Depending on some experiments in the coming weeks, we might be moving to a monorepo setup for core and bundled extensions. This would help simplify things by putting all development in one place. There's still a few issues that might block it though.

While these changes may seem drastic we ask that you please understand where we're coming from. The amount of issues and PRs in our GitHub repos results in developer fatigue, which in turn means less new features, less bug fixes and overall slower development for you. For us, the extra paperwork makes us less happy and excited to work on Flarum, which makes it difficult to keep up morale and build a better, bigger team. We've made this decision unanimously as a team because we all believe that this is in the best interest of not just ourselves, but for Flarum as a whole.
We expect these changes to take place sometime within the next few weeks. Once we move to the new system of tracking issues, authors of discussions in the support and feedback tags here on Discuss will be able to request that their discussions be moved to the new community voting tag. Please bear with us during this transition, and feel free to ask any questions below.