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

Print NetBox version when running upgrade.sh #8955

New Issue
Closed
opened 2025-12-29 20:43:18 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:43:18 +01:00
Owner
Copy Link

Originally created by @markkuleinio on GitHub (Dec 13, 2023).

Originally assigned to: @markkuleinio on GitHub.

NetBox version

v3.7-beta1

Feature type

New functionality

Proposed functionality

When running upgrade.sh it would be beneficial to see what is the actual NetBox version that is being prepared.

Something like

echo "NetBox version is $(grep ^VERSION netbox/netbox/settings.py | cut -d\' -f2)"
NetBox version is 3.7-beta1

would maybe be enough somewhere in the beginning of upgrade.sh.

Use case

Sometimes there is confusion when symlinking or pulling the versions here and there and running upgrade.sh, what is the actual codebase that is being activated.

Database changes

None

External dependencies

None

Originally created by @markkuleinio on GitHub (Dec 13, 2023). Originally assigned to: @markkuleinio on GitHub. ### NetBox version v3.7-beta1 ### Feature type New functionality ### Proposed functionality When running upgrade.sh it would be beneficial to see what is the actual NetBox version that is being prepared. Something like ``` echo "NetBox version is $(grep ^VERSION netbox/netbox/settings.py | cut -d\' -f2)" NetBox version is 3.7-beta1 ``` would maybe be enough somewhere in the beginning of upgrade.sh. ### Use case Sometimes there is confusion when symlinking or pulling the versions here and there and running upgrade.sh, what is the actual codebase that is being activated. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 20:43:18 +01:00
adam closed this issue 2025-12-29 20:43:18 +01:00
adam commented 2025-12-29 20:43:19 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Dec 13, 2023):

I would add, it might be wise too break until there is input after that (unless running non-interactively).

@DanSheps commented on GitHub (Dec 13, 2023): I would add, it might be wise too break until there is input after that (unless running non-interactively).
adam commented 2025-12-29 20:43:19 +01:00
Author
Owner
Copy Link

@markkuleinio commented on GitHub (Dec 16, 2023):

I can submit the PR. I can add the pause in interactive mode (let's discuss in the PR if something needs adjusting).

@markkuleinio commented on GitHub (Dec 16, 2023): I can submit the PR. I can add the pause in interactive mode (let's discuss in the PR if something needs adjusting).
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 status: accepted 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#8955
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?