FEAT-#7265: Automatic publication of Modin wheel to PyPI

[anmyachev]

What do these changes do?

• first commit message and PR title follow format outlined here

  NOTE: If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

• passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
• passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
• signed commit with git commit -s
• Resolves Automatic publication of Modin wheel to PyPI #7265
• tests added and passing
• module layout described at docs/development/architecture.rst is up-to-date

[YarShev]

We should checkout Modin with fetch_depth: 0, otherwise only a latest commit is fetched.

[anmyachev]

Why?

[YarShev]

We should have tagged wheels, otherwise we might get untagged ones.

[devin-petersohn]

It is possible the latest commit is not the tagged commit, so I think @YarShev is correct. Additionally, we may want to check out the latest tag to ensure we only upload tagged releases.

It would be good to also have a check that ensures that the release name is correct, so it doesn't upload a bad release.

[anmyachev]

Will it be better to use fetch-tags: option?

[devin-petersohn]

Yes that would be good, but we should also git checkout the latest tag to ensure we build the correct release. It seems like we still need fetch-depth:0 for fetch-tags to work properly: actions/checkout#1471

[sfc-gh-dpetersohn]

In my suggestion I swapped the order of these 😢

Suggested change

	run: git checkout $(git describe --tags "$(git rev-list --tags --max-count=1)")
	if: github.event_name == 'push'
	if: github.event_name == 'push'
	run: git checkout $(git describe --tags "$(git rev-list --tags --max-count=1)")

[anmyachev]

In my suggestion I swapped the order of these 😢

Actually, I've adjusted your suggestion a bit to make the style similar to what is used in ci.yml :) Does it make sense?

[devin-petersohn]

Oh, is this valid too? If so I'm okay to merge this

[anmyachev]

Oh, is this valid too?

yes

[YarShev]

@anmyachev, we should also have updated the release docs.