Skip to content

Handling pre-releases with care #719

@webknjaz

Description

@webknjaz

Today I got a notification that 25.8.0rc1 was out. But when I clicked on https://github.com/twisted/towncrier/releases/tag/25.8.0rc1, it gave me a 404. It wasn't on PyPI either. Then, I looked into the repo and noticed some mentions of 25.8.0rc2 and 25.8.0rc3 but only 25.8.0rc2 on PyPI.

I'm assuming there's been some force-pushing and deletions involved. It really defeats the purpose of release candidates (or any releases in Git or PyPI) if they are just removed randomly.

Could you please just leave the tags as is when adding new pre-releases instead? And use yanking instead of deletion on PyPI?

This would improve transparency of the release process and make testing pre-releases more reliable.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions