Issue importing a managed solution using import-solution@v1 action

[jpsimonis]

Hi,

for context I am using the yml examples for implementing ALM for Powerplatform with GitHub actions.

I have had to update these examples in 3 ways.

1. add install action for v1 of PowerPlatform actions
2. update references to v0 of the actions to v1
3. ensure i am using ubuntu as using windows for workflows had issues with importing unmanaged solution i previously exported from branch and export step (invalid guid errors for solution)

Scenario

I create a release that imports an unmanaged solution build from the github repo into a clean build environment and then exports a managed solution from this build environment and stores that as a github artifact.

The issue occurs in the next step. I connect to my release environment, download the managed version of the solution from github artifacts and start the import. I can see the solution successfully deploy into my environment but the workflow fails with the following error.

Error: An error occurred while sending the request.
An error occurred while sending the request.
An error occurred while sending the request.
Unable to read data from the transport connection: Connection reset by peer.
Connection reset by peer

Error: error: 1
Error: error: 1
Error: failed: Connected as ...

I cannot seem to make this workflow run without this error.

I have tried running this step with windows and get more info but the same error

Error: An error occurred while receiving the HTTP response to https://xxxxx.crm6.dynamics.com/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.2.49.11611. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
An error occurred while receiving the HTTP response to https://xxxx.crm6.dynamics.com/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.2.49.11611. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
The underlying connection was closed: An unexpected error occurred on a receive.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host