Skip to content

Conversation

@browniebroke
Copy link
Member

Description

As discussed in:

Changes:

@auvipy auvipy self-requested a review September 20, 2025 11:43
# Conflicts: #	docs/community/project-management.md #	docs/community/release-notes.md
@browniebroke browniebroke marked this pull request as ready for review October 30, 2025 13:57
default: "0"
schedule:
# Run the second day of every month.
- cron: "12 3 2 * *"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we really need cron?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about that either: I got it from the django-commons best practices repo, but the actual projects don't seem to use that... I think the idea was to create regular "test" releases the PyPI to ensure the release process keeps working, but I'm not a big fan of that. Maybe I'm missing the problem it's solving 🤷

Anyway, as the move is now getting delayed, I think this PR will become stale. I've reworked this into a single release workflow publishing to Test PyPI before doing it to PyPI:

Curious what you think, but I was hoping to test it out soon with 3.17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants