Skip to content

armgit / ruflo

Public Imported from GitHub
0

🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated

chore(release): 3.42.5 + @claude-flow/memory 3.0.0-alpha.25

ruvnetcf9aebf21e1d
diff --git a/CLAUDE.md b/CLAUDE.md
index 4a00e49833..9e531ab656 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -967,8 +967,44 @@ memory_search_unified({ query: "authentication security", limit: 5 })
- The normal public release train is exactly THREE packages:
`@claude-flow/cli`, `claude-flow`, and `ruflo`.
-- Internal `@claude-flow/*` components are bundled into the public artifacts;
- do not publish them standalone as part of the normal release.
+- **Exactly FOUR `@claude-flow/*` components are bundled** into the public
+ artifacts: `security`, `codex`, `mcp`, `plugin-agent-federation` β€” the list
+ is `INTERNAL_RUNTIME_PACKAGES` in `scripts/stage-internal-runtime-bundles.mjs`.
+ These are built from the tagged source and staged into the tarball's
+ `package/node_modules/`, so a source change in them ships with the train.
+ Do not publish those four standalone.
+- **Every OTHER `@claude-flow/*` dependency resolves from the registry**, at the
+ version `v3/@claude-flow/cli/package.json` pins. A source change in one of
+ those does NOT ship with the train β€” the release silently carries the last
+ *published* copy of that package, not the code you just merged. It must be
+ bumped and published standalone in the same release or the fix reaches nobody:
+
+ | dep of `@claude-flow/cli` | bundled? | how a source change reaches users |
+ |---|---|---|
+ | `security`, `codex`, `mcp`, `plugin-agent-federation` | yes | with the train |
+ | `cli-core`, `neural`, `shared`, `memory` | **no** | **standalone publish required** |
+
+ `memory` is the easiest of these to miss, for three compounding reasons: it is
+ the only one on a caret range (`^3.0.0-alpha.23`) rather than an exact pin, so
+ nothing drifts visibly; `v3/pnpm-lock.yaml` resolves it from the registry
+ rather than `link:../memory`, so workspace CI never exercises the CLI against
+ workspace `memory` source; and its own package tests DO run against source, so
+ CI goes green on a change that cannot ship. #3390 (#3327 Finding A) is the
+ worked example β€” it fixed `memory/src/controller-registry.ts` and
+ `cli/src/memory/memory-bridge.ts` together, and without a standalone `memory`
+ publish only the `cli` half would have shipped, leaving the fix inert.
+- Before tagging, check every non-bundled leaf for drift between what the CLI
+ pins and what the workspace source says β€” a mismatch means an unpublished
+ change is about to be skipped by the release:
+
+ ```bash
+ # needs root deps for `semver` β€” run after `npm ci` at repo root
+ node -e 'const semver=require("semver"),c=require("./v3/@claude-flow/cli/package.json"),d={...c.dependencies,...c.optionalDependencies},b=["security","codex","mcp","plugin-agent-federation"];let n_=0;for(const[n,v]of Object.entries(d)){if(!n.startsWith("@claude-flow/"))continue;if(b.includes(n.slice(13)))continue;let w;try{w=require(`./v3/${n}/package.json`).version}catch{continue}n_++;if(!semver.satisfies(w,v,{includePrerelease:true}))console.log(`DRIFT ${n}: cli pins ${v}, workspace source ${w} β€” publish it or the release skips the change`)}if(!n_){console.error("checked 0 leaves β€” check is broken, do not trust a clean result");process.exit(1)}console.log(`checked ${n_} non-bundled leaves`)'
+ ```
+
+ It must use `semver.satisfies`, not a string compare: `memory` is on a range,
+ so a literal match reports a false DRIFT on every release. It also fails loudly
+ at zero leaves checked β€” a guard that inspects nothing must not report clean.
- MUST update ALL dist-tags for ALL THREE packages after publishing (latest + alpha + v3alpha all point to the same version)
- Publish order: `@claude-flow/cli` first, then `claude-flow` (umbrella), then `ruflo` (alias umbrella)
- MUST run verification for ALL THREE before telling user publishing is complete
diff --git a/package.json b/package.json
index fc6805ef44..688db0028f 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
{
"name": "claude-flow",
- "version": "3.42.4",
+ "version": "3.42.5",
"workspaces": [
"v3/@claude-flow/codex",
"v3/@claude-flow/mcp",
diff --git a/ruflo/package.json b/ruflo/package.json
index 5c646b75f0..f131d062d0 100644
--- a/ruflo/package.json
+++ b/ruflo/package.json
@@ -1,6 +1,6 @@
{
"name": "ruflo",
- "version": "3.42.4",
+ "version": "3.42.5",
"description": "Ruflo - Enterprise AI agent orchestration platform. Deploy 60+ specialized agents in coordinated swarms with self-learning, fault-tolerant consensus, vector memory, and MCP integration",
"main": "bin/ruflo.js",
"type": "module",
diff --git a/v3/@claude-flow/cli/package.json b/v3/@claude-flow/cli/package.json
index 2debb9f768..e8d5502ba6 100644
--- a/v3/@claude-flow/cli/package.json
+++ b/v3/@claude-flow/cli/package.json
@@ -1,6 +1,6 @@
{
"name": "@claude-flow/cli",
- "version": "3.42.4",
+ "version": "3.42.5",
"type": "module",
"description": "Ruflo CLI - Enterprise AI agent orchestration with 60+ specialized agents, swarm coordination, MCP server, self-learning hooks, and vector memory for Claude Code",
"main": "dist/src/index.js",
diff --git a/v3/@claude-flow/memory/package.json b/v3/@claude-flow/memory/package.json
index c3a5af6105..275bd8d2a8 100644
--- a/v3/@claude-flow/memory/package.json
+++ b/v3/@claude-flow/memory/package.json
@@ -1,6 +1,6 @@
{
"name": "@claude-flow/memory",
- "version": "3.0.0-alpha.23",
+ "version": "3.0.0-alpha.25",
"type": "module",
"description": "Memory module - AgentDB unification, HNSW indexing, vector search, hybrid SQLite+AgentDB backend (ADR-009)",
"main": "dist/index.js",