gg_one

Changed

• "Quiet
• "Tighten

Changed

• Use ggwsm in pipelines
• Install the dna_ggsuite DNA

Changed

• Rework copyright headers

Fixed

• Cleanup copy right headers. Update to dart 3.13. Auto fixes.
• Cleanup copy right headers. Update to dart 3.13. Auto fixes. Setup quick-check pipeline.

Changed

• Provide gg via npm
• Fix shell changes

Changed

• Refactor commit messages, version increment

Changed

• Make sure »dart pub upgrade --tighten --major-versions« is called before publishing

Removed

• Merge .ticket with ticket.json. Remove usage of .ticket

Changed

• Move gg commit conventions from gg_git to gg_one_core
• Improve commit behavior

Changed

• Extract the state kernel, the check commands and the publish configuration into the new gg_one_core package
• Extract the commit, push, upgrade and ticket flows into the new gg_one_commit package
• Extract MergeFlow, CreatePullRequest, lock files helper and CanMerge into the new gg_one_merge package
• Extract DoPublish, CanPublish, DidPublish and the version tag tools into the new gg_one_do_publish package
• Reduce gg_one to the umbrella CLI; distribute behavior docs into the sub-packages
• Split gg_one into gg_one_core, gg_one_commit, gg_one_merge and gg_one_do_publish
• Port the .gg/gg.json ignore guard from gg_one main into gg_one_core

Removed

• Decouple internals from the gg_one barrel; remove dead code and unused dependencies

Added

• ».gg/gg.json« must not be git-ignored: every command now heals simple .gitignore rules (».gg«, ».gg/«, ».gg/«, a literal ».gg/gg.json«) into the canonical ».gg/« + »!.gg/gg.json« pair and commits the fix — or fails with the manual fix when the rule cannot be rewritten safely

Changed

• Changes to .gg/gg.json are only amended into gg's own »#gg: …« bookkeeping commits. User commits are never rewritten silently; the state lands in a separate »#gg:« commit instead

Fixed

• The first »do publish« in a repository whose .gitignore ignored the whole ».gg/« folder no longer crashes with »git add .gitignore .gg/gg.json failed«

Changed

• Show ticket deletion dialog at the beginning of publish. Recolorize.
• Use overrides in package.json

Changed

• Keep published repos editable in tickets

Added

• »do publish« refuses when the version about to be published is already in CHANGELOG.md and continuing would lose »## Unreleased« entries or the pubspec.yaml version does not match
• The versions in CHANGELOG.md are sorted before publishing. Newest first.

Changed

• Fix issues with CHANGELOG.md

Removed

• Remove duplicate upgrade calls from publish workflow

Changed

• Improve push and publish workflow
• Rename »gg one do upgrade dependencies« into Rename

Added

• Add cached repo test helpers (initCachedRepo, initCachedRepoPair, initCachedGit, initCachedLocalAndRemoteGit); move pushLocalChangesUpstream from gg_one to gg_git; fix stale emoji expectations from gg_status_printer 1.4.2

Changed

• Merge origin/main and tighten dependency constraints (dart pub upgrade --tighten)

Fixed

• Migrate slow git-fixture suites to gg_git cached repo helpers (do_publish -43%, full run -36%)

Changed

• Rename .master to .ocean with automatic migration at next start
• Rename ocean workspace -> ocean

Changed

• Finetune command line output

Changed

• Prevent pubspec.lock interrupting publishing

Fixed

• Fix issues with pubspec.lock

Fixed

• Fix test error paths

Changed

• Improve review workflow

Changed

• dart pub upgrade --major-versions --tighten
• shorten the long CLI messages and share the duplicated ones: one unfinishedPublishMessage, one continueConflictMessage, one editMessage
• use the semantic colors of gg_console_colors: cAction for instructions, cWarn for warnings, cDetail for progress, cCmd/cPath inside a message
• wrap every exception text in cError
• assert the plain text in the tests, not the escape codes (rmC)
• replace the ✓/✗ emoji by the plain marks ✓/✗ — gg_status_printer 1.2.0 colors them via cSuccess/cError
• replace do cancel-review with do review --abort
• refactor: rename publish --reconfigure to --restart
• refactor: shorten all CLI help texts to 60 chars
• Rework CLI texts
• refactor(gg_one): move do upgrade to do upgrade dependencies
• refactor(gg_one): move did upgrade to did upgrade dependencies
• reword all command descriptions to the same terse imperative gg do and gg can already use
• Rework console colors
• Improve cli log and colors

Removed

• refactor(gg_one): remove do maintain command
• refactor(gg_one): remove can checkout from the CLI
• refactor(gg_one): remove can merge from the CLI
• refactor(gg_one): remove can upgrade from the CLI
• refactor(gg_one): remove the check command group from the CLI
• refactor(gg_one): remove do configure-publish from the CLI
• remove do checkout — gg do import ticket covers reproducing a ticket
• Remove unused CLI commands

Added

• CreatePullRequest (lib/src/tools/create_pull_request.dart): opens — or reuses — the pull request of the current feature branch on GitHub/Azure DevOps and returns its url. It is created without auto-merge, so gg_multi do review can open a pull request while the ticket is still being worked on; only do publish adds the auto-merge flag.

Changed

• Create pull request as part of the review

Changed

• Merge main into 71

Fixed

