Changelog doesn't reflect v02/v01 removal

[cumason123]

Expected Behavior

Changelog should explain why versions v02 and v01 were removed

Actual Behavior

Changelog wasn't updated in that PR

Steps to Reproduce the Problem

View the changelog

Specifications

• Platform: any

[cumason123]

@di should changelog adjustments go in the PR which makes the change or separate PR's? Just wanna know how I should merge in the changelog adjustment

[cumason123]

Furthermore, should I just add YANKED to every version of 0.2 and 0.1? I'm unsure what the format is for yanking an entire version.

[di]

Ideally they would be in the PR that makes the changes, with a link to the corresponding issue.

[di]

Furthermore, should I just add YANKED to every version of 0.2 and 0.1? I'm unsure what the format is for yanking an entire version.

Not sure I follow. Why would we be yanking these versions?

[cumason123]

So we removed versions v0.1 and v0.2. I'm unsure how to modify a changelog to reflect those changes (my first time modifying a changelog).

[di]

We removed support for the v0.1 and v0.2 specifications. The releases on PyPI, while they have the same version numbers, are independent from the spec versions, and should remain.

I would expect to see something like the following in the changelog:

Remove support for CloudEvents v0.1 and v0.2 specs (#35)

[cumason123]

Thanks, I was confused on what version referred to what. Rookie mistake!