-
Notifications
You must be signed in to change notification settings - Fork 3
mkdocs 2.0 incompatibilites #39
Copy link
Copy link
Open
Labels
ci-buildContinuous integration, automated builds, deployment pipelines, or dev workflowsContinuous integration, automated builds, deployment pipelines, or dev workflowsdependenciesIssues involving external dependencies or upstream developmentIssues involving external dependencies or upstream developmentdomain: mkdocsMkDocs static site generator settings, theme customization, and build configurationMkDocs static site generator settings, theme customization, and build configurationtype: questionSeeks clarification, usage help, or discussion about functionality and implementationSeeks clarification, usage help, or discussion about functionality and implementation
Metadata
Metadata
Assignees
Labels
ci-buildContinuous integration, automated builds, deployment pipelines, or dev workflowsContinuous integration, automated builds, deployment pipelines, or dev workflowsdependenciesIssues involving external dependencies or upstream developmentIssues involving external dependencies or upstream developmentdomain: mkdocsMkDocs static site generator settings, theme customization, and build configurationMkDocs static site generator settings, theme customization, and build configurationtype: questionSeeks clarification, usage help, or discussion about functionality and implementationSeeks clarification, usage help, or discussion about functionality and implementation
According to this blog post, the announced v2 of
mkdocsbrings incompatibilites. This needs to be evaluated. We might need to migrate to different build tools.First step is to pin
mkdocsinrequirements.txt.