# Discourse 3.0 is Here!

**URL:** <https://meta.discourse.org/t/discourse-3-0-is-here/251372>\
**Category:** Blog\
**Created:** [January 11, 2023, 6:07am UTC](https://meta.discourse.org/t/discourse-3-0-is-here/251372 "2023-01-11T06:07:40Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Alexander](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alexander/32/497634_2.png) [@Alexander](https://meta.discourse.org/u/Alexander)\
**Post date:** [January 12, 2023, 1:32pm UTC](https://meta.discourse.org/t/discourse-3-0-is-here/251372/5 "2023-01-12T13:32:29Z")

</div>

There are few and rare times that breaking changes are introduced in my opinion, Discourse goes through a lot of tests, when possible breaking changes are going to be introduced (for example in some method in the Rails code or javascript) usually throws a warning in the console, for example:  
“`someMethod is deprecated since Discourse vX.X, use x instead. Removal in Discourse vX.Y.Z`”

I don’t think I’ve ever seen such stable software, and with all the facilities in the world to update almost without complications, no need to even worry about migrations or precompiling assets 😃 (As long as the official guides are used)

---

_[View the full topic](https://meta.discourse.org/t/discourse-3-0-is-here/251372)._