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:
π¨βπ» 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:
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.