gg_publish

Removed

• Retry the remaining git network commands on transient transport errors: RemoveVersionTag's remote tag removal and MergeMainIntoFeat's fetch run through gg_git's GitRetry

Changed

• Count the next version on from the highest version tag on origin and refuse to merge over a tag of the prepared version

Changed

• "Quiet
• "Tighten

Changed

• MainBranch returns the declared default branch of the repository when it has one

Changed

• Keep the build number of pubspec.yaml on publish and count it up: 1.2.4+155 becomes 1.2.5+156

Changed

• Install the dna_ggsuite DNA

Changed

• Use ggwsm in pipelines

Fixed

• Fix Windows-specific test failures that blocked the review

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

Fixed

• Various log and color fixes across the gg command output

Changed

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

Added

• SyncHybridVersions — writes the higher of pubspec.yaml and package.json into both manifests and regenerates the version files. A hybrid has two version numbers describing one artifact, and nothing kept them together, so they drifted.
• PublishTo.targets — the registries a package publishes to, as a set. fromDirectory stays, but only as a label for messages (pub.dev+npm for a hybrid): no single string can answer "run pana?", "check the npm login?" and "is there any registry?" at once, and pretending otherwise is what made hybrids npm-only.
• Publish takes targets and an onPublished callback. A resumed publish passes the registries that are still open, and the callback runs between the uploads, so a registry that already accepted the version is recorded before the next one can fail.
• PublishedVersion.latestVersionFor / registryVersionsFor answer per registry; IsInRegistry.missingTargets names the registries a package has never been released on.

Changed

• A hybrid is published to both of its registries. Each manifest decides for its own side: publish_to: none takes the Dart side out without touching the npm side, and private: true does the reverse. pub.dev is uploaded first because dart pub publish --dry-run is the only pre-upload validation gate.
• When one registry fails after another succeeded, the failure now says which registry is already done — reporting "nothing happened" made users restart instead of continue, and the restart was then rejected by the registry.
• PublishedVersion.get returns the highest version across all registries of a package, and allVersions/registryVersions their union. The bump has to clear every registry the package is on.
• IsInRegistry reports true only when every registry has the package, and the first-publish prompt asks per registry, naming that registry's package name and publish command.
• The npm wait prints the status page of the resolved registry. A scoped package on a private feed is not on npmjs.com, and that link sent users to a
• publish_to: naming a custom pub server is treated as a pub.dev target instead of raising UnimplementedError. Only none takes a package off its registry. Note the version lookup still queries pub.dev itself — the registry url comes from the language catalog, not from the manifest.
• Allow to publish hybrid packages

Changed

• Allow to pass custom options to exec of dir commands.

Changed

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

Changed

• Rename .master in .ocean

Changed

• Finetune command line output

Changed

• Prevent pubspec.lock interrupting publishing

Fixed

• Fix issues with pubspec.lock

Changed

• refactor: shorten all CLI help texts to 60 chars
• Improve cli log

Fixed

• Fix unit test errors

Changed

• Take base version from git tags when publish_to is none

Changed

• Fix: Skipping unchanged repos from publishing does not work

Added

• New command »is-in-registry«: checks if at least one version of the package is available on its registry (pub.dev / npm)
• »publish« makes sure at least one version is already on the registry. A package that was never published is published manually by the user first — the shell commands to execute are shown, the publish continues after the package became visible on the registry

Changed

• Make sure package is already published in registry before publishing
• Merge main

Fixed

• Fix: Publishing fails

Changed

• Stop publishing when warnings happen
• #gg: changed references to pub.dev

Removed

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

Added

• Add package version number code to each package

Added

• RemoveVersionTag command: removes an already existing tag of the version to be published - locally as well as on the remote - so the publish flow can recreate it on the new release commit

Changed

• Publish removes an already existing version tag before publishing to the registry. A publish that failed after tagging left the tag on a commit the retry replaces, which made the tag step of the next run refuse to tag or tag an abandoned commit.

Changed

• Support projects without manifest: ProjectType.none, checks skipped, version tracked as git tag only
• gg_multi: changed references to git

Added

