Unable to push component archive to insecure registry after bumping ocm to v0.16.0

[nesmabadr]

What happened:

When I try to push component archive to an insecure registry, I get an error saying "could not push component version: failed to finish component transfer: module version: creating target version: Head https url: http: server gave HTTP response to HTTPS client:"

What you expected to happen:
The component archive should have been pushed successfully to the insecure image

How to reproduce it (as minimally and precisely as possible):
Use the Golang function transfer.TransferVersion with an insecure registry (having an http prefix)

Anything else we need to know:

This is after the use of ORAs which always has the PlainHttp set to false regardless the registry is insecure or not.

Environment:
Golang package ocm.software/ocm v0.16.0

[morri-son]

@Skarlso, can you please check this as this worked before introducing ORAS? #755 is asking for an own flag to easily enable insecure protocols, so related topic.

[Skarlso]

#968 will also fix this issue now.

[morri-son]

#972 just flew in :-)

[Skarlso]

@nesmabadr Can you test with the main branch please? :) I pushed the fix in.

[nesmabadr]

@Skarlso it is now working, thanks a lot! When should this be released?

[Skarlso]

Nice thanks for checking.

I don't know unfortunately. Maybe today but if not then next week. I'll ask the team.

[Skarlso]

Hey, just created a new release v0.16.1. Once this finishes https://github.com/open-component-model/ocm/actions/runs/11404619423 you can use the new version that contains this patch.

[Skarlso]

We've reverted the ORAS changes. We'll release a new version that will contain the old docker code, so this should no longer be a problem.