Update for Python 3.13

[felixhekhorn]

Follow up from NNPDF/yadism#340

I think it boils down to regenerate the lock file and do an actual run. Unfortunately we don't have unit tests here

[felixhekhorn]

and this also requires a new yadism release -> v0.13.8

@jekoorn it should be sufficient to just adjust the changelog there and you tag that specific commit as v0.13.8

[jekoorn]

Is the recent commit I pushed what you mean?

[felixhekhorn]

basically yes, but no need to do it on the branch. Cherry-pick that commit onto master (so we avoid an additional merge commit) and tag that as v0.13.8

after that you can continue here ...

[jekoorn]

I think I did this, with the v0.13.8 tag and updated changelog. But it doesn't show up yet as a new release. What can I do?

[felixhekhorn]

first, take a look here - there you can see our publishing workflow, i.e. how we publish a new release to PyPI - and you learn why it is not immediate (just in case you were expecting that 🙈 ). Indeed, there is the new release: https://pypi.org/project/yadism/0.13.8/

Buuut, we also see from there that something went wrong: it doesn't show 3.13 as supported version and we need to find out why - I have no idea 🙃

Let me try to ping @alecandido who knows more about packaging than myself.

1. we have the necessary line here https://github.com/NNPDF/yadism/blob/fdf8cdb5421f2d7c982efbc6f5b66cc761f3cf9e/pyproject.toml#L39
2. we know from unit tests that we can run on 3.13 https://github.com/NNPDF/yadism/actions/runs/21139988664/job/60791247511

any idea?

[scarlehoff]

The problem is the tag is done in the wrong commit. Re-do a tag in the latest main and that should work.

[felixhekhorn]

Make it v0.13.9 to avoid any name clash

[alecandido]

I think I did this, with the v0.13.8 tag and updated changelog. But it doesn't show up yet as a new release. What can I do?

Assuming this is referred to yadism, and not Pinefarm...

If you want an actual "release" you have to manually make it

https://github.com/NNPDF/yadism/releases/new

However, the tag correctly triggered the CI, https://github.com/NNPDF/yadism/actions/runs/21139996340, and this correctly deployed the package on PyPI, https://pypi.org/project/yadism/0.13.8/.

In a sense, the release is just nice promotion of what you are doing. But it is not really required at functional level (though somewhere we had a workflow that was triggered by the release, instead of being triggered by the tag, as it is in Yadism deployment).

EDIT: Ah, sorry, I just saw that @felixhekhorn mentioned the same 😅

[alecandido]

Make it v0.13.9 to avoid any name clash

Yes, that's better. PyPI does not allow to unpublish and reuse the same version number, as it could be a vehicle to deceive users (though that's perfectly feasible for Git tags - but not advisable, in general).

If you did not intend to publish v0.13.8 you can actually "yank" it from PyPI. It will be still there, but marked as removed - such that people know it should be avoided. But maybe it's also no big deal to just leave it there 🤷

[jekoorn]

Sorry for the late reply - I was at a conference and had no opportunity to look deper into this. I think I understand now where it went wrong, and I will re-do a tag for v0.13.9 on the current tip of master. Then see if it will be deployed in PyPI correctly. Sorry for the confusion 🙈

[felixhekhorn]

Please add a new commit where you adjust the Changelog. E.g. write something like "rerelease because of wrong tag" or similar

EDIT: aah too late - I'll do it "post-mortem" 🙃