Skip to content

release: v0.0.94 — callable sources, and the module agent on core v0.18.0 - #1077

Merged
antoinetoussaint-byte merged 2 commits into
mainfrom
release/v0.0.94
Oct 11, 2026
Merged

antoinetoussaint-byte merged 2 commits into
mainfrom
release/v0.0.94

Conversation

@antoinetoussaint-byte

Copy link
Copy Markdown
Contributor

Step 1 of the deploy-counter recipe in RELEASE_GATES.md § Release cadence and ownership, so that v0.0.94 can be tagged. Same shape as #1037.

Why the module agent's version moves

Its own build changed since v0.0.93: the root go.mod moved github.com/codefly-dev/core from v0.5.11-0.20260926231217-d481a2d49683 to v0.18.0 (#1071, #1052), and golang.org/x/net from v0.59.0 to v0.60.0 (#1053). Tagging v0.0.94 without this bump would ship a different agent binary under the version v0.0.93 already published. So 0.0.46 → 0.0.47.

0.0.47 is the module agent's own version, not the deploy counter (#405). The annotated v0.0.94 tag goes on this commit once it is on main.

What v0.0.94 carries (since v0.0.93)

Why not codefly publish

codefly publish patch (CLI v0.1.185) refused in its source-CI pre-flight: multiple compatible source agents advertise languages [go]. It would also have rewritten agent.codefly.yaml from 0.0.46 to 0.0.94, conflating the two axes this recipe keeps apart. Nothing was changed by that attempt.

🤖 Generated with Claude Code

…18.0

Step 1 of the deploy-counter recipe (RELEASE_GATES.md § Release cadence and
ownership): the module agent's own build changed since v0.0.93 — core moved
from a v0.5.11 pseudo-version to v0.18.0 (#1071, #1052) and golang.org/x/net
to v0.60.0 (#1053) — so its version moves 0.0.46 → 0.0.47. 0.0.47 is the
module agent's version, not the deploy counter; the annotated v0.0.94 tag goes
on this commit once it is on main.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@antoinetoussaint-byte
antoinetoussaint-byte added this pull request to the merge queue Oct 11, 2026
Merged via the queue into main with commit 9f6a4aa Oct 11, 2026
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant