-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sphinx 6 support #660
Comments
Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗 |
I have an issue on my CI/CD when trying to upgrade to Sphinx 6:
More on: https://github.com/staticdev/human-readable/actions/runs/3804136558/jobs/6471114085 |
FYI, I yanked all old version of myst-parser, with no sphinx pinnings, from PyPI, to stop any unexpected downgrading |
Please @chrisjsewell can you create a new release so that we can upgrade sphinx in our projects? |
I second that request, thanks! |
+1 |
I saw that v0.19.0 that fixes this is now out, thanks for the release! |
Thanks! |
Excellent! Thanks 👍 |
Describe the bug
context
When I do
poetry update
withmyst-parser = "*'
withsphinx = "*"
(atexpectation
I expected
myst-parser
to stay at the latest version with sphinx 6.0, e.g.bug
But instead, myst-parser is downgraded to 0.3.2
Here's an error message I ran into...
problem
This is a problem for people upgrading to sphinx 6.0, released 5 hours ago - Sphinx docs, Release notes
It's due to
<6
being pinned:MyST-Parser/pyproject.toml
Line 42 in c2f0416
Reproduce the bug
Update
sphinx
to 6.x whem myst-parser is at 0.18.1List your environment
The text was updated successfully, but these errors were encountered: