Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.87%. Comparing base (d4231f5) to head (e9a414e).
Report is 5 commits behind head on main.

@@           Coverage Diff           @@
##             main     #266   +/-   ##
=======================================
  Coverage   91.87%   91.87%           
=======================================
  Files           2        2           
  Lines         320      320           
  Branches       64       64           
=======================================
  Hits          294      294           
  Misses         17       17           
  Partials        9        9           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@matthewfeickert I am trying to create a 0.9.1 version and I followed your video, but https://github.com/scikit-hep/pylhe/actions/runs/11403842254/job/31731751820#step:8:46 here "Bump version" fails with

fatal: Failed to resolve 'v0.9.1^{}' as a valid ref.

Further I still need to figure out conda after pypi.

@matthewfeickert @eduardo-rodrigues Can one of you help with releasing pylhe 0.9.1?

It is best that @matthewfeickert helps as I have not released here so far. I tend to do my releases a different way. Can you help out @matthewfeickert?

Aside - this PR isn't done, right? Maybe better have this "admin" doc under the docs directory?

I am trying to create a 0.9.1 version and I followed your video, but https://github.com/scikit-hep/pylhe/actions/runs/11403842254/job/31731751820#step:8:46 here "Bump version" fails with

fatal: Failed to resolve 'v0.9.1^{}' as a valid ref.

Further I still need to figure out conda after pypi.

@APN-Pucky Sorry, I've been pretty distracted (feel free to poke me on email/Slack if I'm not responsive on GitHub as my notifications can become just a wall sometimes). Can you tell me where you're hitting this specifically in the release workflow?

I fixed @APN-Pucky not having publishing permissions in PR #269, but I also went ahead and released v0.9.1 which is now on PyPI.

Further I still need to figure out conda after pypi.

@APN-Pucky the good news is that there really isn't anything to figure out. Conda-forge automatically watches PyPI for new releases and will generate a new release PR to https://github.com/conda-forge/pylhe-feedstock for us in a few hours. We then just review it to make sure there are no dependency changes and then we can merge it and conda-forge will then do all the building and publishing automatically.