added support for scala 3 - series/0.23

[kailuowang]

same as #54

[rossabaker]

Does this transitively add a jar dependency? With the change in release coordinates, I think this would be a breaking change.

What we could do -- and have done in these integration modules -- is create an 0.24 release against http4s-0.23 core. Then Twirl can stay current without forcing a breaking change to everything.

[rossabaker]

Note that this wasn't a problem on #54, because there's no bincompat yet on the 1.x liine.

[kailuowang]

Sounds good. Will do tomorrow. Thanks for the review.

[kailuowang]

@rossabaker I couldn't find an example of the ritual of bumping minor version in regards to mima.
Do we set mimaPreviousArtifacts to Set.empty in this PR and immediately remove the setting after a 0.24.0-M1 release or is there way to let mima automatically skip checking for the first 0.24.x release?

[rossabaker]

tlMimaPreviousArtifacts should default to doing the right thing when we bump tlBaseVersion. I would bump that to 0.24 and remove the tlMimaPreviousArtifacts entirely and see where that gets us.

[kailuowang]

tlMimaPreviousArtifacts should default to doing the right thing when we bump tlBaseVersion. I would bump that to 0.24 and remove the tlMimaPreviousArtifacts entirely and see where that gets us.

that worked. thanks!

[rossabaker]

Alright, if you create series/0.24 off series/0.23 and retarget this into that, it should be all set. And then it can be tagged 0.24.0-M1 to match the Twirl milestone status.

[rossabaker]

And I probably wouldn't bother to maintain 0.23 anymore at that point, unless there's a security thing.

[kailuowang]

Done, if you approve, I can merge and tag.

[rossabaker]

👍 Looks good.