From 2d447d1f1e890a2e63efe26ca4062a88e5aa755c Mon Sep 17 00:00:00 2001
From: JSONbored <49853598+JSONbored@users.noreply.github.com>
Date: Wed, 29 Jul 2026 01:05:17 -0700
Subject: [PATCH] chore(release): move the ORB target to 3.6.0 so the beta
 channel resumes

orb-v3.5.0 shipped as stable, but orb-manifest.json still declared 3.5.0 as the
target. orb-release-core.ts refuses to cut a beta for a version that already has a
stable tag (targetAlreadyStable), so every nightly orb-beta-release run since has
reported due:false and done nothing -- the beta channel has been silently dormant,
with 73 image-relevant commits accumulated behind it.

The report already said what to do: manifestStale:true, inferredVersion 3.6.0 from
the feat: commits since stable. Bumping the manifest is the deliberate human step
that gate is waiting for -- the automation never bumps it itself.

After this, the report reads due:true, nextTag orb-v3.6.0-beta.1, manifestStale:false.
---
 orb-manifest.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/orb-manifest.json b/orb-manifest.json
index eea9acb12d..7deec5fbac 100644
--- a/orb-manifest.json
+++ b/orb-manifest.json
@@ -1,4 +1,4 @@
 {
-  "version": "3.5.0",
+  "version": "3.6.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."
 }