-
Notifications
You must be signed in to change notification settings - Fork 193
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
Rendering with current markdown version #571
Comments
Not directly related to this here #391 but could be fixed in the same go ;-) |
Just for reference: |
Nice, good find @phue - if they are depreciating something does that mean that we should update a method we're using somewhere? Though I think we're not actually using that method, so I guess it's only a cross-package compatibility thing and we're fine.. |
Hmm, looks like the feedstock for this package is a little out of love: https://github.com/conda-forge/pymdown-extensions-feedstock/pulls |
Yeah :-( |
Have bumped the version and re-rendered with conda smithy. Hopefully that will fix it. At least the Azure builds will still be there if it fails so that we can see what is going wrong.. |
ok, tests are passing so it should be good to merge ✅ - just needs someone to merge it now 🤞 |
I pinged the conda-forge core team and got myself added as a maintainer, so the above PR was merged and hopefully we can move this forward now.. |
This should be fixed now. |
When using the latest (V1.9) template, we replaced the R code with a Python script. This is broken when updating the
markdown
package in the container used for any pipeline and results in e.g. errors like this:The text was updated successfully, but these errors were encountered: