Build both PDF and web in texlive-action #8
Merged
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 fixes the inconsistency issue in #5 which was trying to accelerate LaTeX building but it only moved the PDF building into texlive-action (which is the key to the acceleration) but blueprint website is left out as I wasn't sure it will work well inside texlive-action .
Soon I realized that plastex (leanblueprint relies on it to generate the web version) will need a full texlive installation for more adavanced features, e.g. the support for adding commutative diagram to both the PDF and the web page requires rendering tikz-cd to PDF then SVG images for the web page , the inconsistency breaks functionalities like this.
After fixing an issue related to Python 3.11 compatibility, both PDF and web can be built in texlive-action, hence the PR. This will also be ~1 minute faster due to less duplicated installation.