NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
gg_multi manages multi package workspaces and supports orchestrated editing and publishing
Last release today
06 Oct 2026
Ships fairly regularly
a new release about every 9 days
Most releases are documented
notes for 51 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
4 months old
92 releases · first in 2026
One column per month.
Remove doublicate cli output when adding organisations
Support projects without manifest: ProjectType.none, checks skipped, version tracked as git tag only
Delete ticket and remote feature branches by default
Nothing published for this version
gg_multi: changed references to git
Nothing published for this version
Forward --pr and --no-pr to gg_one so ticket publishes merge via auto-merge pull requests by default
Print repos added to a ticket in blue instead of green - gg do checkout included
gg do checkout included.gg/* instead of the whole .gg directory, so .gg/.gg.json and .gg/.ticket.json stay trackableAdd rc prerelease channel to gg do publish (channel field/flag, X.Y.Z-rc.N computation, npm --tag rc, single + multi repo)
The delete-ticket and merge-message default prompts fail fast with an actionable error when stdin is not a terminal (via gg_one's throwWhenNotATermina
.gg/.gg-publish.json (or pass -m /
--config) for headless runs.do configure-publish: new command that interactively writes /.gg/.gg-publish.json (per-repo version increment + merge message, plus one delete_ticket
do configure-publish: new command that interactively writes
<ticket>/.gg/.gg-publish.json (per-repo version increment + merge
message, plus one delete_ticket choice). do publish runs it
automatically when started without a config, so every interactive
decision is made up front before the unattended publish.do publish --continue: records per-repo progress in
.gg/.gg-publish.json, skips already-published repos and resumes the
rest after a failure; the file is deleted on full success. Review /
can publish are re-run unless at least one repo already published.
Within a repo, resume: true is forwarded to gg_one's do publish,
which resumes at the first open step of its repo-level
<repo>/.gg/.gg-publish.json (done_steps) — including the version
tag. The full-restore rollback deletes that repo-level file (its
markers would be stale); the keep-commits rollback keeps it, and
--reconfigure discards ticket and repo-level files. Each repo's
.gitignore gets the .gg/.gg-publish.json entry automatically
before the pre-publish commit.do publish --reconfigure: discards an existing .gg/.gg-publish.json
and reconfigures interactively.--continue also skips review/can-publish when
a failed repo's own step file proves irreversible progress (first-repo
failure after registry publish/merge no longer blocks the resume);
--config and do configure-publish refuse to clobber a runtime file
that still holds progress markers.do publish --message / -m is kept, with refined meaning: it is the
default merge message used only when the .gg/.gg-publish.json is
written interactively (a fresh run or --reconfigure). It seeds every
repo's merge-message prompt and takes precedence over the ticket
description. It is ignored once a config exists or is supplied via
--config. do configure-publish accepts the same -m.do review and do publish now roll back the repository state when they fail, restoring the snapshot taken before the run. do review restores every chan
do review and do publish now roll back the repository state when
they fail, restoring the snapshot taken before the run. do review
restores every changed, not-yet-pushed repo; do publish restores only
the failed repo — fully when nothing irreversible happened, otherwise
keeping all commits so a re-run resumes. The shared git runner and
snapshot capture live in backend/git_snapshot.dart.gg_multi: changed references to git
Org-prefixed repo folders: repos newly added to the master workspace are cloned into _ (Dart) / - (TypeScript) folders, so same-named repos from diffe
<org>_<repo> (Dart) / <org>-<repo> (TypeScript)
folders, so same-named repos from different organizations can coexist.
Existing unprefixed folders keep working: do add, do rm, ticket
copies and transitive-dep cloning now resolve repos by folder name,
manifest package name or git remote URL (RepoFolderResolver).do add <name> now tries the known organizations from .organizations
first and uses the bare <name>/<name> guess only as a last resort, so
a plain add clones straight from the right org without a failed attempt.can publish now runs gg can publish for every repo in the ticket
(feature branch, CHANGELOG, pana, npm authentication), so publish
blockers — like a missing npm login for an npm-published package —
surface up front instead of as a cryptic 404 mid-publish.do review (and therefore do publish) now disables pnpm 11's
blockExoticSubdeps while refreshing dependencies, so the transitive
git-referenced dependency chain that localizing to git feature branches
creates installs instead of failing with ERR_PNPM_EXOTIC_SUBDEP. This
matches the fix do publish already applied to its own refresh step.do review now surfaces a failed install's output from stdout when
stderr is empty (pnpm writes its errors to stdout), instead of throwing
the cause-less ... (pnpm install failed: ).gg can commit and gg do push (commit
c97a31a). Restores the previous sequential implementation.Nothing published for this version
Preserve dependency constraint operator (^^/~/exact) through publish
gg_multi: changed references to git
Build dependency graph across Dart and TypeScript bridge repos
gg_multi: changed references to git
feat(ts): version-pinned git deps via #semver: + tag-push for npm/pnpm
feat(do review): integrate the remote feature branch before pushing to avoid non-fast-forward rejections; on a real rebase conflict it aborts cleanly
can review fuehrt vor dem Uncommitted-Check dart pub get --offline aus (analog gg_one can commit, mit Status-Printer)
Revertiere die Parallelisierung von 'gg can commit' und 'gg do push' (Commit c97a31a). Die vorherige sequentielle Implementierung wird wiederhergestel
Nothing published for this version
Nothing published for this version
gg_multi: changed references to git
gg_multi: changed references to git
### Changed - parallelization - documentation
Nothing published for this version
gg_multi: changed references to git
gg_multi: changed references to git
kidney_core to gg_multi.
Repository moved to https://github.com/ggsuite/gg_multi. Update
dependencies: entries and import 'package:kidney_core/...'
statements to import 'package:gg_multi/...'. The executable is now
gg_multi (previously kidney_core).gg ^7.0.5 with gg_one ^8.0.0
(the gg package itself was renamed to gg_one upstream)..kidney_status to .gg_multi_status.
Existing checked-out workspaces must rename the file or run the
localization commands again.Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →