"repositories": [
{
"type": "vcs",
"url": "https://xxx@bitbucket.org/xxx/package.git"
}
],Failed to update https://xxx@bitbucket.org/xxx/package.git, package information from this repository may be outdated
[RuntimeException]
Failed to execute git clone --no-checkout 'https://xxx@bitbucket.org/xxx/package.git' '/home/site.ru/dev/vendor/package/package' && cd '/home/site.ru/dev/vendor/package/package' && git remote a dd composer 'https://xxx@bitbucket.org/xxx/package.git' && git fetch composer
error: Cannot communicate securely with peer: no common encryption algorithm(s). while accessing https://xxx@bitbucket.org/xxx/package.git/info/refs
fatal: HTTP request failed
Bitbucket Cloud will be disabling support for TLSv1 and TLSv1.1 effective 1 December 2018.
This will affect all HTTPS traffic to Bitbucket, including:
Git or Mercurial traffic to bitbucket.org
The bitbucket.org Web interface
API calls to api.bitbucket.org
Hosted sites on bitbucket.io
Any other HTTPS traffic not listed here
You should be able to test your connection from the command line:This will connect to Bitbucket using the Git client and list the connection parameters. If you see a line like “SSL connection using TLSv1.2” in the output, then you are unaffected; if that line mentions a different version of TLS, then you are affected.GIT_CURL_VERBOSE=1 git ls-remote https://bitbucket.org/
Средний
Простой
Простой
Сложный
