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

Add a time-based "out of date" warning for NetBox releases #9078

New Issue
Open
opened 2025-12-29 20:45:08 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:45:08 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jan 10, 2024).

NetBox version

v3.7.0

Feature type

New functionality

Proposed functionality

If the running NetBox version was released more than a certain number of days ago, display an alert on the web UI letting users (probably just administrators) know they should upgrade. This could be displayed at the top or bottom of the main page.

This could be accomplished by introducing a new OUTDATED_RELEASE_DAYS configuration parameter (name TBD) which defaults to perhaps 90 days. Setting this parameter to zero would disable the warning.

Note that the determination is being made by comparing the current date to the release date, as opposed to actively checking for the most recent release (which is also possible). To facilitate this, we would also need to encode the release data along with the version number in each release.

Use case

NetBox typically publishes a new patch release roughly every two weeks on average, yet we find that many users lag far behind the latest stable release when raising issues. This mechanism would provide a reminder to keep NetBox deployments up to date.

Admittedly, there's some overlap with the release checking feature mentioned above. However, this is a purely passive check whereas the former is actively querying for the latest release (and is disabled by default). The time-based warning would better suit deployments which have been isolated from the Internet for security reasons.

Database changes

None

External dependencies

None

Originally created by @jeremystretch on GitHub (Jan 10, 2024). ### NetBox version v3.7.0 ### Feature type New functionality ### Proposed functionality If the running NetBox version was released more than a certain number of days ago, display an alert on the web UI letting users (probably just administrators) know they should upgrade. This could be displayed at the top or bottom of the main page. This could be accomplished by introducing a new `OUTDATED_RELEASE_DAYS` configuration parameter (name TBD) which defaults to perhaps 90 days. Setting this parameter to zero would disable the warning. Note that the determination is being made by comparing the current date to the release date, as opposed to actively checking for the most recent release (which is [also possible](https://docs.netbox.dev/en/stable/configuration/miscellaneous/#release_check_url)). To facilitate this, we would also need to encode the release data along with the version number in each release. ### Use case NetBox typically publishes a new patch release roughly every two weeks on average, yet we find that many users lag far behind the latest stable release when raising issues. This mechanism would provide a reminder to keep NetBox deployments up to date. Admittedly, there's some overlap with the release checking feature mentioned above. However, this is a purely passive check whereas the former is actively querying for the latest release (and is disabled by default). The time-based warning would better suit deployments which have been isolated from the Internet for security reasons. ### Database changes None ### External dependencies None
adam added the type: featurecomplexity: mediumnetboxstatus: backlog labels 2025-12-29 20:45:08 +01:00
adam commented 2025-12-29 20:45:08 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Jan 18, 2024):

For isolated instances, its likely the users browser will have public internet access so in-browser javascript could be used to attempt to pull the current release version from github or some other website, if thats also blocked then failing back to a time based alert would be a good path.

@ITJamie commented on GitHub (Jan 18, 2024): For isolated instances, its likely the users browser will have public internet access so in-browser javascript could be used to attempt to pull the current release version from github or some other website, if thats also blocked then failing back to a time based alert would be a good path.
adam commented 2025-12-29 20:45:08 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 14, 2024):

Blocked by #15908

@jeremystretch commented on GitHub (May 14, 2024): Blocked by #15908
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 complexity: medium netbox status: backlog 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#9078
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?