10000 verify_release: Fix issue with draft releases no showing up · Issue #2388 · theupdateframework/python-tuf · GitHub
[go: up one dir, main page]

Skip to content
verify_release: Fix issue with draft releases no showing up #2388
Closed
@jku

Description

@jku

I think at some point I made the verify_release use "draft:true" when uploading the draft release, instead of modifying the name.
This was a mistake as already documented by lukas in #1933:

It would be nice if we could set the release as draft at first, but that has the same caveat, i.e. it requires a token and special knowledge to download the assets.

so what happens is that while the release is a draft ./verify_release -- skip-pypi does not notice that a new GitHub release exists:

./verify_release --skip-pypi
* Built release 3.0.0
* WARNING: GitHub latest version is 2.1.0
* ERROR: GitHub artifacts do not match built release

Easiest fix would be to revert using "draft:true".

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

      0