-
Notifications
You must be signed in to change notification settings - Fork 61
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
mkdocs and mkdocs-material updates #145
Comments
I am not maintainer here but I think upgrading to the latest 9.1.x material at least should be straightforward. |
Apologies but I second this need for updates. New updates has been introduced post-material-mkdocs v9.2 particularly the built-in Blog that is highly sought after by teams within my org. |
What does the scope of an update look like? I haven't looked at it and don't have a ton of familiarness with it, but someone I work with does. Any new features? |
Hi - We've just merged a change that bumps the version of mkdocs-material to The new version of |
While this update is very appreciated, it does not really solve the issue exposed here. |
@alexlorenzi, this is happening once again with: See also: |
👋 Hi, the project is currently configured with these versions
mkdocs-techdocs-core/requirements.txt
Line 4 in b91a812
mkdocs-techdocs-core/requirements.txt
Line 12 in b91a812
I understand the complexity of updating these core components and why they are pinned. HTML markup is not documented as public API, and this might break things (#66).
That being said, we are currently missing a lot of nice features and bugfixes.
What would be the best approach to update these dependencies?
Are there any automated regression tests, or specific issues to check.
Or does testing-dependencies-end-to-end is enough?
The text was updated successfully, but these errors were encountered: