This is an overview of the user-visible changes to Catalyst between major
Catalyst releases.
+=head2 VERSION 5.90105
+
+This version primarily fixed a regression in the way we preserved $c->state
+which the previous version introduced. Now in the case when you forward to
+an action, should that action throw an exception it sets state to 0 and is
+sure that the return value is false. This is to meet expected behavior based
+on the documentation. If you relied on the last update behavior you may not have
+regressions but it was thought that we should make the code behave as documented
+for more than 10 years.
+
+We also changed how we compose the request, response and stats base class. We
+now compose the base class with any configured traits once at the end of the
+application setup, rather than for each request. This reduced request overhead
+when you are composing lots of traits. It possible this may break some code that
+was adding traits after the application setup was finalized. Please shout out if
+this actually causes you trouble and we'll do the best to accommodate.
+
=head2 VERSION 5.90102 - 5.90103
A significant change is that we now preserve the value of $c->state from action
-to follwoing action. This gives you a new way to pass a value between actions
+to following action. This gives you a new way to pass a value between actions
in a chain, for example. However any 'auto' actions always have $c->state
forced to be set to 0, which is the way its been for a long time, this way an
auto action is required to return 1 to pass the match. It also exists to maintain
compatibility with anyone that exits an auto action with a detach (which is not a
-documented way to excape matching, but exists in the wild since it worked as a
+documented way to escape matching, but exists in the wild since it worked as a
side effect of the code for a long time).
Additionally, upon $c->detach we also force set state to 0.