New release v0.9.0-alpha.1

[dtzar]

Lots of important changes merged since v0.8.0 and should cut a new release.
Would like to just take what's on main now plus merge #44

• Decide on main commit for a release
• Cut branch named v0.9.0-alpha.1 based on agreed upon main commit
• Cut a tag named v0.9.0-alpha.1

@SteveLasker @gokarnm @iamsamirzon @FeynmanZhou

[iamsamirzon]

Thanks @dtzar for driving a release of Notation/Notation-go. I am particularly interested in seeing this issue ( notaryproject/notation#119) fixed in this next release. Refer discussion here notaryproject/notation#170

[SteveLasker]

@iamsamirzon, would like to pull in -u, -p for ecr support.

[dtzar]

@iamsamirzon - I'd like to still cut this release but now that there has been a number of changes since the request (28 days ago), I think we should stick to committing it with the version around this same date to help illustrate the cli and go library were working/tested together at this time (both 0.9.0) which was the original intent.

The issue mentioned workaround is a problem with oras-go and even if we release a new version of this library it won't matter.

[iamsamirzon]

Thanks @dtzar . That works.

[dtzar]

Once someone approves/merges #65 then I'll cut this release.

[FeynmanZhou]

Once someone approves/merges #65 then I'll cut this release.

I think this issue does not rely on #65 , @shizhMSFT explained the reason under that PR.

@dtzar Could you check if #65 is necessary for this release?

[dtzar]

Yes, Shiwei's response makes sense. I started to investigate alternative approaches to helping automate release notes. I'm not going to hold up releasing this on the PR.

[dtzar]

v0.9.0-alpha.1 is released.