Errors creating bundles from GitHub repositories

We've now resolved the incident, but please reach out if you continue to see issues.

We believe the underlying issues was an undocumented change in how GitHub authenticates certain OAuth2 repository clone URLs. A fix was deployed that adjusted how our task runner cloned repositories to a mechanism that correctly authenticated.

We've identified the change in behaviour with regards to GitHub repository clone authentication and have deployed a fix. We're currently monitoring to verify the fix.

We're seeing customers are able to get around the issue by temporarily switching to the "Manual" repository connection type.

Note: This requires the SSH deploy key found in the project's "Build & Deploy" page to be registered with the repository. GitHub have recently changed their requirements with regards to the length of SSH deploy keys, so if you require your project's deploy key to be regenerated, reach out to support via our chat widget or at support@servd.host.

Projects attempting to build bundles from GitHub repositories are currently failing and throwing the following errors:

fatal: could not read Username for 'https://github.com': No such device or address fatal: expected flush after ref listing

We're currently investigating and will report updates as soon as we have them.