scriptuser authored 2 years ago and david.bauer committed 2 years ago

Bumps [helmet](https://github.com/helmetjs/helmet) from 5.0.2 to 5.1.0.
- [Release notes](https://github.com/helmetjs/helmet/releases)
- [Changelog](https://github.com/helmetjs/helmet/blob/main/CHANGELOG.md)
- [Commits](https://github.com/helmetjs/helmet/compare/v5.0.2...v5.1.0)

scriptuser authored 2 years ago and david.bauer committed 2 years ago

Bumps [bull](https://github.com/OptimalBits/bull) from 4.8.2 to 4.8.3.
- [Release notes](https://github.com/OptimalBits/bull/releases)
- [Changelog](https://github.com/OptimalBits/bull/blob/develop/CHANGELOG.md)
- [Commits](https://github.com/OptimalBits/bull/compare/v4.8.2...v4.8.3)

scriptuser authored 2 years ago and david.bauer committed 2 years ago

Bumps [ioredis](https://github.com/luin/ioredis) from 5.0.4 to 5.0.6.
- [Release notes](https://github.com/luin/ioredis/releases)
- [Changelog](https://github.com/luin/ioredis/blob/main/CHANGELOG.md)
- [Commits](https://github.com/luin/ioredis/compare/v5.0.4...v5.0.6)

scriptuser authored 2 years ago and david.bauer committed 2 years ago

Bumps [express](https://github.com/expressjs/express) from 4.17.3 to 4.18.1.
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/master/History.md)
- [Commits](https://github.com/expressjs/express/compare/4.17.3...4.18.1)

scriptuser authored 2 years ago and david.bauer committed 2 years ago

Bumps @open-xchange/logging from 0.0.9 to 0.0.11.

Every watcher gets notification anyway

Cache lookups will immediately register a promise to prevent multiple requests for the same ressource

Use correct path for index.html for the memory lookup

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