From 3caee1b328a2dfe6792e0e49f22f1c7566b4f7ef Mon Sep 17 00:00:00 2001
From: Antoine Toussaint
 <312536060+antoinetoussaint-byte@users.noreply.github.com>
Date: Wed, 7 Oct 2026 15:20:13 -0400
Subject: [PATCH] release: v0.0.93
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The module agent's own code changed since v0.0.92 and its version did not.
`gitops.go` gained `AllowModules` on `topologyInterface` in b89af575a (#1025,
landed 2026-10-07 00:25Z; v0.0.92 was cut 2026-10-06 21:27Z), so the GitOps
topology render can now carry `allow-modules`. Tagging v0.0.93 without this bump
would ship that new render under the same agent version string v0.0.92 already
published — two different agent behaviours behind one immutable version, which is
the hazard the deploy-counter recipe's first step exists to prevent
(RELEASE_GATES.md § Release cadence and ownership).

This is step 1 of that recipe; the annotated v0.0.93 tag goes on this commit once
it is on main. The deploy counter and this version are separate axes on purpose —
0.0.46 is the agent's own version, not the tag.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---
 agent.codefly.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/agent.codefly.yaml b/agent.codefly.yaml
index cafd4c69d..7cc96763e 100644
--- a/agent.codefly.yaml
+++ b/agent.codefly.yaml
@@ -1,5 +1,5 @@
 publisher: codefly.dev
 kind: codefly:module
 name: saas-starter
-version: 0.0.45
+version: 0.0.46
 description: "Complete SaaS foundation — auth, multi-tenancy, generated RPC policy, RBAC, impersonation, audit, billing-ready"