v0.33

• Added support for x86 Windows machines with new windows-386 build
• Added logic to check if a target repo exists before generating GHES archives
• Fixed reclaiming a single mannequin using reclaim-mannequin with the --mannequin-user and --target-user parameters
• Added logic to ensure target org exists before generating GHES archives

v0.32

• Improve error messages when the specified target organization or enterprise cannot be found
• Mask the value for AWS_ACCESS_KEY and AWS_SECRET_KEY parameters in log output
• Fix log output so we don't say we've finished upload to Azure Blob Storage when you're actually using Amazon S3
• Extend the expiration of blob storage signed URLs from 24hrs to 48hrs so migration can still be successful even if there is a long queue of migrations
• Skip the upload to Azure/AWS blob storage when migrating from GHES 3.8+, as GHES will now handle putting the archives into blob storage. This change only applies to GHES 3.8 onwards, which is not yet released to the public.
• Fixed a bug where bad credentials were incorrectly being treated as rate-limit errors

v0.31

• introduced a new command gh gei migrate-secret-alerts which migrates the state and resolution of secret scanning alerts. This is useful if you have existing secret scanning alerts which have been closed (e.g. revoked, false positive, etc). The state (closed) and resolution will be migrated over to the target repo with this command.
• make gh gei migrate-org visible in the help menu as this is now a published feature of GEI see more. We are now capable of moving an org with all their repositories, teams and certain cross repository references by running one command. ( Currently does not support GitHub Enterprise Server )

v0.30

• Added logging to gh gei wait-for-migration and gh gei migrate-org --wait, showing the number of repos that have been migrated so far

v0.29

• Added additional retry logic covering the case when polling for migration status fails for any reason (along with a few other situations)
• Added --aws-bucket-name to gh gei generate-script and removed --azure-storage-connection-string.

v0.28

• Fixed a bug where uploading archives to S3 still required --azure-storage-connection-string to be passed.

v0.27

• 6 months ago in v0.10, we deprecated the --ssh flag, making it silently do nothing. Now, we’ve removed the flag entirely, so the CLI will error if you try to specify it. If you have any scripts that include the --ssh flag, you must remove that flag or the script will break.
• fixed a bug where secrets were not getting scrubbed from the logs in some circumstances
• If create-team fails when linking an IdP group with an HTTP 400, we will retry
• If create-team fails when removing the initial team member, it will retry
• In v0.25 we started publishing ado2gh as an extension to the gh CLI. However, we didn't update ado2gh generate-script to use the new syntax in the generated migration script. Now it will, and you will need the gh ado2gh extension installed in order to run the generated migration script.
• Added --ghes-api-url as an optional arg to the grant-migrator-role and revoke-migrator-role commands for both ado2gh and gei.
• Added AWS support for archive uploads to gei using the --aws-bucket-name, --aws-access-key and --aws-secret-key arguments.

v0.26

• Retry all failed GET requests made to Github, Azure Devops, and Bitbucket Server.

v0.25

• We are now shipping all functionality for Azure DevOps -> GitHub migrations as a new extension to the GitHub CLI. Run gh extension install github/gh-ado2gh to install. All commands are the same as the previous ado2gh CLI (e.g. gh ado2gh generate-script). If you were previously using gh gei to handle ADO migrations (instead of the separate ado2gh stand-alone CLI), that functionality has now been moved to the gh ado2gh extension. gh gei is solely used for GitHub -> GitHub migration scenarios.
  • We will continue shipping ado2gh stand-alone CLI in this release and probably the next couple, after that the only way to acquire new versions will be via the gh extension.
  • Technically in this release the ADO capabilities in gh gei have only been hidden from the built-in help, but will still work and give the user a warning that they should be using gh ado2gh instead. In a future release we will remove them entirely.
  • Our docs have been updated to reflect these changes and can be accessed here: https://docs.github.com/en/early-access/enterprise-importer

v0.24

• Added --lock-source-repo option to gh gei migrate-repo and gh gei generate-script commands. This will make the source repo read-only as part of the migration.