Releases: github/gh-bbs2gh
Releases · github/gh-bbs2gh
v1.2.0
- When running migrations with
gh bbs2gh
and migrations from GitHub Enterprise Server withgh gei
, create the migration source before starting the export
v1.1.0
- Log migration warnings count after a migration completes
v1.0.0
- BREAKING CHANGE: Drop deprecated
--wait
option formigrate-repo
andmigrate-org
commands - Allow Enterprise Managed Users (EMU) organizations to skip the invitation process in the
reclaim-mannequin
command with the--skip-invitation
option - Fix target repo existence check in GitHub Enterprise Server migrations so it doesn't error if the target repo used to exist, but has been renamed
- Fail fast if the target GitHub repo already exists in
bbs2gh migrate-repo
v0.49
- Validate that the
--ghes-api-url
is a valid URL ingh gei generate-script
- Allow CLI to fail fast when an unauthorized token is provided by preventing retry logic on 401 errors
- Improve performance when reclaiming a single mannequin with
reclaim-mannequin
- Improve logging for
reclaim-mannequin
command - Ensure that CLI runs have separate log files, even if they start at the same time, by adding the process ID to the filenames
v0.48
- BREAKING CHANGE: Require the AWS region to always be specified with the
--aws-region
argument orAWS_REGION
environment variable if using AWS S3 for blob storage. Previously, this was optional (with a warning) if you weren't specifying an AWS session token. - BREAKING CHANGE: Drop support for deprecated
AWS_ACCESS_KEY
andAWS_SECRET_KEY
environment variables ingh gei
andgh bbs2gh
. The AWS S3 credentials can now only be configured using the industry-standardAWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
variables or command line arguments. - BREAKING CHANGE: Require the Bitbucket Server URL, project key and repo to always be provided for
bbs2gh migrate-repo
, even if using the upload-and-migrate (--archive-path
) or migrate-only (--archive-url
) flows - Increase timeouts in archive uploads to AWS to prevent timeouts during large uploads
v0.47
- Include the
databaseId
(GUID) in the verbose logs when starting a migration - Fix recommended
gh gei
,gh bbs2gh
andgh ado2gh
commands in log output
v0.46
- Add additional error handling to
reclaim-mannequin
process - Removed ability to use
gh gei
to migrate from ADO -> GH. You must usegh ado2gh
to do this now. This was long since obsolete, but was still available via hidden args - which have now been removed. - Add
bbs2gh inventory-report
command to write data available for migrations in CSV form
v0.45
- Improve log sanitization to also remove secret values that have been URL encoded
- Warn when the
--ssh-port
argument forbbs2gh migrate-repo
andbbs2gh generate-script
is set to the default port for Git operations
v0.44
- Hide the
reclaim-mannequin --skip-invitation
option from documentation, since it's still under development and not yet available
v0.43
- Add new '--skip-invitation' flag for
reclaim-mannequin
to allow EMU organizations to reclaim mannequins without an email invitation - Write warnings to log and console if GitHub is experiencing an availability incident.
- Improve the error thrown when you have insufficient permissions for the target GitHub organization to explicitly mention the relevant organization
- Write log output prior to making API calls in wait-for-migration commands
- Support forked repositories in Bitbucket Server migrations