docs: update changelog for 0.8.0rc1

[henryiii]

Preparing for a release (mentioned in #83).

[henryiii]

(Personally, I'd be fine with a RC release first to make sure PDM, scikit-build-core, & meson-python (and others?) are fine.)

[henryiii]

@FFY00 @pradyunsg gentle reminder. :) (From #83 (comment))

[rooterkyberian]

@henryiii AFAIK pdm won't be affected since they are explicitly vendoring this library, so they have to manually port changes every time.

On that topic - I just prepared such porting PR and it seem now maintainer of pdm is blocking vendoring new version waiting for official release ( pdm-project/pdm-backend#220 (comment) ), so my questions would be:

• when this release can happen?
• can it include fixes from current master (I'm only really intrested in comma fix )
• anything I can do to help?

[henryiii]

@FFY00 and @pradyunsg are the only ones that can make a release or set up trusted publishing. I can't make a release, if I could, I would have months ago - scikit-build-core has had to carry around over a year's worth of patches on pyproject-metadata now. I probably will sadly move to vending in the next scikit-build-core release.

[rooterkyberian]

I see,

@FFY00 , @pradyunsg anything we can do to help to get a release out?

[pradyunsg]

@henryiii Could you resolve the merge conflicts with main?

[henryiii]

Sure, will rebase tonight.

[henryiii]

@pradyunsg rebased.

[henryiii]

I made an RC release. Everything seemed fine. Backend authors should check to make sure it works with backends. Everything happened automatically, which was nice. We could add approvals to the release environment, I think that would be nice, say two approvals from maintainers to publish?

[rgommers]

We could add approvals to the release environment, I think that would be nice, say two approvals from maintainers to publish?

That does sound like a good idea to me.