Upload wheels to PyPI from GitHub workflows

[chaeyeunpark]

Before submitting

Please complete the following checklist when submitting a PR:

• All new features must include a unit test.
  If you've fixed a bug or added code that should be tested, add a test to the
  tests directory!

• All new functions and code must be clearly commented and documented.
  If you do make documentation changes, make sure that the docs build and
  render correctly by running make docs.

• Ensure that the test suite passes, by running make test.

• Add a new entry to the .github/CHANGELOG.md file, summarizing the
  change, and including a link back to the PR.

• Ensure that code is properly formatted by running make format.

When all the above are checked, delete everything above the dashed
line and fill in the pull request template.

---

Context:

Description of the Change:

Benefits:

Possible Drawbacks:

Related GitHub Issues:

[github-actions]

Hello. You may have forgotten to update the changelog!
Please edit .github/CHANGELOG.md with:

• A one-to-two sentence description of the change. You may include a small working example for new features.
• A link back to this PR.
• Your name (or GitHub username) in the contributors section.

[codecov]

Codecov Report

Merging #220 (613035e) into master (8b9d412) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #220   +/-   ##
=======================================
  Coverage   99.71%   99.71%           
=======================================
  Files           4        4           
  Lines         351      351           
=======================================
  Hits          350      350           
  Misses          1        1           

Impacted Files	Coverage Δ
pennylane_lightning/_version.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b9d412...613035e. Read the comment docs.

[github-actions]

Test Report (C++) on Ubuntu

       1 files  ±0         1 suites  ±0   0s ⏱️ ±0s
   294 tests ±0     294 ✔️ ±0  0 💤 ±0  0 ❌ ±0 
2 677 runs  ±0  2 677 ✔️ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 613035e. ± Comparison against base commit 8b9d412.

♻️ This comment has been updated with latest results.

[chaeyeunpark]

Hi @mlxd, it now seems to work (see forked repository which uploads Pennylane-Lightning-Test to test-PyPI well (https://github.com/chaeyeunpark/pennylane-lightning/actions). If this looks okay, I want to change test-PyPI to real PyPI and merge.

[mlxd]

Hey @chaeyeunpark
Looks good to me! I think we may update this after the current release cycle (ie once the 0.22.0-dev branch is onboard) to simplify the changing in naming. Do you think that sounds reasonable?

Otherwise, we can merge now and backport the change to the 0.21.0-rc0 branch without the dev name. Happy with whichever you think is best here. I'll approve after this decision.

[chaeyeunpark]

Hi @mlxd, the current script does not update the version if it is not a dev version. As it also uploads wheels to PyPI only when it is released or merged into the master, it might be nice to test this feature with the rc build.

[mlxd]

Hi @mlxd, the current script does not update the version if it is not a dev version. As it also uploads wheels to PyPI only when it is released or merged into the master, it might be nice to test this feature with the rc build.

Great, thanks @chaeyeunpark ! I think we can merge this safely on Monday/Tuesday, once we increment the master version to 0.22.0-dev. How does that sound to you?

[chaeyeunpark]

@mlxd Yes, that sounds more safe 👍

[mlxd]

💯