master to test-v2-master - #1450
Merged
Merged
Conversation
## Summary Update `v2` with/ changes to `v1` demonstrations directory using `qml sync-v2` with @rashidnhm 's recent updates to the demo. --------- Co-authored-by: Andrija Paurevic <46359773+andrijapau@users.noreply.github.com>
## Issue - `:doc:` references for intersphinx (disabled by default in Sphinx 5.0+) ## Changes - Fix sphinx interlinking for external projects to allow `:doc:` ## Testing - Check that links to doc work in the following demo in [PR preview](https://qml-build-previews.pennylane.ai/pull_request_build_preview/1426/qml/demos/tutorial_qubit_rotation#optimization) which is broken in [production](https://pennylane.ai/qml/demos/tutorial_qubit_rotation) ## Snaps ### PR preview  ### Live 
The `master` and `dev` branch builds are used for two purposes: - As a canary to surface potential issues introduced into the demos via changes to the underlying dependencies - In the [qml-diff-checker workflow](https://github.com/PennyLaneAI/qml-diff-checker) to compare the two builds priori to a new release of PennyLane. This PR adjusts the build frequency of these pipelines, as well as the retention period of the resulting build artifacts: - Two build were occurring over the weekend, which is redundant as the odds of a material change between Saturday and Sunday is low, and no one is likely to action it anyway during that time. The new cron frequency builds these pipelines Monday morning, Wednesday morning, and Friday morning at 12am so any changes are apparent at the start of the work day. - The retention period of the consolidated artifacts is bumped from 1 day (default) to 3 days for these pipelines, so that there is always a fresh artifact associated with a successful run of these pipelines. This is required for the [qml-diff-checker workflow](https://github.com/PennyLaneAI/qml-diff-checker).
This pull request updates the deployment workflow configuration in `.github/workflows/v2-deploy-pr.yml`. The changes focus on improving the logic for determining pull request identifiers and updating the deployment environment. Workflow logic updates: * Replaced the condition for checking `updated_demos` with a condition for checking `pr_id` to ensure accurate identification of pull requests. (`[.github/workflows/v2-deploy-pr.ymlL83-R88](diffhunk://#diff-bb1f887f50cfc7839e56ce823ccf5b9b7a4a07bfd475c5646b28105610511bf3L83-R88)`) Environment configuration changes: * Updated the deployment environment from `'swc-dev'` to `'swc-staging'` to align with staging requirements. (`[.github/workflows/v2-deploy-pr.ymlL83-R88](diffhunk://#diff-bb1f887f50cfc7839e56ce823ccf5b9b7a4a07bfd475c5646b28105610511bf3L83-R88)`) --------- Co-authored-by: Paul Finlay <50180049+doctorperceptron@users.noreply.github.com>
Following the release guide, > Create a new branch from dev, and open a PR to merge the new branch into master. Once merged in, ensure that master subsequently builds successfully. This merges all changes from `dev` that occured for the release of `v0.42.0` PL ecosystem. PR is a follow up to #1441 where we updated dependencies in `dev`. This PR was created with, - Make branch `final-dev-v0420` after pulling latest `dev` - Create PR targeting master --------- Co-authored-by: GitHub Nightly Merge Action <actions@github.com> Co-authored-by: josephbowles <54283511+josephbowles@users.noreply.github.com> Co-authored-by: Rashid N H M <95639609+rashidnhm@users.noreply.github.com> Co-authored-by: Paul Finlay <50180049+doctorperceptron@users.noreply.github.com> Co-authored-by: doctorperceptron <paul@xanadu.ai> Co-authored-by: dwierichs <david.wierichs@xanadu.ai> Co-authored-by: JerryChen97 <chenys13@outlook.com> Co-authored-by: Alan Martin <53958929+Alan-eMartin@users.noreply.github.com> Co-authored-by: Mudit Pandey <18223836+mudit2812@users.noreply.github.com> Co-authored-by: Astral Cai <astral.cai@xanadu.ai> Co-authored-by: Luis Alfredo Nuñez Meneses <alfredo.nunez@xanadu.ai>
|
👋 Hey, looks like you've updated some demos! 🐘 Don't forget to update the Please hide this comment once the field(s) are updated. Thanks! |
|
Thank you for opening this pull request. You can find the built site at this link. Deployment Info:
Note: It may take several minutes for updates to this pull request to be reflected on the deployed site. |
justinpickering
temporarily deployed
to
swc-staging
July 17, 2025 21:10 — with
GitHub Actions
Inactive
justinpickering
temporarily deployed
to
swc-staging
July 17, 2025 21:22 — with
GitHub Actions
Inactive
justinpickering
temporarily deployed
to
swc-staging
July 18, 2025 12:48 — with
GitHub Actions
Inactive
justinpickering
temporarily deployed
to
swc-staging
July 18, 2025 13:16 — with
GitHub Actions
Inactive
justinpickering
temporarily deployed
to
swc-staging
July 18, 2025 13:42 — with
GitHub Actions
Inactive
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
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.
Changes