From 5e3f07c28aa737545836cb87267cbaaf9ef28c41 Mon Sep 17 00:00:00 2001
From: JSONbored <49853598+JSONbored@users.noreply.github.com>
Date: Thu, 30 Jul 2026 09:23:31 -0700
Subject: [PATCH] chore(release): move the ORB target to 3.7.0 so the beta
 channel resumes
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

orb-v3.6.0 was promoted to stable, which by design stops the beta channel:
`due = commitsSinceLastTag.length > 0 && !targetAlreadyStable`, and the
manifest still targeted the version that just went stable. The due-check has
been reporting `manifestStale: true` and offering `orb-v3.6.0-beta.1` — a tag
that would sort BEHIND the stable release it follows.

44 image-relevant commits have landed since orb-v3.6.0, including a feat
(gate: guardrailEscalation.onCleanReview), so the next target is a minor bump.
With this, the due-check resolves to orb-v3.7.0-beta.1 and the nightly
workflow resumes unattended.

Same one-line move as #9777 did for 3.6.0.
---
 orb-manifest.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/orb-manifest.json b/orb-manifest.json
index 7deec5fbac..b98af094c8 100644
--- a/orb-manifest.json
+++ b/orb-manifest.json
@@ -1,4 +1,4 @@
 {
-  "version": "3.6.0",
+  "version": "3.7.0",
   "description": "Source of truth for the self-hostable loopover-orb container image's target release version (ghcr.io/jsonbored/loopover-selfhost). Bumped by a maintainer when a feat/fix/breaking change since the last stable orb-v tag warrants moving to a new target version -- scripts/orb-release-core.ts and .github/workflows/orb-beta-release.yml read this file to decide what version the next automated beta snapshot targets. Promoting a beta to a stable orb-vX.Y.Z release is still a manual `git tag` -- this manifest only drives the automated beta channel."
 }