-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge v0.19.0 release fixes onto master #170
Changes from 6 commits
2b15d02
6b570ed
2798d5b
983ed03
73a8f87
5c546ec
92844aa
3a977d9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,12 @@ | ||
name: Wheels | ||
name: Wheel::Linux::x86_64 | ||
on: | ||
release: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we need the "types" line, as we do e.g. for There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch. I think these need to be added to all. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch -- I think these need to be added to all workflows. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Rather than changing the RC, maybe we merge this as is and modify in a subsequent PR. This won't change the wheel, and help with consistency across the wheel history. What do you think? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sounds good! Thanks @mlxd! |
||
push: | ||
branches: | ||
- master | ||
pull_request: | ||
|
||
|
||
env: | ||
CIBW_BUILD: 'cp37-* cp38-* cp39-*' | ||
|
||
|
@@ -52,7 +54,7 @@ jobs: | |
CIBW_ARCHS_LINUX: ${{matrix.arch}} | ||
|
||
- uses: actions/upload-artifact@v2 | ||
if: github.ref == 'refs/heads/master' | ||
if: ${{ github.event_name == 'release' || github.ref == 'refs/heads/master' }} | ||
with: | ||
name: ${{ runner.os }}-wheels.zip | ||
path: ./wheelhouse/*.whl |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
name: Wheel::Any::None | ||
on: | ||
push: | ||
branches: | ||
- master | ||
pull_request: | ||
release: | ||
|
||
jobs: | ||
build-pure-python-wheel: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- name: Checkout PennyLane-Lightning | ||
uses: actions/checkout@v2 | ||
with: | ||
path: main | ||
|
||
- uses: actions/setup-python@v2 | ||
with: | ||
python-version: '3.7' | ||
|
||
- name: Build wheels | ||
run: | | ||
python -m pip install --upgrade pip wheel | ||
cd main | ||
python setup.py bdist_wheel | ||
env: | ||
SKIP_COMPILATION: True | ||
|
||
- uses: actions/upload-artifact@v2 | ||
if: ${{ github.event_name == 'release' || github.ref == 'refs/heads/master' }} | ||
with: | ||
name: pure-python-wheels | ||
path: main/dist/*.whl |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -16,4 +16,4 @@ | |
Version number (major.minor.patch[-label]) | ||
""" | ||
|
||
__version__ = "0.19.0-dev" | ||
__version__ = "0.19.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need the
or
here?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. I think
||
is supported (link https://docs.github.com/en/actions/learn-github-actions/expressions#operators) though happy to modify if you thinkor
is better.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I misunderstood. Yea, we want this to run in both cases. We can issue a release from a non master branch (the tagged v0.xy branch), and ensure the wheels are built. Master may have since move on, so we need to be able to support both ( I think).