NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
The convenient dart & flutter developer command line, bundling the gg_one tool family into one CLI.
Last release 11 days ago
23 Sep 2026
Ships fairly regularly
a new release about every 2 weeks
Most releases are documented
notes for 51 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
4 months old
75 releases · first in 2026
One column per month.
do configure-publish: new command that interactively writes /.gg/.gg-publish.json (version increment + merge message; -m presets the message). do publ
do configure-publish: new command that interactively writes
<repo>/.gg/.gg-publish.json (version increment + merge message; -m
presets the message). do publish runs it automatically when started
without a resolved configuration, so all interactive decisions happen
before the unattended publish. The command also makes sure
.gg/.gg-publish.json is listed in .gitignore (appending and
committing the entry once per repo).do publish --continue / --reconfigure: per-step publish progress
(done_steps: prepare_version, publish_registry, merge, tag) is
recorded in .gg/.gg-publish.json and a failed publish resumes at the
first open step — including the version tag, which the old hash-based
state could silently skip. A leftover progress file makes a plain
re-run refuse until --continue or --reconfigure is chosen. The file
stores the feature branch (trusted only when resuming) and is deleted
after a fully successful publish. On resume, the hash-keyed
did commit check still runs, so raw commits added after the failure
are never published unvalidated; the feature-branch deletion is
idempotent and re-runs; when the merge is already done, the default
branch is checked out before the first push. do configure-publish
refuses to overwrite a file that carries done_steps (code review).DoPublish.exec accepts resume: so gg_multi do publish --continue
resumes each repo at its open step.PublishConfig: done_steps + branch runtime fields with
withStepDone/isStepDone/hasStepProgress; new
EnsurePublishConfigIgnored tool; GgState.ignoreFiles now excludes
.gg/.gg-publish.json from content hashes.DoPublish no longer takes versionSelector /
editMessage — both prompts live in the injectable
DoConfigurePublish now. The publish-step resume no longer uses the
hash-keyed doPrepareVersion/doPublishPubDev/doMerge GgState keys;
doPublish/doCommit are still written for did publish and the
pre-push hook.feat: merge via auto-complete pull request on protected main (Azure) and wait until merged
npm-logged-in: resolve the package's actual publish registry (publishConfig.registry → @scope:registry → default registry) and run whoami against that
publishConfig.registry → @scope:registry → default registry) and run
whoami against that registry, instead of always checking npmjs.org. This
makes the check work for Azure DevOps, GitHub Packages and other private
registries. Registries without reliable whoami support (e.g. Azure
DevOps) are skipped gracefully instead of failing the check — the auth is
verified for real at publish time.feat(gg): interactive npm publish + npm-logged-in precheck; package.json prepublishOnly->build->test rules (bridges exempt from build->test); do revie
Preserve dependency constraint operator (^^/~/exact) through publish
gg_multi: changed references to git
Add 'package-json-scripts' check to can commit: TypeScript projects (incl. bridges) must declare test/build/lint/prepublish in package.json, and prepu
gg_multi: changed references to git
feat(ts): version-pinned git deps via #semver: + tag-push for npm/pnpm
feat: language-universal commit/publish via gg_lang (isDartFamily gating, lockFileFor, registry-aware dispatch)
CanCommit: dart pub get --offline (or the Flutter equivalent) now runs as a regular check below the Can commit? header and is logged as Running "dart
CanCommit: dart pub get --offline (or the Flutter equivalent) now runs as
a regular check below the Can commit? header and is logged as
Running "dart pub get --offline", matching the style of the other checks
(was framed with »« and printed above the header).gg to gg_one and moved the repository to
https://github.com/ggsuite/gg_one. The previous history (versions
up to and including 7.0.5) lives at https://github.com/ggsuite/gg
at commit 9141ef54f5edac470d119a39285813299143898f.gg_multi: changed references to git
gg_multi: changed references to git
gg_multi: changed references to git
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →