[BUG] Premature rebase to alpine 3.21

[borntohonk]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hi, I've been made aware that your medusa docker image has been rebased to alpine 3.21 from alpine 3.19.

And this is causing some mild inconvenience, even though it is much later than when you did that (~3 weeks?), it is first now some new adopters are finding their way to the pymedusa discord server with problems.

TL:DR
pymedusa does not yet support python 3.12, this PR: pymedusa/Medusa#11966 will add that support.

It is not yet merged, and when merged would be in the develop branch, until a new medusa version is pushed.

a new version of pymedusa will also enable control over "WEB_PORT" through environment variables (as of pymedusa/Medusa@0383abd)

(i've pre-emptively also filed a PR to add python 3.13 support - pymedusa/Medusa#11967)

Expected Behavior

for the image to not yet be on alpine 3.21, but alpine 3.19

Steps To Reproduce

N/A

Environment

N/A

CPU architecture

x86-64

Docker creation

N/A

Container logs

N/A

[thespad]

What happened to pymedusa/Medusa#11633 (comment) ?

[borntohonk]

What happened to pymedusa/Medusa#11633 (comment) ?

The tl:dr is that they didn't verify they had fixed 3.12 compatibility properly.

The author of the PR has done this kind of half-and-half work on a lot of stuff, the maintainer probably in good faith merged it and accepted it as a solution as 3.12 was tad premature.

I only addressed it properly myself after someone pointed out errors in the medusa discord, and sent two PRs, one for 3.12 and one for 3.13

[thespad]

Gotcha, I'll do a PR to roll back to 3.19 until upstream is confirmed to work with python 3.12