Root cause: If multiple connections are opened at the same time after an update, the ui-middleware will do multiple requests to get initial data. That went especially worse, when e2e-tests are launched against ui-middlewares with multiple clients connecting at the same time.
Soltion: Make sure, that a node already caches stuff without a response.

Root cause: configuration was only reloaded on those nodes, that did the version update. The other nodes might not notice that.
Solution: On propagated version changes, the nodes always check for config changes

this now happens directly in the release-it script, so no need
to configure it a second time in package.json

it's just a simple switch, but we want to have it documented for completeness.

this automates a lot of tasks when creating a Changelog entry for the next release.

Change the prefix to reflect the "new" name of the service. May be this even should be configurable at some point.

This is a breaking change.

Root cause: cache keys handled differently when reading/writing
Solution: make sure keys are handled equally

Fixes OXUIB-1528

Root cause: Cross-Origin-Opener-Policy is set to same-origin per default and will prevent parent or window.opener to be set
Solution: Set Cross-Origin-Opener-Policy to same-origin-allow popups

during startup the ui-middleware might need some more memory, so we adjust the actual limit to something larger.

Use redirect instead of delivering index.html to prevent /ui paths in the future

Root cause: There are middlewares, which still use old redirects to /ui
Solution: To prevent 404s, we just serve the index.html