Lockstep Releases

New

• Uniform (lockstep) versioning for multi-repo projects — You can now release every repository in a project on one shared version number instead of each repo tracking its own. Pick a Version strategy under Release Defaults — Independent (the default, each repo on its own line) or Uniform (lockstep) — globally, per team, or per project. In lockstep mode Trinity takes the highest current version across all your repos, bumps it once (the biggest change anywhere in the set decides patch/minor/major, and a breaking change in any repo raises the whole set to a major), and tags every repository — even ones the release didn't touch — with that single new version, so anyone consuming your code can pin "everything at vX." The release gate's Version bumps tab shows it as one clear "All repos → vX.Y.Z" headline.

Improved

• Onboarding Discuss is grounded in what's on screen — When you open Discuss on a question, a stack item, a suggestions section, or the roadmap, the advisor now sees exactly the subject you're looking at and can read your project's existing decisions and accepted stack. It engages with the actual options and pending picks instead of asking you to restate them, and a roadmap discussion always reflects the latest version after you apply a change.
• Older releases tuck away in the changelog — On this changelog page, older patch releases within a version now collapse behind a "Show older releases" toggle, so the list stays easy to scan as releases pile up.

Fixed

• First git push or clone over SSH works on a fresh machine — Trinity now establishes trust for a host's SSH keys before the first managed git operation, and re-checks after a key rotation, so pushes and clones no longer fail with a host-key error the first time you use a new account or device. A genuinely untrusted key is still rejected.
• Update button stays crisp across themes — Fixed the "update available" pill in the title bar showing stray focus-outline slivers in some themes.