CI/docs: Some fixes for CF Pages publishing
Description
- Disables beta/rc tags being published to live page
- Runs version update step for
workflow_dispatchas well - Sphinx output is now created without
.htmlsuffix in Links to avoid unnecessary redirects on CF's platform
Note: This would break browing the docs locally unless they're hosted on a webserver that is configured to support extension-less URLs.
Motivation and Context
Fixing good.
How Has This Been Tested?
Tested on my fork: https://obs-docs-test.pages.dev/
Types of changes
- Bug fix (non-breaking change which fixes an issue)
- Tweak (non-breaking change to improve existing functionality)
Checklist:
- [x] My code has been run through clang-format.
- [x] I have read the contributing document.
- [x] My code is not on the master branch.
- [x] The code has been tested.
- [x] All commit messages are properly formatted and commits squashed where appropriate.
- [x] I have included updates to all appropriate documentation.
Note: This would break browing the docs locally unless they're hosted on a webserver that is configured to support extension-less URLs.
This is unfortunate. If I'm checking docs builds, I load them locally in a browser without running a webserver. @WizardCM thoughts?
I think there are two ways to keep offline docs working:
- Only use extension-less links on
workflow_disaptchortagsso normal pushes create regular docs - Generate second set of docs with different settings for publishing only
@derrod I vote for the second option. Docs should always generate user-usable ZIPs, including alongside CF Pages runs.
Updated based on @WizardCM's and @RytoEX's feedback so that the workflow generates a separate artifact for CF pages and the normal artifact remains locally browseable.
Artifact has HTML files, though the version in the docs is seemingly outdated.

Artifact has HTML files, though the version in the docs is seemingly outdated.
The step to update the version number doesn't run for PRs. Not sure why that was originally done.
Artifact has HTML files, though the version in the docs is seemingly outdated.
The step to update the version number doesn't run for PRs. Not sure why that was originally done.
Then I suppose it's a non-issue. Will merge shortly.