chore(release): update pypi packaging

[thomasrockhu-codecov]

• splits build_assets and build_for_pypi into separate workflows that run on
• they also run on new tags
• adds pyproject.toml because its what should be used over setup.py
• splits the build and deploy job for the build_for_pypi workflow
• small opentelem thing to not run on tests

fixes #466

[codecov]

❌ 5 Tests Failed:

Tests completed	Failed	Passed	Skipped
3560	5	3555	0

View the top 3 failed tests by shortest run time

api.temp.calculator.test_calculator::test_divide

Stack Traces | 0.001s run time

def
                test_divide():
                > assert Calculator.divide(1, 2) == 0.5
                E assert 1.0 == 0.5
                E + where 1.0 = <function Calculator.divide at 0x104c9eb90>(1, 2)
                E + where <function Calculator.divide at 0x104c9eb90> = Calculator.divide
                .../temp/calculator/test_calculator.py:30: AssertionError

api.temp.calculator.test_calculator::test_divide

Stack Traces | 0.001s run time

def
                test_divide():
                > assert Calculator.divide(1, 2) == 0.5
                E assert 1.0 == 0.5
                E + where 1.0 = <function Calculator.divide at 0x104c9eb90>(1, 2)
                E + where <function Calculator.divide at 0x104c9eb90> = Calculator.divide
                .../temp/calculator/test_calculator.py:30: AssertionError

api.temp.calculator.test_calculator::test_divide

Stack Traces | 0.001s run time

def
                test_divide():
                > assert Calculator.divide(1, 2) == 0.5
                E assert 1.0 == 0.5
                E + where 1.0 = <function Calculator.divide at 0x104c9eb90>(1, 2)
                E + where <function Calculator.divide at 0x104c9eb90> = Calculator.divide
                .../temp/calculator/test_calculator.py:30: AssertionError

To view more test analytics, go to the Test Analytics Dashboard
📢 Thoughts on this report? Let us know!

[github-actions]

✅ All tests successful. No failed tests were found.

📣 Thoughts on this report? Let Codecov know! | Powered by Codecov

[webknjaz]

@thomasrockhu-codecov short of the broken regex, the rest should be ready even without implementing improvement suggestions in other comments — they can be declared out of the scope and filed as separate issues, I suppose.

[webknjaz]

you can email me at [email protected].

Thanks! I've emailed you.

[webknjaz]

Just realized that the environment isn't set. Here's a patch to fix this. Additionally, add required reviewers to the environment called pypi in the repo settings.

[webknjaz]

@thomasrockhu-codecov additionally to that incorrect URL that I suggested initially, could you confirm you've enabled required reviewers in the environment called pypi? There's been discussions about this topic recently, when TP was being integrated into pip: pypa/pip#13048 (comment). I recommend having this gate just to be in control of the process.

[thomasrockhu-codecov]

@webknjaz

[webknjaz]

LGTM

[thomasrockhu-codecov]

@webknjaz any advice on this error? https://github.com/codecov/codecov-cli/actions/runs/13401097003/job/37432195453#step:4:1169

[thomasrockhu-codecov]

just kidding, I think I got it

[webknjaz]

@thomasrockhu-codecov oh, #620 broke it. Trusted Publishing doesn't yet support auth from reusable workflows due to different security considerations that aren't yet worked out fully. It's a limitation of how PyPI implements trust currently. It sometimes works almost by accident but we treat that as unsupported. This is being designed slowly, but no ETA so far.

To combine it with testing, I usually have a top-level workflow with the conditional publishing jobs and that workflow calls a few reusable ones, while keeping pypi-publish in the top level one.

P.S. When testing out publishing automation updates, I tend to use pre-release versions (a0/b0/rc0 etc). They are not picked up by installers by default so there's not as much harmful impact in terms of confusing the end users.