File tree Expand file tree Collapse file tree 2 files changed +8
-5
lines changed Expand file tree Collapse file tree 2 files changed +8
-5
lines changed Original file line number Diff line number Diff line change 47
47
cache-key : python-nightly
48
48
run : |
49
49
./go "py:version[nightly]"
50
- ./go py:release
50
+ ./go py:build
51
+ twine upload --repository testpypi bazel-bin/py/selenium-4*.whl bazel-bin/py/selenium-4*.tar.gz
51
52
secrets : inherit
52
53
53
54
Original file line number Diff line number Diff line change @@ -629,13 +629,15 @@ namespace :py do
629
629
# 1. Switching from a release build to a nightly one
630
630
# 2. Updating a nightly build for the next nightly build
631
631
# 3. Switching from nightlies to a release build.
632
- # According to PEP440, the way to indicate a nightly build is `M.m.v.devN`
633
- # Where `N` is sorted numerically. That means we can create the dev
634
- # version number from today's date.
635
632
636
633
if bump_nightly && old_version . include? ( '.dev' )
637
- new_version = old_version . gsub ( /\d +$/ , "#{ Time . now . strftime ( "%Y%m%d%H%M" ) } " )
634
+ # This is the case where we are updating a nightly build to the next nightly build.
635
+ # This change is usually done by the CI system and never committed.
636
+ # The ".dev" is removed to have the pushed package in TestPyPi be shown as latest.
637
+ new_version = old_version . gsub ( /\. dev\d +$/ , '' ) + + ".#{ Time . now . strftime ( "%Y%m%d%H%M" ) } "
638
638
elsif bump_nightly
639
+ # This is the case after a production release and the version number is configured
640
+ # to start doing nightly builds.
639
641
new_version = old_version + ".dev#{ Time . now . strftime ( "%Y%m%d%H%M" ) } "
640
642
else
641
643
new_version = updated_version ( old_version . gsub ( /\. dev\d +$/ , '' ) , arguments [ :version ] )
You can’t perform that action at this time.
0 commit comments