Signed-off-by: Niklas <nscuro@protonmail.com>

… `null`

Fixes #3296

Signed-off-by: nscuro <nscuro@protonmail.com>

…t dependencies

Fixes #3295

Signed-off-by: nscuro <nscuro@protonmail.com>

Backport: Fix notifications not being sent for child projects where `active` is `null`

Backport: Fix NPE in VersionDistancePolicyEvaluator when project has no direct dependencies

Updating an existing `ProjectMetadata#authors` value fails due to a DataNucleus-internal casting error.

Signed-off-by: nscuro <nscuro@protonmail.com>

…uthors` field

Fixes #3309

Signed-off-by: nscuro <nscuro@protonmail.com>

Signed-off-by: nscuro <nscuro@protonmail.com>

Without the version field there is a NullPointerException

See #3299 

Signed-off-by: Kristóf Havasi <lnksz@users.noreply.github.com>

Backport: Fix `ClassCastException` when updating an existing `ProjectMetadata#authors` field

fixes #3299

Signed-off-by: Jadyn Emma Jäger <jadyn@jadyn.dev>

The timestamp is created with value `null` in a context where L2 caching is enabled (`DefaultObjectGenerator`), but updated in one where L2 caching is disabled (`NistApiMirrorTask#updateLastModified`). What's more, it's queried in a context with L2 caching enabled (`NistApiMirrorTask#inform`). This causes the property to be updated, but the cache not being invalidated, thus still serving queries.

To not have similar inconsistencies in other areas of the application, re-enable L2 caching when updating the property.

Eventually, L2 caching should be disabled system-wide.

Signed-off-by: nscuro <nscuro@protonmail.com>

Backport: Fix NVD API's last modified timestamp requiring restart to be applied

Backport: Improve Error handling and add default version type

Signed-off-by: nscuro <nscuro@protonmail.com>

Add changelog for v4.10.1

Signed-off-by: nscuro <nscuro@protonmail.com>