• »gg do create ticket« no longer applies a stash it did not create: »git stash create« probes the worktree first, so a clean worktree skips stashing entirely and a foreign stash entry is never restored into the fresh ticket branch. The own entry is pushed with a »gg:<branch>« message and popped instead of applied, so the stash stack no longer grows with every ticket
• Fix git errors: own stash in create ticket, locale-independent push state

Changed

• Throw an error on unknown gg one sub commands, also if option -h is given
• Throw an error when gg on do publish is called within a ticket repo
• Use gg_args 2.1.0 which reports unknown sub commands itself

Removed

• Remove gg do merge, use gg do publish --merge-only which asks for no version increment

Changed

• Do not upload ticket.json. Share it manually and import it using "gg do checkout"

Changed

• Merge gg one do merge to gg one do publish --merge-only

Removed

• The »gg do merge« command — use »gg do publish --merge-only«, which runs the same flow without version bump, changelog heading, registry upload and tag
• The »DoMerge« class — its merge implementation is now the plain tool »MergeFlow« (lib/src/tools/merge_flow.dart), driven by »DoPublish«

Changed

• Use pubspec_overrides.yaml for git references

Changed

• Fix: Skipping unchanged repos from publishing does not work

Fixed

• Fixes

Changed

• Make sure package is already published in registry before publishing

Added

• Add »gg do merge«

Changed

• #gg: changed references to git
• #gg: changed references to pub.dev

Changed

• Make gg do commit work in main branch using --push

Changed

• Never publish ticket.json

Fixed

• Remove the .gg/ticket.json ticket marker before the version bump and registry upload, so it is no longer shipped to pub.dev/npm inside the published package (previously it was only removed at merge time, after the upload)

Changed

• Do not publish unchanged packages: skip repos without manual changes when no dependency outgrew its published constraint
• Prefix all gg-generated commit messages with "#gg: "; the unchanged-repo check treats such commits as not user generated

Changed

• Don't hide files in .gg folder

Changed

• Don't allow gg do commit in master

Fixed

• do publish now discards publish progress recorded on a different feature branch instead of refusing to run (or, on --continue, silently skipping the version bump and registry upload and merging without publishing). Such progress is a stale leftover that arrived with a copy of the repository — e.g. a ticket copy of the master workspace.
• Fix publishing error

Removed

• Don't delete branches twice. Remove pubspec_override.yaml before publishing

Changed

• No commit in main

Changed

• Support projects without manifest: ProjectType.none, checks skipped, version tracked as git tag only
• do publish removes an already existing tag of the version to be published - locally as well as on the remote - before it tags the release. A publish that failed after tagging left the tag on a commit the retry replaces, which made the tag step refuse to tag ("must be greater ...") or tag an abandoned commit.
• Recreate tags on publishing

Removed

• Removed .gg/.ticket.json before merge muss nicht gelb sein

Removed

• Remove git hooks functionality completely because merging is done via merge requests

Changed

• Delete remote feature branch by default

Added

• do publish now waits after the registry publish until the version is actually visible on pub.dev/npm (via gg_publish's WaitUntilPublished): a message announces the wait incl. a status url, progress is reported and the wait is bounded by a timeout instead of hanging

Changed

• do publish: wait visibly until the version appears on pub.dev/npm
• do publish: keep merge and pull-request wait messages visible
• do merge: sync main fast-forward-only, reset gg-bookkeeping divergence
• Refuse to publish ticket repos with a suppressed publish target
• do publish waits until version is published and pull request is merged

Fixed

• do publish refuses to publish a repo whose publish target is suppressed by the ticket tooling (gg multi do add writes publish_to: none). Before, it silently skipped the registry upload and merged publish_to: none into the main branch — publish the ticket with gg multi do publish instead
• do publish announces a skipped registry upload instead of skipping silently
• do merge passes the pull request's source branch to the wait, so a moved HEAD no longer causes "No pull request found for branch main"
• do merge: updating the local main branch no longer aborts with "You have divergent branches": the pull is fast-forward-only, and when main diverged from origin/main with gg bookkeeping or lock-file drift only, it is reset to origin/main (real local commits still abort with a clear message)

Added

• Add --pr flag (default on): merge via auto-merge pull request and wait, fall back to local merge on unsupported providers, --no-pr restores local merge

Changed

• Forward the merge message into the pull-request flow, drop the doMerge and doPublish states and prune legacy keys from .gg/.gg.json
• Absorb pre-push-hook worktree drift in the pull-request merge flow so the final checkout of main does not fail
• Skip pull request and wait when a resumed run finds the release content already merged into main
• Use the shared origin-url lookup and gg_lang lock-file names and memoize the legacy-key pruning
• gg_multi: changed references to git

Changed

• Accept test in a TypeScript package's prebuild script as fulfilling the build-must-run-test rule
• gg_multi: changed references to git

Fixed

• Ignore .gg/* instead of the whole .gg directory, so .gg/.gg.json and .gg/.ticket.json stay trackable

Removed

• Remove stale root .ticket marker from main - do merge only drops .gg/.ticket.json, so the old marker leaked through squash merges and preset wrong merge messages

Fixed

• Re-release combining the rc prerelease channel (10.2.0) with the do-merge dirty-worktree fix - pub.dev 10.2.1 was published without the rc channel

Changed

• fix(do-merge): commit pending tracked worktree changes before switching branches, so a publish-time formatter (prettier --write reformatting pubspec.yaml) or a gg .gg/.gg.json state write no longer aborts the merge's git checkout <main> with 'local changes would be overwritten'