-
Notifications
You must be signed in to change notification settings - Fork 1
Wrong version when publishing to PyPI #12
Copy link
Copy link
Closed
Labels
area:deploymentImprovements or additions to app packaging or deploymentImprovements or additions to app packaging or deploymentbug:minorIssue affecting small user population or stand-alone use-casesIssue affecting small user population or stand-alone use-casesfeature:changeFeature is implemented, but should be refactoredFeature is implemented, but should be refactoredlevel:easySolution is easy to implementSolution is easy to implement
Milestone
Metadata
Metadata
Assignees
Labels
area:deploymentImprovements or additions to app packaging or deploymentImprovements or additions to app packaging or deploymentbug:minorIssue affecting small user population or stand-alone use-casesIssue affecting small user population or stand-alone use-casesfeature:changeFeature is implemented, but should be refactoredFeature is implemented, but should be refactoredlevel:easySolution is easy to implementSolution is easy to implement
When package is published on PyPI by the build pipeline, it is assigned version
${CURRENT_VERSION}-dev${BUILD_ID}.But in SemVer
0.1.0-rc.3is a higher version than0.1.0-rc.3-dev2019100801. This causing more recent builds to be considered an "older" version by PyPI.Refactor to use next release version for PyPI publishing.