* The `discretionary_policy` command does not accept the `planner_discount_latex_name` option, contrary to what the documentation says (bug fixed in preprocessor@f7917e9bd4369f25a20ce81e617014fdfe4f5718)
* The `discretionary_policy` command does not accept the `planner_discount_latex_name` option, contrary to what the documentation says (bug fixed in preprocessor@f7917e9bd4369f25a20ce81e617014fdfe4f5718)
* The `outfile` option of the `smoother2histval` command would produce an incorrect file on models with two lags or more, leading to incorrect results when loading that file with `histval_file` (bug fixed in 618712ad9fb9a128545ae9ee8ca01ca2900a3af9)
* The `outfile` option of the `smoother2histval` command would produce an incorrect file on models with two lags or more, leading to incorrect results when loading that file with `histval_file` (bug fixed in 618712ad9fb9a128545ae9ee8ca01ca2900a3af9)
* The point forecasts triggered by `forecast` option of `estimation` did not take shock uncertainty into account (bug fixed in f03929f3)
* The point forecasts triggered by `forecast` option of `estimation` did not take shock uncertainty into account (bug fixed in f03929f3)
* The `nodecomposition` option of `estimation` did not suppress all variance decompositions (bug fixed in 6d2828287bf04f7e85369d99fcc69e411f24ad91)
* The `example1_reporting.mod` file was broken (bug fixed in b3e7d59b)
* The `EndTemperature` option of `mode_compute=10` (`simpsa`) was broken (bug fixed in d802ed7c)
* Optimization may in rare cases erroneously apply an infinite penalty function value (bug fixed in 46809c41)
* Using the `forecast` command with a model solved at `order=2` with `varexo_det`, Dynare would return uncertainty bands based on a first-order approximation (bug not fixed, see #1940)
* Using the `forecast` command with a model solved at `order=2` with `varexo_det`, Dynare would return uncertainty bands based on a first-order approximation (bug not fixed, see #1940)
* The results of mode-finding were not correctly stored in `oo_.posterior_mode` for shock and measurement error correlations (bug fixed in 7a8d8539)
* The results of mode-finding were not correctly stored in `oo_.posterior_mode` for shock and measurement error correlations (bug fixed in 7a8d8539)