Automate PyPI releases/uploads #2670

New issue

Open

opened 2026-02-28 01:17:15 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 01:17:15 -05:00

Owner

Originally created by @greenship24 on GitHub (Dec 24, 2025).

Just a note that there is no release on pypi yet. Could be something forgotten, a pypi break for the holidays, etc.

Just noting it as the docs for install tell you to use pip and all but it is not present (even when manually specifying) and I've checked the release dates for the other beta releases which were all released on pypi on the same day as the actual release on github.

Originally created by @greenship24 on GitHub (Dec 24, 2025). Just a note that there is no release on pypi yet. Could be something forgotten, a pypi break for the holidays, etc. Just noting it as the docs for install tell you to use pip and all but it is not present (even when manually specifying) and I've checked the release dates for the other beta releases which were all released on pypi on the same day as the actual release on github.

deekerman added the

CI/CD

label

2026-02-28 01:17:15 -05:00

deekerman commented

2026-02-28 01:17:17 -05:00

Author

Owner

@MichaIng commented on GitHub (Dec 27, 2025):

Oh thanks for the hint. I was watching the automated Docker builds, tags, and Docker Hub uploads that I totally forgot to trigger the PyPI uploads. Done now, should be there in a minute.

I'll add an automatic trigger, like the Docker builds.

@MichaIng commented on GitHub (Dec 27, 2025): Oh thanks for the hint. I was watching the automated Docker builds, tags, and Docker Hub uploads that I totally forgot to trigger the PyPI uploads. Done now, should be there in a minute. I'll add an automatic trigger, like the Docker builds.

deekerman commented

2026-02-28 01:17:17 -05:00

Author

Owner

@greenship24 commented on GitHub (Dec 31, 2025):

No problem at all. I honestly thought you might have slow rolled it just to avoid new issues before the new year's ;)
And yes, I see it just fine on pypi now.

Thanks for all your guys' hard work!

@greenship24 commented on GitHub (Dec 31, 2025): No problem at all. I honestly thought you might have slow rolled it just to avoid new issues before the new year's ;) And yes, I see it just fine on pypi now. Thanks for all your guys' hard work!

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/motioneye#2670

No description provided.

Rows
Columns