Repository navigation
fix: pin Python API documentation build dependencies - #71
Merged
Merged
Conversation
|
☁️ Cloudflare Pages preview: https://58729dfa.zvec-web.pages.dev |
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.
Summary
The production build after merging #67 failed while generating the Python API reference:
mkdocstrings==1.0.6calledHighlightwithout themdargument required bypymdown-extensions12.2 and later. The PR build had passed with 12.1, but both workflows installed unpinned documentation tools and production resolved 12.3.Add a shared requirements file with the documentation tool versions from the successful September 23 PR build, including
pymdown-extensions==12.1. Both production and PR preview builds now install from that file, and the local build instructions use it too.Validation
mkdocs buildin a fresh Python 3.10 virtual environment using the shared requirements andzvec==0.7.0(2.46 seconds).pip checkandgit diff --check.Previous runs: passing PR build, failing production build.