Skip to content

duobrain v0.1.2

Choose a tag to compare

@github-actions github-actions released this 25 Sep 13:06
· 29 commits to main since this release

duobrain v0.1.2

A safety fix for projects that copied duobrain into a folder of their own. Upgrade if duobrain lives
anywhere inside your project other than .duobrain/.

Fixed

  • update could change your project. In v0.1.0 and v0.1.1, running update from a copy inside the
    project's repository (for example tools/duobrain) used Git on the enclosing project: it fetched the
    project and, when the project had its own package.json and a newer upstream commit, fast-forwarded the
    project's branch. It never discarded work, since it only fast-forwards a clean tree, but it moved the
    project without being asked. update now refuses with UPDATE_INSIDE_PROJECT.
  • install run from such a copy records the release as v<version> rather than the project's commit.

Added

  • install --no-agents vendors duobrain without writing AGENTS.md, CLAUDE.md or .gitattributes, for
    teams that maintain their own agent instructions.

If duobrain is in tools/duobrain or a similar folder

Do not run update from that copy with v0.1.0 or v0.1.1. Move to the vendored layout instead:

node tools/duobrain/bin/duobrain.js install      # add --no-agents to keep your own AGENTS.md
git rm -r tools/duobrain
git add .duobrain AGENTS.md CLAUDE.md .gitattributes
git commit -m "chore: vendor duobrain in .duobrain"
node .duobrain/bin/duobrain.js update

See Moving from a copied folder.

Verification

The suite contains 108 tests, including a regression test that reproduces the reported layout: a project
with its own package.json, duobrain copied to tools/duobrain, and a newer partner commit upstream.
update now refuses and the project branch does not move; install from that copy creates .duobrain.