• WaitUntilPublished command: waits until the current manifest version is visible on the registry (pub.dev/npm) — announces the wait incl. a status url, reports progress and fails with a bounded timeout (15 min — pub.dev itself can take up to ~10 min) instead of hanging; skips packages that publish to no registry
• IsVersionPrepared.messagePrefixFor(manifestFile) builds the message prefix from the manifest the version was actually read from
• Add WaitUntilPublished command with status url and bounded timeout

Changed

• Raise WaitUntilPublished default timeout to 15 min (pub.dev can take ~10 min)

Fixed

• Fix hanging publishing process
• "Version in ./pubspec.yaml must be one of the following" no longer names pubspec.yaml for TypeScript projects, which made them look like they were detected as Dart projects. The message now names package.json.
• Requires gg_lang ^0.2.5, so npm published-version lookups no longer trust the "latest" dist-tag

Changed

• Name the actual manifest in the version-not-prepared message

Changed

• Run npm registry lookups in the package directory so the project-level .npmrc with private feeds is honored
• gg_multi: changed references to git

Added

• Add rc prerelease channel to gg do publish (channel field/flag, X.Y.Z-rc.N computation, npm --tag rc, single + multi repo)
• Address review: wrap registry version-parse errors as RegistryException, clarify spent-version rc message, lock cider rc changelog format

Changed

• gg_multi: changed references to git

Changed

• npm/pnpm (TypeScript) publishes now run interactively by inheriting the terminal's stdio, so the package manager can drive its own 2FA flow — prompting for a one-time password or opening its browser login — instead of failing with ERR_PNPM_OTP_NON_INTERACTIVE when gg captured the pipe. Dart/pub.dev publishing is unchanged (still captured, gg answers the confirmation prompt).
• feat(gg): do checkout + .gg/.ticket.json ticket marker; TS format no direct eslint & P:\programs\flutter/bin/internal/exit_with_errorlevel.bat
• feat(gg): interactive npm publish + npm-logged-in precheck; package.json prepublishOnly->build->test rules (bridges exempt from build->test); do review pnpm blockExoticSubdeps + stdout; can publish runs per-repo can-publish; do merge/publish write doCommit; pana skip label
• gg_multi: changed references to git

Changed

• gg_multi: changed references to git

Changed

• Treat dart-typescript bridge repos as TypeScript for can/do review (npm install, skip dart pub get); export isBridgeProject from gg_one
• Publish bridges as TypeScript: pnpm-aware publish, dual-manifest version bump, non-swallowed publish errors, idempotent resume, review skips merged repos, link: for local TS deps, package.json scripts check
• gg_multi: changed references to git

Changed

• feat: language-universal publishing via gg_lang (npm + pub.dev registry-aware version checks, manifest-driven publish command, TypeScript bypasses CHANGELOG)
• feat(do add): auto-clone transitive deps into master before graph build & P:\programs\flutter/bin/internal/exit_with_errorlevel.bat
• gg_multi: changed references to git
• gg_multi: changed references to git
• Gg Multi: changed references to pub.dev

Changed

• kidney: changed references to path
• Refactor MainBranch to inject process runner and improve tests
• kidney: changed references to git

Fixed

• Remove useCarriageReturn and fix ggLog parameter in merge command

Added

• Add is-main-branch command to check for main branch in Git

Changed

• Improve error message for non-feature branches in is_feature_branch
• Update dependencies: gg_console_colors, gg_git, gg_capture_print
• Update latest dependencies, Add .gitattributes file

Changed

• Update to gg_git 3.0.0

Changed

• Improve version mismatch error message

Removed

• dependency pana

Added

• use dart pub outdated json response

Removed

• dependency to gg_install_gg, remove ./check script

Changed

• upgrade dependencies

Changed

• Fix mocks

Added

• PrepareNextVersion: Specify published version from outside

Changed

• MockIsUpgraded reuses code from MockDirCommand
• derive all mocks from MockDirCommand
• Fintue mocks

Added

• Extend mock for IsUpgraded

Removed

• 'Pipline: Disable cache'

Fixed

• Fixed an error on IsVersionPrepared

Changed

• Update dependency gg_version to 4.0.0