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

Display updates available for current major version #6939

New Issue
Closed
opened 2025-12-29 19:47:00 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:47:00 +01:00
Owner
Copy Link

Originally created by @PieterL75 on GitHub (Sep 7, 2022).

NetBox version

v3.3.2

Feature type

Change to existing functionality

Proposed functionality

The 'new update available' always shows the newest available version.
It would benefit, if the updates for the current main version are displayed, in addition to the latest available.

Use case

We have to stick with 3.2 due to the API changes in 3.3
The update versions show the latests availabe (3.3.2). but not if there is a new version for the current train (3.2.9)
This causes us to miss out on patch releases of the current major/minor version

Database changes

No response

External dependencies

No response

Originally created by @PieterL75 on GitHub (Sep 7, 2022). ### NetBox version v3.3.2 ### Feature type Change to existing functionality ### Proposed functionality The 'new update available' always shows the newest available version. It would benefit, if the updates for the current main version are displayed, in addition to the latest available. ### Use case We have to stick with 3.2 due to the API changes in 3.3 The update versions show the latests availabe (3.3.2). but not if there is a new version for the current train (3.2.9) This causes us to miss out on patch releases of the current major/minor version ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:47:00 +01:00
adam closed this issue 2025-12-29 19:47:00 +01:00
adam commented 2025-12-29 19:47:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 7, 2022):

We have to stick with 3.2 due to the API changes in 3.3

There are no v3.2 releases after v3.3.0, so once you've upgraded to the last v3.2 release, you can simply disable the release checking if desired by setting RELEASE_CHECK_URL to None.

@jeremystretch commented on GitHub (Sep 7, 2022): > We have to stick with 3.2 due to the API changes in 3.3 There are no v3.2 releases after v3.3.0, so once you've upgraded to the last v3.2 release, you can simply disable the release checking if desired by setting [`RELEASE_CHECK_URL`](https://docs.netbox.dev/en/stable/configuration/miscellaneous/#release_check_url) to `None`.
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#6939
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?