Repository navigation
Update pinned requirements and pin pygments == 2.18.0 due to incompatibility with sphinx-codeautolink - #2933
Conversation
|
Thank you for submitting this pull request (PR)! ✨ PlasmaPy depends on contributors like you, so we deeply appreciate it! The bottom of this page shows several checks that are run for every PR. ✅ Don't worry if something broke! We break stuff all the time. 😅 Click on "Details" to learn why a check didn't pass. Please also feel free to ask for help. We do that all the time as well! 🌸 We invite you to our weekly community meeting (2 pm ET on most Tuesdays) and office hours (3 pm ET on most Thursdays). After this PR is marked as ready for review, someone should stop by to provide a code review and offer suggestions soon. 👥 If we don't provide a review within a few days, please feel free to send us a reminder. 🎗 PlasmaPy's contributor guide has information on:
Tip 📚 For a documentation preview, click on Details next to docs/readthedocs.org:plasmapy. For cryptic documentation errors, see the documentation troubleshooting guide. Tip 🧹 Automatically fix most pre-commit.ci failures by commenting We thank you once again! 🌌 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2933 +/- ##
==========================================
- Coverage 95.28% 94.49% -0.79%
==========================================
Files 108 108
Lines 9631 9631
Branches 1451 1451
==========================================
- Hits 9177 9101 -76
- Misses 273 343 +70
- Partials 181 187 +6 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
There seem to be two issues that have arisen here...a great way to return from a month long vacation! 😺
|
I am testing if the documentation build errors are the consequence of sphinx-codeautolink not working with pygments ≥ 2.19.0
pygments == 2.18.0 due to incompatibility with sphinx-codeautolink
|
Figured it out! The |
This pull request (PR) regenerates the requirements files in
ci_requirements/that are used for running tests, building documentation, and performing other continuous integration (CI) checks. Pinning requirements files reduces the probability that a CI check will spontaneously start failing in a PR due to a breaking change in a dependency. This PR lets us find unexpected breaking changes in newly released dependencies before they get used in CI. 🛡If all checks pass ✅, please merge this PR. If any checks fail due to a breaking change in a dependency 🚨, please fix the problem and get the checks to pass again.
Note
These changes were generated by running
nox -s requirementsin the top-level directory of the repository, using therequirementssession defined innoxfile.py. This Nox session uses uv to regenerate requirements files. The workflow is defined in.github/workflows/update-pinned-reqs.yml. For more information, seeci_requirements/README.md.Important
When it is necessary to put a temporary upper limit on the allowed versions of a dependency in
pyproject.toml, please create an issue that this upper limit should be removed.