tor-browser

commit 5ba8bd1b9b0d6d3379dcebdafac74c262b4386a5
parent 09afb12e95342e172411ce9cd500c7467b973016
Author: Andrew Halberstadt <ahal@mozilla.com>
Date:   Fri, 19 Dec 2025 19:09:50 +0000

Bug 2006158 - Use 'release_level' utility function when resolving "release" run-on-projects alias, r=releng-reviewers,taskgraph-reviewers,jcristau

There should be only a single implementation that determines whether a project
is release or not.

Differential Revision: https://phabricator.services.mozilla.com/D276708

Diffstat:
M
taskcluster/gecko_taskgraph/util/attributes.py
 | 
4
+++-

1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/taskcluster/gecko_taskgraph/util/attributes.py b/taskcluster/gecko_taskgraph/util/attributes.py
@@ -66,7 +66,9 @@ RUN_ON_PROJECT_ALIASES = {
     "integration": lambda project: (
         project in INTEGRATION_PROJECTS or project == "toolchains"
     ),
-    "release": lambda project: (project in RELEASE_PROJECTS or project == "toolchains"),
+    "release": lambda project: (
+        release_level(project) == "production" or project == "toolchains"
+    ),
     "trunk": lambda project: (project in TRUNK_PROJECTS or project == "toolchains"),
     "trunk-only": lambda project: project in TRUNK_PROJECTS,
     "autoland": lambda project: project in ("autoland", "toolchains"),