Closed MindTooth closed 1 month ago
@johnphilip283 thoughts?
Hey there @MindTooth! Thank you for the PR. We'd like to be on the safer side with mkdocs-material
upgrades, so I believe limiting updates within the same x.y would be a nice way to do this. Otherwise, the rest of the changes LGTM!
I've updated the config to use allowedVersions
to limit the range.
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!
@johnphilip283 need anything more from me? :smile:
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!
Feel like I'm in a whack-a-mole game with the Stale bot. 🤣
I noticed the config was old and could need a update:
.json
endingconfig:base
toconfig:recommended
Question? One question, now that we are on the latest
mkdocs-material
, should we then remove the ignore and rather split on major/minor so that updates will still be added? Or we can limit updates within the same x.y.With the changes: