How does the crew’s work on dependency upgrades reach main?

Tares moves dependency upgrades to main the same way it moves any other ticket. A builder works on its own branch and opens a pull request, the reviewer posts its verdict on it, and the builder merges once the reviewer passes it and CI is green. Without a releaser, the ticket ends at merged on main.

How it works

A dependency upgrade is a ticket in a Tares project, so it follows the crew’s normal path. The factory is a software factory for Claude Code: every member of the crew is a Claude Code session running in the background on your machine.

• Plan. You write the plan with tares factory spec. It becomes a Tares project with milestones, tickets and an AGENTS.md. The upgrade is one of the tickets.
• Hand out. The orchestrator hands out the work and starts builders, one per milestone and repo of a project.
• Branch and pull request. The builder takes the ticket, works on its own branch and opens a pull request. It pushes and opens the pull request with your gh login.
• Review. The reviewer reviews every pull request to a fixed bar and posts its verdict on the pull request.
• Merge. The builder merges its pull request once the reviewer passes it and CI is green.

Tares reads the pull request, CI and merge state of every ticket itself, so the ticket’s stage on Tares follows what happens on GitHub. Tares keeps the plan, the tickets, every review and the assumptions the crew made. If a session restarts, the crew carries on from that record.

Set it up

Local Tares is shown here. On Tares Cloud, run tares login instead of tares up and tares mcp, and choose Connect GitHub in your workspace settings. The order below does not change.

1. Check that Claude Code is signed in on a plan that allows background sessions. Check that gh is signed in with write access to the repos the crew works in, and that git, jq and curl are installed.
2. Install the CLI and start Tares locally.
3. In a second terminal, start the MCP endpoint every crew session shares. On a local Tares the crew reaches Tares only through it.
4. Give Tares access to GitHub under Settings > GitHub, so it can read the pull request, CI and merge state of each ticket.
5. Bring up the crew. The first run asks how far the crew may go, including whether it merges on its own after review and green CI (recommended) or waits for your yes.
6. Plan the project, with the upgrade as a ticket, and say yes when asked whether to hand it to the crew.

uv tool install tares     # or: brew install glassflow/tap/tares
tares up
tares mcp --transport streamable-http
tares factory crew up
tares factory spec "what you want to build"

Run tares factory doctor at any point to check everything the crew needs. The full walkthrough is on Get started.

What you get

• Each upgrade lands as a reviewed pull request on its own branch, never as a direct push to main.
• The reviewer holds the upgrade to the same fixed bar as every other change, and its verdict sits on the pull request.
• The merge waits for a passing review and green CI.
• You are pulled in only for decisions that are yours. Questions reach you one at a time in the orchestrator’s session, each with a recommendation. Attach to it with tares factory crew attach orchestrator.
• The Crew page in the Tares console shows each project’s builders and the pull requests waiting for review.
• The assumptions the crew made are written down, so you can check them at the end of each milestone.
• If you want a say in the merge itself, a single project can wait for your yes before every merge, even when the rest of the crew merges on its own.
• tares factory crew halt stops merges, pushes and new sessions until tares factory crew resume.

When something else fits

• If you want an upgrade tagged and deployed after it merges, ask for the releaser. Without one, tickets end at merged on main.
• If you would rather work on a project yourself than hand it to the crew, run tares factory session to build it in your own Claude Code session, still on Tares.
• If the work is small and needs no plan, that session path is lighter than bringing up a crew.

Related