Update doc build to correctly get version #15540
Merged
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/15540
Note: Links to docs will display an error until the docs builds have been completed. ⏳ 46 Pending, 1 Unrelated FailureAs of commit 8a4c6e0 with merge base d361573 ( FLAKY - The following job failed but was likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
meta-cla
bot
added
the
CLA Signed
svekars
added
module: doc
GregoryComer
approved these changes
Nov 6, 2025
Member
|
@pytorchbot cherry-pick --onto release/1.0 -c docs |
pytorchbot
pushed a commit
that referenced
this pull request
Nov 6, 2025
- Update the theme version to to pull the wheel from pypi - Change how we obtain the version in the CI. - Updated to properly parse `RELEASE` variable - Fixed `Makefile` to use `RELEASE=true` instead of `RELEASE=1` for consistency - Workflow sets `RELEASE=true` only for tagged releases (e.g., `v1.1.0`) - Main branch builds with `<meta name="robots" content="noindex">` tag - Release builds remain indexable by search engines cc @mergennachin @byjlw (cherry picked from commit 692825d)
Collaborator
Cherry picking #15540The cherry pick PR is at #15652 The following tracker issues are updated: Details for Dev Infra teamRaised by workflow job |
abhinaykukkadapu
pushed a commit
to abhinaykukkadapu/executorch
that referenced
this pull request
Nov 6, 2025
- Update the theme version to to pull the wheel from pypi - Change how we obtain the version in the CI. - Updated to properly parse `RELEASE` variable - Fixed `Makefile` to use `RELEASE=true` instead of `RELEASE=1` for consistency - Workflow sets `RELEASE=true` only for tagged releases (e.g., `v1.1.0`) - Main branch builds with `<meta name="robots" content="noindex">` tag - Release builds remain indexable by search engines cc @mergennachin @byjlw
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.
RELEASEvariableMakefileto useRELEASE=trueinstead ofRELEASE=1for consistencyRELEASE=trueonly for tagged releases (e.g.,v1.1.0)<meta name="robots" content="noindex">tagcc @mergennachin @byjlw