update changelog

CHANGELOG.md

@@ -8,7 +8,6 @@
 - `nflow-engine`
   - Throw `StateVariableValueTooLongException` if a state variable value that does not fit into the database column is detected. Checked in `StateExecution.setVariable`, `StateExecution.addWorkflows`, `StateExecution.addChildWorkflows`, `WorkflowInstanceService.insertWorkflowInstance` and when creating a new or updating an existing instance via REST API.
     If the exception is thrown during state processing and not handled by the state implementation, nFlow engine will catch the exception and retry state processing after delay configured by property `nflow.executor.stateVariableValueTooLongRetryDelay.minutes` (default is 60).
-    REST API will return HTTP 400 in case the state variable value is too long.
   - Fix honoring of `includeCurrentStateVariables` flag in `WorkflowInstanceService.listWorkflowInstances`. This caused major slowness when using bulk workflows.
     To preserve the existing (incorrect) default behaviour in backwards compatible way the default value in `QueryWorkflowInstances.Builder` is changed to `true`. The REST API is unaffected.
     Especially in workflows with many children that use the `StateExecution.getAllChildWorkflows` method the performance impact can be high. Before 7.0.0 release, it is recommended to use `StateExecution.queryChildWorkflows(new QueryWorkflowInstances.Builder().setIncludeCurrentStateVariables(false).build())` if state variables are not needed.
@@ -19,6 +18,9 @@
     - spotbugs 4.0.0-beta4
     - spotbugs-annotations 4.0.0-beta4
     - swagger 1.6.0
+- `nflow-rest-api`
+  - REST API returns HTTP 400 in case the state variable value is too long when inserting a new or updating an existing workflow instance
+  - Exception mappers return JSON objects instead of raw strings
 - `nflow-explorer`
   - Dependency updates:
     - angular 1.7.9