Build dev from test-pypi, use RCs #1604
Open
+34
−26
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Comment on lines
+5
to
+6
| - cron: '0 5 * * 1,3,5' # At 05:00 (12am EST) on Sunday (Monday am), Tuesday (Wednesday am), Thursday (Friday am). | ||
| #- cron: '0 10 * * *' # At 10:00 (5am EST) on every day-of-week. Use this during feature freeze. |
Collaborator
Author
There was a problem hiding this comment.
Updated the old cron job to account for UTC and added a commented out cron to use during feature freeze.
doctorperceptron
changed the title
runora95
approved these changes
Nov 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes the way we install the development versions of PennyLane, Lightning, and Catalyst (PLC) to support building from RC versions during feature freeze.
Previously, the tool would install the latest versions of PLC from test-pypi or directly from the repo. This would mean that during feature freeze the dev build pipeline would be building against the next-to-next release, rather than the release coming up. To address this, a few changes have been made to dev builds:
By pinning the upper bound of the PLC versions to be less than the next-to-next release version, the dev build pipeline will continue to use the RC pre-releases uploaded to test-pypi during feature freeze. Once the new versions of PLC are released, we can bump the dev PLC constraints long with the stable build constraints.