You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There hasn't been a release of pytest-html in almost 2 years. Several fixes and dependency updates have been merged since then. All CI tests are currently passing against master branch.
I'm not sure why that matters, but here is a PR that updates chai to the latest version without making the import changes that were breaking tests in the dependabot PR: #951
All JS tests pass for me locally. Can you approve the PR workflow to run?
Yeah, the fail in CI prompted me to try some import change for chai 5.3.1 without success (js is not my main language). Maybe we'll avoid the issue entirely by upgrading directly to the new major of chai.
Sorry for being a ghost here. I simply haven't been able to prioritize it. I've tried at least twice via the pytest-dev channels to get additional maintainers, but haven't gotten any responses.
@Pierre-Sassoulas What TZ are you in? Maybe we could coordinate a release. Happy to do it, but don't have time to deal with any issues that might arise. I could set aside like 60 minutes and we can go through any open PRs etc. and then do a release.
I'm in Europe/Stockholm TZ.
I would love to see PRs to implement semantic release and strict convential-commit checking.
That way, releases would be automatic on merge to main/master.
Sounds good ! Europe/Paris, let me know. Maybe settting up a release doc (via tag ?) would be best for the long term. We don't have to merge all pending MRs before release either.
HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/
User 'pytest-dev' does not have a verified primary email address.
Please add a verified primary email before attempting to upload to
PyPI.
We lost access to the pytest-dev account (we tried a password reset, but that seems to fail because the mail apparently was never verified on PyPI). We can recover it but this is going to take some time. Do you mind adding me in pypi before that @BeyondEvil ? (Same username than for github)
We lost access to the pytest-dev account (we tried a password reset, but that seems to fail because the mail apparently was never verified on PyPI). We can recover it but this is going to take some time. Do you mind adding me in pypi before that @BeyondEvil ? (Same username than for github)
Thank you, I think I need to have the manager right to be able to generate an API key for the release and move the project to the pytest-dev organisation later; right now I can only view the project.
Thank you, I think I need to have the manager right to be able to generate an API key for the release and move the project to the pytest-dev organisation later; right now I can only view the project.
Activity
Pierre-Sassoulas commentedon Sep 18, 2025
Didn't manage to upgrade Chai (#939), so this is probably a blocker.
cgoldberg commentedon Sep 18, 2025
I'm not sure why that matters, but here is a PR that updates chai to the latest version without making the import changes that were breaking tests in the dependabot PR: #951
All JS tests pass for me locally. Can you approve the PR workflow to run?
Pierre-Sassoulas commentedon Sep 18, 2025
Yeah, the fail in CI prompted me to try some import change for chai 5.3.1 without success (js is not my main language). Maybe we'll avoid the issue entirely by upgrading directly to the new major of chai.
Pierre-Sassoulas commentedon Sep 20, 2025
@BeyondEvil how do you feel about releasing ? (the upgrade of chai was done in #951 )
BeyondEvil commentedon Sep 20, 2025
Sorry for being a ghost here. I simply haven't been able to prioritize it. I've tried at least twice via the pytest-dev channels to get additional maintainers, but haven't gotten any responses.
@Pierre-Sassoulas What TZ are you in? Maybe we could coordinate a release. Happy to do it, but don't have time to deal with any issues that might arise. I could set aside like 60 minutes and we can go through any open PRs etc. and then do a release.
I'm in Europe/Stockholm TZ.
I would love to see PRs to implement semantic release and strict convential-commit checking.
That way, releases would be automatic on merge to main/master.
Pierre-Sassoulas commentedon Sep 20, 2025
Sounds good ! Europe/Paris, let me know. Maybe settting up a release doc (via tag ?) would be best for the long term. We don't have to merge all pending MRs before release either.
BeyondEvil commentedon Sep 20, 2025
Sent you a connect request on LinkedIn. We can exchange emails etc. there and put something on the calendar for next week perhaps? @Pierre-Sassoulas
RonnyPfannschmidt commentedon Sep 21, 2025
i'll be traveling for work until the 28th - afterward i can help setup release and maintenance automation + using the pypi org to ease things
scottdmcc commentedon Oct 27, 2025
Has there been any progress on this?
srodriguez91 commentedon Oct 31, 2025
If it's not too late, I'd really like to request for this feature to be merged in: #934
We generate quite a few environment variables to display here.
klott commentedon Dec 21, 2025
Any update on this? would love to get an older merged bug fix released
bparthas21 commentedon Jan 13, 2026
Can you publish a new release please? We need the fix in this PR that was done on Dec 2, 2025.
Pierre-Sassoulas commentedon Jan 13, 2026
@BeyondEvil would you approve of someone else (a pytest-dev admin for example) putting the release action into place and releasing ?
BeyondEvil commentedon Jan 14, 2026
Happy to relinquish all ownership and maintenance etc. to pytest-dev.
BeyondEvil commentedon Jan 14, 2026
Tried doing a release but it failed. I don't have time to troubleshoot.
cgoldberg commentedon Jan 15, 2026
Publishing to PyPI failed with:
I think if you just add a verified email to this account and try again it will work: https://pypi.org/user/pytest-dev/
Pierre-Sassoulas commentedon Jan 15, 2026
We lost access to the pytest-dev account (we tried a password reset, but that seems to fail because the mail apparently was never verified on PyPI). We can recover it but this is going to take some time. Do you mind adding me in pypi before that @BeyondEvil ? (Same username than for github)
BeyondEvil commentedon Jan 15, 2026
Invite sent.
Pierre-Sassoulas commentedon Jan 15, 2026
Thank you, I think I need to have the manager right to be able to generate an API key for the release and move the project to the pytest-dev organisation later; right now I can only view the project.
BeyondEvil commentedon Jan 19, 2026
Added a new API token as a secret:
PYPI_API_TOKENRonnyPfannschmidt commentedon Jan 19, 2026
id recommend migration from api token to openid connect as soon as possible
BeyondEvil commentedon Jan 19, 2026
Done and done ✅
https://github.com/pytest-dev/pytest-html/actions/runs/21135663546/job/60776992948
Thanks @RonnyPfannschmidt, I had now idea that was a possibility.