Skip to content
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

chore: relax azure-quantum version requirement #12

Merged
merged 4 commits into from
Mar 13, 2023

Conversation

Shadow53
Copy link
Contributor

Uses the same changes from #11 but also updates poetry.lock.

Copy link
Contributor

@kalzoo kalzoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Shadow53 👍

@Shadow53 Shadow53 merged commit 8e22555 into main Mar 13, 2023
@Shadow53 Shadow53 deleted the relax-azure-quantum-version branch March 13, 2023 19:00
@Shadow53
Copy link
Contributor Author

@vxfield this should fix the issue you were seeing in #11.

@vxfield
Copy link

vxfield commented Mar 13, 2023

Great!
@Shadow53, @dbanty @kalzoo, how soon can you release pyquil-for-azure-quantum 0.0.3 with this fix?
We would like to test it against the latest azure-quantum package.

@vxfield
Copy link

vxfield commented Feb 28, 2024

@Shadow53, @dbanty @kalzoo, I just checked that pyquil-for-azure-quantum 0.0.3 was not released yet.
Could you release it so that it include this fix?

@MarquessV
Copy link
Contributor

@vxfield Thanks for the heads up! I just released 0.0.3 with the fix.

@vxfield
Copy link

vxfield commented Mar 1, 2024

@MarquessV,

Actually, I missed one important thing and I apologize for that.
We have recently bumped the major version of azure-quantum from 0 to 1 and the latest version is 1.2.1.

I created PR #15 with the necessary changes.
Could you review it, and if everything is okay, merge and release a new version (0.0.4) of pyquil-for-azure-quantum?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants