Update python-publish.yml

[raoulcollenteur]

Short Description

Quick PR to fix the python-publish workflow, because Pastas was not automatically uploaded to Pypi with the latest release.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.13% (target: +0.00%)	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (eabc767)	5975	4457	74.59%
Head commit (33d7471)	5999 (+24)	4483 (+26)	74.73% (+0.13%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#692)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{You may notice some variations in coverage metrics with the latest Coverage engine update. For more details, visit the documentation}

[martinvonk]

I can't judge if this will work? Maybe @dbrakenhoff can? Can't we test it on the test-pypi?

I am surprised however that the python-publish.yml fails, since this worked fine for Metran yesterday..

[dbrakenhoff]

Looks good, we can delete the other PYPI secrets (USERNAME and PASSWORD) if this works properly.

[dbrakenhoff]

@raoulcollenteur it might be easiest to manually upload pastas 1.4 to PYPI with your token, instead of trying to re-release 1.4 on Github to trigger the build.