Closed trungleduc closed 1 year ago
Added a test for nbconvert
< 7.6.0
Should this be backported?
The execution time (in milliseconds) are grouped by test file, test type and browser. For each case, the following values are computed: min <- [1st quartile - median - 3rd quartile] -> max.
It looks like GitHub is running out of osx runner
Should this be backported?
Yes, only to 0.4.x
since 0.3.x
works with nbconvert
<7
@meeseeksdev please backport to 0.4.x
Owee, I'm MrMeeseeks, Look at me.
There seem to be a conflict, please backport manually. Here are approximate instructions:
git checkout 0.4.x
git pull
Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 f416ab5134cee990920d157f333103d6873dcc34
You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #1333: Add nbconvert version check'
git push YOURFORK 0.4.x:auto-backport-of-pr-1333-on-0.4.x
"Backport PR #1333 on branch 0.4.x (Add nbconvert version check)"
And apply the correct labels and milestones.
Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!
Remember to remove the Still Needs Manual Backport
label once the PR gets merged.
If these instructions are inaccurate, feel free to suggest an improvement.
References
Due to the non-backward compatible change in
nbconvert
7.6.0 on markdown rendering,VoilaMarkdownRenderer
class needs to be aware of thenbconvert
version.Code changes
User-facing changes
Backwards-incompatible changes