From 63278c6c5cb4c8cda451974690613927f1534f13 Mon Sep 17 00:00:00 2001
From: DonalMe <76789979+DonalMe@users.noreply.github.com>
Date: Tue, 3 Mar 2026 13:50:13 -0500
Subject: [PATCH] Handle beta version not yet updated in product-details

For a few days after each release, product-details still reports the old
beta version (e.g. release=149, beta=149, nightly=150) because no Fx150
beta builds have landed yet. This caused get_checked_versions() to fail
its consecutive-version check and return {}, silently disabling the
regression_set_status_flags rule for that window.

When release == beta and nightly == release + 1, we now treat beta as
nightly (N+1) so the rule can continue running.
---
 bugbot/utils.py | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/bugbot/utils.py b/bugbot/utils.py
index 34deeda71..fe722da90 100644
--- a/bugbot/utils.py
+++ b/bugbot/utils.py
@@ -526,6 +526,17 @@ def get_checked_versions():
 
     from . import logger
 
+    if v[0] == v[1] and v[0] + 1 == v[2]:
+        # Beta version not yet updated in product-details after a new release
+        # cycle starts (release=N, beta=N stale, nightly=N+1). Treat beta as
+        # nightly until the first beta builds land and product-details catches up.
+        logger.info(
+            "Beta version not yet updated in product-details, treating beta as %d",
+            v[2],
+        )
+        versions["beta"] = str(v[2])
+        return versions
+
     logger.info("Not consecutive versions in product/details")
     return {}