Remove pining mkdocstrings to 0.17.0 #6374

Closed
opened 2025-12-29 19:39:58 +01:00 by adam · 3 comments
Owner

Originally created by @L1ghtn1ng on GitHub (Apr 19, 2022).

Proposed Changes

Remove the pining of mkdocstrings in base requirements.txt and unpin jinja2 as well

Justification

There has been a new release of https://github.com/mkdocstrings/mkdocstrings/releases which now supports jinja2 3.1 release

Originally created by @L1ghtn1ng on GitHub (Apr 19, 2022). ### Proposed Changes Remove the pining of mkdocstrings in base requirements.txt and unpin jinja2 as well ### Justification There has been a new release of https://github.com/mkdocstrings/mkdocstrings/releases which now supports jinja2 3.1 release
adam closed this issue 2025-12-29 19:39:58 +01:00
Author
Owner

@DanSheps commented on GitHub (Apr 19, 2022):

This issue is pending closure as it does not conform to one of the provided templates as required by the contributing guide. If you'd like to request that your issue be re-opened, please first update the content so that it matches the appropriate template (this may require rewriting your issue entirely).

@DanSheps commented on GitHub (Apr 19, 2022): This issue is pending closure as it does not conform to one of the [provided templates](https://github.com/netbox-community/netbox/issues/new/choose) as required by the [contributing guide](https://github.com/netbox-community/netbox/blob/master/CONTRIBUTING.md). If you'd like to request that your issue be re-opened, please first update the content so that it matches the appropriate template (this may require rewriting your issue entirely).
Author
Owner

@jeremystretch commented on GitHub (Apr 19, 2022):

Thanks for the heads up, but we don't need an issue for this. Dependencies are re-evaluated on each release.

@jeremystretch commented on GitHub (Apr 19, 2022): Thanks for the heads up, but we don't need an issue for this. Dependencies are re-evaluated on each release.
Author
Owner

@L1ghtn1ng commented on GitHub (Apr 19, 2022):

Fair enough just wanted to point it out as that release has been a few months out as it turns out

On 19 Apr 2022, at 15:05, Jeremy Stretch @.***> wrote:



Thanks for the heads up, but we don't need an issue for this. Dependencies are re-evaluated on each release.


Reply to this email directly, view it on GitHubhttps://github.com/netbox-community/netbox/issues/9163#issuecomment-1102699391, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA3V2QRDHRIAZXUG3RHRUPTVF24TTANCNFSM5TXB2HRA.
You are receiving this because you authored the thread.Message ID: @.***>

@L1ghtn1ng commented on GitHub (Apr 19, 2022): Fair enough just wanted to point it out as that release has been a few months out as it turns out On 19 Apr 2022, at 15:05, Jeremy Stretch ***@***.***> wrote:  Thanks for the heads up, but we don't need an issue for this. Dependencies are re-evaluated on each release. — Reply to this email directly, view it on GitHub<https://github.com/netbox-community/netbox/issues/9163#issuecomment-1102699391>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA3V2QRDHRIAZXUG3RHRUPTVF24TTANCNFSM5TXB2HRA>. You are receiving this because you authored the thread.Message ID: ***@***.***>
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6374