This can be closed, except that it looks as if, when we updated skpkg, we may have missed changing the m2r dependency to m2r2 so the docs are not building again. @zmx27 or @stevenhua0320 please could you take a look? I think it is a simple one line fix in requirements/docs.txt
Also, I don't see a release issue template here. This makes me a bit nervous that this wasn't skpkg'ed correctly. Please could you quickly check that too. We need a release issue for 1.6.0. Thanks.
I think it is a simple one line fix in requirements/docs.txt
I have now changed m2r to m2r2 in requirements/docs.txt. Sorry about missing this.
Also, I don't see a release issue template here. This makes me a bit nervous that this wasn't skpkg'ed correctly.
I looked back into the repo and it seemed like there was a formatting error in the issue template, which was why it wasn't showing up properly. I don't know why this didn't come up when I first ran package update. To ensure I didn't skpkg anything incorrectly, I quickly reran package update in my repo and scanned through the changes it made to see if I needed to make any other changes, and I found none.
Activity
sbillinge commented on Mar 27, 2026
This can be closed, except that it looks as if, when we updated skpkg, we may have missed changing the m2r dependency to m2r2 so the docs are not building again. @zmx27 or @stevenhua0320 please could you take a look? I think it is a simple one line fix in requirements/docs.txt
sbillinge commented on Mar 27, 2026
Also, I don't see a release issue template here. This makes me a bit nervous that this wasn't skpkg'ed correctly. Please could you quickly check that too. We need a release issue for 1.6.0. Thanks.
zmx27 commented on Mar 27, 2026
I have now changed m2r to m2r2 in requirements/docs.txt. Sorry about missing this.
I looked back into the repo and it seemed like there was a formatting error in the issue template, which was why it wasn't showing up properly. I don't know why this didn't come up when I first ran package update. To ensure I didn't skpkg anything incorrectly, I quickly reran package update in my repo and scanned through the changes it made to see if I needed to make any other changes, and I found none.