From b417cc8a5f9d3799d9f0ac4b9270a4eda6821488 Mon Sep 17 00:00:00 2001 From: Niklas Date: Sun, 7 Jun 2026 19:00:14 +0200 Subject: [PATCH] Relax wording of EPSS re-population delay The task starts a few minutes after startup and usually completes in <30s thanks to batch loading. The current "within hours" wording is overly pessimistic. Signed-off-by: Niklas --- docs/guides/administration/migrating-from-v4.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/administration/migrating-from-v4.md b/docs/guides/administration/migrating-from-v4.md index 2a8cd4d..5df39c6 100644 --- a/docs/guides/administration/migrating-from-v4.md +++ b/docs/guides/administration/migrating-from-v4.md @@ -364,7 +364,7 @@ v4 inactive projects become `INACTIVE_SINCE = '1970-01-01 00:00:00+00'` (Unix ep v4 stored EPSS score and percentile directly on each vulnerability row. v5 stores EPSS in a dedicated table populated from the upstream feed. -The migrator does not copy v4 EPSS values. v5 re-populates them at runtime within hours of first launch. +The migrator does not copy v4 EPSS values. v5 re-populates them at runtime within minutes of first launch. ### Metrics retention