starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Show supported Netbox Version on Plugins Overview page #11180

New Issue
Closed
opened 2025-12-29 21:41:27 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:41:27 +01:00
Owner
Copy Link

Originally created by @peterbaumert on GitHub (May 15, 2025).

NetBox version

v4.3.0

Feature type

Change to existing functionality

Proposed functionality

I would like to see the min and/or at least the max supported Netbox version on the Plugins Overview page.

Use case

Before upgrading Netbox I always have to check each plugin by itself which is the supported Netbox version to not loose the Plugins functionality after upgrade. Currently this is a manual annoying task. It would reduce work and headaches quite significantly.

Database changes

I dont think there are any, since the catalog data comes via API.

External dependencies

Data seems to already be available in the api request to the catalog e.g.:

        "netbox_min_version": "4.2.4",
        "netbox_max_version": "4.2.9",
Originally created by @peterbaumert on GitHub (May 15, 2025). ### NetBox version v4.3.0 ### Feature type Change to existing functionality ### Proposed functionality I would like to see the min and/or at least the max supported Netbox version on the Plugins Overview page. ### Use case Before upgrading Netbox I always have to check each plugin by itself which is the supported Netbox version to not loose the Plugins functionality after upgrade. Currently this is a manual annoying task. It would reduce work and headaches quite significantly. ### Database changes I dont think there are any, since the catalog data comes via API. ### External dependencies Data seems to already be available in the api request to the catalog e.g.: ``` "netbox_min_version": "4.2.4", "netbox_max_version": "4.2.9", ```
adam added the type: feature label 2025-12-29 21:41:27 +01:00
adam closed this issue 2025-12-29 21:41:27 +01:00
adam commented 2025-12-29 21:41:28 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (May 15, 2025):

The compatibility information is available on each plugin's detail view; this is all we can support as showing the version window in the list view for all table items introduces complexity that may be too great. This information can also be fetched via the API.

@bctiemann commented on GitHub (May 15, 2025): The compatibility information is available on each plugin's detail view; this is all we can support as showing the version window in the list view for all table items introduces complexity that may be too great. This information can also be fetched via the API.
adam commented 2025-12-29 21:41:30 +01:00
Author
Owner
Copy Link

@peterbaumert commented on GitHub (May 15, 2025):

But showing the latest versions compatability would be enough wouldnt it? Clicking each plugin is working yeah but annoying :)

@peterbaumert commented on GitHub (May 15, 2025): But showing the latest versions compatability would be enough wouldnt it? Clicking each plugin is working yeah but annoying :)
adam commented 2025-12-29 21:41:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 15, 2025):

But showing the latest versions compatability would be enough wouldnt it?

No, because it provides incomplete information. Users need to be aware of all potential upgrade options.

@jeremystretch commented on GitHub (May 15, 2025): > But showing the latest versions compatability would be enough wouldnt it? No, because it provides incomplete information. Users need to be aware of all potential upgrade options.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11180
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?