The problem stems from this commit to m.css. The change is described below (copied from the linked commit's message), where the "additional check" mentioned was throwing errors for us:
The use case is explicitly including a module that otherwise doesn't get
transitively imported from the parents. They were treated as a standalone
root module until now, causing quite a mess. Now they aren't, but there's
an additional check requiring the user to explicitly supply also all
parents.
Also reworks the doc deployment pipeline so that the docs are built on every PR, but only deployed on pushes to develop or main. This way we'll catch errors in the pipeline before merging PRs.
Fixes #551
The problem stems from this commit to
m.css. The change is described below (copied from the linked commit's message), where the "additional check" mentioned was throwing errors for us:Also reworks the doc deployment pipeline so that the docs are built on every PR, but only deployed on pushes to
developormain. This way we'll catch errors in the pipeline before merging PRs.