Release for security updates

[shizhMSFT]

Proposing we release v1.0.0-draft.2 for doc and security updates.

[SteveLasker]

Draft 2 still has at least two items tracked before cutting the draft.

The big one is the content breaking change for [blobs] to [descriptors], which we're just making a name change now, for possible future usage.
#74 is blocked on distribution merging the pr. Since it's not a persisted data change, while unfortunate, I wouldn't say it's blocking at this point.

[shizhMSFT]

Thanks @SteveLasker for the details behind the draft.2. Since we haven't reached the milestone 1.0.0.draft.2, we cannot release with the security updates as v1.0.0-draft.2.

The tag name v1.0.1-draft.1 is not an option as we are targeting v1.0.0. Then releasing with the same tag name v1.0.0-draft.1 is our only option.

[shizhMSFT]

@SteveLasker proposed draft.1.1. I've tested that

v1.0.0-draft.1 < v1.0.0-draft.1.1 < v1.0.0-draft.2

Yes, v1.0.0-draft.1.1 is a better option.

[SteveLasker]

for lack of a better option 👍 for v1.0.0-draft.1.1

[sajayantony]

LGTM. v1.0.0-draft.1.1 You can update the issue and share the digest you want to tag?

[shizhMSFT]

@sajayantony I am tagging ac46408 as v1.0.0-draft.1.1.

[shizhMSFT]

Released v1.0.0-draft.1.1.

[corburn]

Links in the v1.0.0-draft.1.1 release notes point to the prior v1.0.0-draft.1 documentation.