Hey there,
v1.5.0 just rolled off hot from the press. This diary is to replace the Dev Diary: Build 22 diary.
In these diaries, the team talks about some of the progress we made. It's a great way to stay on track about important changes, overhauls, but also how we operate.
Click follow to stay informed 😉

v1.5.0 - Satin Bowerbird

---

📣 The Release

---

We are happy to announce the release of v1.5, bringing you a large set of changes, additions and improvements, this was a large release with a significant amount of effort, some of the highlights:

• 👍️ Likes are now listed on user profiles (flarum/framework#3528).
• 🙋 Admins can specify if users are able to like their own posts (flarum/framework#3534).
• ⚠️ A warning is displayed on the admin page if debug mode is ON (flarum/framework#3590).
• 🗑️ Users can delete all their notifications (flarum/framework#3529).
• 🌐 Discussions now support UTF-8 slugs through a new slug driver (flarum/framework#3606).
• 🛑 Email change, email confirmation, and password reset endpoints are now throttled (flarum/framework#3555).
• 📁 Assets are published after clearing the cache (flarum/framework#3564).
• 🔔 Users can specify if they want notifications when not caught up (flarum/framework#3503).
• 🖥️ Some PHP 8 compatibility issues are fixed (flarum/[email protected]07b2f86, flarum/[email protected]b01b75e).
• 🪟 Developers can stack modals (flarum/framework#3456).
• 🖌️ Developers can add custom Less variables through a new extender (flarum/framework#3530).
• 🐛 Many bugs have been squashed.
• ♿️ Accessibility improvements have been made.
• 🧑‍💻 And much much more...

👨‍💻 For Developers

---

Extensions compatible with 1.4 should still operate on Flarum 1.5 without any changes. Unless you are overriding component views, directly manipulating the DOM, or changing core behavior through service providers you might need to adapt your code.

⤴️ 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 or 1.4 to 1.5, 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.5.0, and any errors to their fullest.

😇 Thanks to our Sponsors

---

Financial donations keep Flarum alive and kicking. The following companies and people deserve credit for making Flarum sustainable:

• @glowingblue
• Sridhar Kamma
• @linc
• Carlos Tabora
• @BartVB
• Circuit Dojo
• @davwheat
• Seaborn
• Leon Kükel
• SKruIJ
• Timotheus Pokorra
• Edmilerad
• ange1k
• Gregor Hammerschmidt, @askvortsov, Paulina, Jai Gupta, @tankerkiller125, Zou Guoqing, Miguel A. Lago, Soobin Rho, PapaFig1, Nsustain

Thanks for being awesome 😍 !

🙇‍♀️ 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:

• The non-team contributors that usually tackle unplanned, but extremely welcomed bugs or overhauls. We absolutely love contributions that help us move forward, so thank you very much:
  @Kylo @rob006 @JasperVriends @datlechin @soobinrho.
• Documentation contributions: red0888, @soobinrho,
• The core and staff team contributors, people that have vast knowledge of the code base who sacrifice their free time to bring the awesome Flarum software to you, for free. Thank you so much:
  @askvortsov @SychO @davwheat @luceos @ianm @clarkwinkelmann @Deebug
• The community staff is the foundation to a warm and welcoming community. Many cheers for all you do:
  @jordanjay29 @Prosperous @GreXXL @katos @tankerkiller125
• The well oiled machine that is the translation team, keeping up with new languages, their maintainers and the translations perfectly well. Very, very much appreciated:
  @GreXXL @Justoverclock @rob006
• A great shout out to everyone who's submitted carefully described issues and suggestions, especially:
  @mikedugan @orschiro @Kakifrucht.
• 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.

v1.4.0 is out, this build targets v1.5.0.
Subscribe to this discussion for development updates 😉

Releasing new versions of Flarum in a timely manner has been one of the hardships we, as a team, have been facing for years. The releases started to gradually span apart as the team battled to get to stable.

• beta 2 took 1 month
• beta 3 (with 4) took 1.5 months
• beta 5 took 5 months
• beta 6 took 7 months
• beta 7 took almost 9 months
• beta 8 took 1 year and 5 months
• beta 9 took 7 months

Feeling the pain of our users, the community and embracing the excitement people have for stable, it was time for change.
Inspired by GitLab and Agile methodologies, we found our solution in a fixed release cycle. No matter the tasks in this release, we target a specific release date. Even though we initially decided to hold off until a stable release, with our recent boost in motivation we decided to go for it now and use beta 10 as our testing grounds.
A few of the principles that we relied on:

• Target the release on a specific date in two months.
• Feature freeze (issues) one week before release.
• Freeze pull request merging three days before release.
• Allow QA and discuss-powered testing during the feature freeze phase. We use nightly.flarum.site, deploy latest changes to discuss and test locally.
• Work Kanban style using one GitHub organisation wide board for the release with the columns Backlog, To Do, In Progress, Review and Done.
• Appoint and rely on the Release Coordinator to keep us aware of our deadlines. For someone adopting a badly scoped position @Ralkage has been doing an awesome job.
• Hold a team meeting every month, in sync with the cycle, so that we can discuss technical and organisational topics regularly and keep our heads pointed in the same direction.

We're still shaping our processes where needed, but I'm already extremely happy with the results we've managed to achieve and I hope you do too too, now that we released beta 10.

v1.4.0 - Echidna

---

📣 The Release

---

We step into the summer 🌅 with another release. Version 1.4 follows within two months of 1.3 to tackle a wide range of bugs and improve extensibility. Many of these improvements are purely internal focused at core, but cascade into the ecosystem through bundled and community extensions.

• 🔗 Rel and target attributes on links can now be modified using extensions (flarum/framework#3455)
• 💦 Long topic titles in the notification dropdown don't overflow (flarum/framework#3500)
• ⛔ Sub tags of tags a user has access to are visible even though the user has no access to those sub tags (flarum/framework#3419)
• 🏷️ Without any tags required the tag modal would be forced on the user regardless (flarum/framework#3448)
• 👮 Once a suspension is over the modal showing the suspension would still be shown (flarum/framework#3449)

• 🧑‍💻 And much much more...

👨‍💻 For Developers

---

All extensions compatible with Flarum 1.3 will work with 1.4. There was no need for an upgrade guide this time. If you receive any bug reports or have questions, feel free to hop onto our Discord into the #extend channel.

⤴️ 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 a version 1 Flarum to version 1.4, 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.4.0, and any errors to their fullest.

😇 Thanks to our Sponsors

---

Financial donations keep Flarum alive and kicking. The following companies and people deserve credit for making Flarum sustainable:

• @glowingblue
• Sridhar Kamma
• @linc
• @hrvoje_hr
• @davwheat
• @jaredwolff
• @matteocontrini
• Donald Broussard
• @BartVB
• @ange1k
• @Edmilerad
• Leon Kükel, @GreXXL, @SKruIJ, Lay Dominicans of bl. Michał Czartoryski, Timotheus Pokorra, Circuit Dojo, @Teddan, PapaFig1, ange1k, jgupta, @askvortsov1, @Wadera, @zgq354, @tankerkiller125, @malago, @Edmilerad

Thanks for being awesome 😍 !

🙇‍♀️ 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:

• The non-team contributors that usually tackle unplanned, but extremely welcomed bugs or overhauls. We absolutely love contributions that help us move forward, so thank you very much:
  @iPurpl3x, @hason, flawedworld
• The core and staff team contributors, people that have vast knowledge of the code base who sacrifice their free time to bring the awesome Flarum software to you, for free. Thank you so much:
  @askvortsov @SychO @davwheat @datitisev @luceos @ianm @clarkwinkelmann
• The community staff is the foundation to a warm and welcoming community. Many cheers for all you do:
  @jordanjay29 @Prosperous @GreXXL
• The well oiled machine that is the translation team, keeping up with new languages, their maintainers and the translations perfectly well. Very, very much appreciated:
  @GreXXL @Justoverclock @rob006
• A great shout out to everyone who's submitted carefully described issues and suggestions, especially @matteocontrini, @ornanovitch and @Valeyard !
• 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.