Update dependency netbox-community/netbox to v4.5.2 #58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.4.7→4.5.2Release Notes
netbox-community/netbox (netbox-community/netbox)
v4.5.2: - 2026-02-03Compare Source
Enhancements
cabledfilter for interfaces in GraphQL API?omit=parameterPerformance Improvements
get_by_natural_key()to resolve ContentTypesBug Fixes
SyncErrorexception when Git URL contains an embedded usernameattribute_datain ModuleType YAML exportscopefield whenscope_typechangesstaff_onlypermissionAttributeErrorexception when checking for latest releasev4.5.1: - 2026-01-20Compare Source
Enhancements
/api/ipam/prefixes/<id>/available-ips/REST API endpointBug Fixes
RelatedObjectDoesNotExistexception when importing modules into unnamed devicesdata_fileassignment for ConfigContext and ConfigContextProfile via the REST APIValueErrorexception whenAPI_TOKEN_PEPPERSis not definedfieldsparameter for job, object change, and object type REST API endpointsAPISelectchoices resolutionDEFAULT_LANGUAGEis setAuthenticationFailedexception when using an invalid API token to fetch media filesv4.5.0: - 2026-01-06Compare Source
Breaking Changes
id: 123becomesid: {exact: 123 }.render_configpermission for the applicable object type.ALLOW_TOKEN_RETRIEVALconfig parameter has been removed./api/dcim/cable-terminations/REST API endpoint is now read-only. Cable terminations must be set on cables directly via the/api/dcim/cables/endpoint.is_staffhas been removed from theUsermodel./api/extras/object-types/REST API endpoint has been removed. (Use/api/core/object-types/instead.)modelin payload data. (Referenceobject_typeinstead, which includes the parent app label.)core.models.contenttypeshas been removed (replaced in v4.4 bycore.models.object_types).load_yaml()andload_json()utility methods have been removed from the base class for custom scripts.New Features
Lookup Modifiers in Filter Forms (#7604)
Most object list filters within the UI have been extended to include optional lookup modifiers to support more complex queries. For instance, filters for numeric values now include a dropdown where a user can select "less than," "greater than," or "not" in addition to the default equivalency match. The specific modifiers available depend on the type of each filter. Plugins can register their own filtersets using the
register_filterset()decorator to enable this new functionality.(Note that this feature does not introduce any new filters. Rather, it makes available in the UI filters which already exist.)
Improved API Authentication Tokens (#20210)
This release introduces a new version of API token (v2) which implements several security improvements. HMAC hashing with a cryptographic pepper is used to authenticate these tokens, obviating the need to store plaintexts. The new tokens also employ a non-sensitive key which can be shared to identify tokens without divulging their plaintexts. We've also adopted the standard "bearer" HTTP header format, as shown below.
Note that v2 token keys are prefixed with the fixed string
nbt_, which can be used to aid in secret detection.Backward compatibility with legacy (v1) tokens is retained in this release. However, users are strongly encouraged to begin using only v2 tokens, as support for legacy tokens will be removed in NetBox v4.7.
Object Ownership (#20304)
An optional
ownerforeign key field has been added to most models. This enables the assignment of objects to a new Owner model, which represents a set of users and/or groups. Through this relationship, we can now convey ownership of objects within NetBox natively, without needing to rely on the assignment of tags or custom fields.(Note that ownership differs significantly in function from tenancy. Ownership determines the parties responsible for the maintenance of an object, whereas as tenancy conveys an operational dependency.)
Advanced Port Mappings (#20564)
The previous many-to-one mapping of front to rear ports has been expanded to support bidirectional mappings. The
rear_portandrear_port_positionfields on the FrontPort model have been replaced with an intermediary PortMapping model, which supports any number of assignments between front port/position pair and a rear port/position pair. This change unlocks the ability to model complex inline devices that swap individual fiber pairs between cables.Cable Profiles (#20788)
Cables can now be assigned profiles which determine how they are treated for path tracing. A profile indicates the number of discrete parallel channels or lanes carried by the cable among its endpoints. For example, a 1-to-4 breakout cable has four lanes, shared at one end via a common termination and split out at the other end to four separate terminations. Profiles, when assigned, enable NetBox to more accurately trace a specific connection within a cable, rather than the cable as a whole.
The assignment of cable profiles is optional: Cable tracing will continue to operate as before for cables with no profile assigned.
Enhancements
render_configpermission, which is now required to render a device or virtual machine configurationstart_on_bootchoice field for virtual machinescolorfield for device type power outletsALLOW_TOKEN_RETRIEVALconfig parameter)enabledboolean field to API tokenscommentsfield to all subclasses ofOrganizationalModelrender_configpermission to view a rendered device/VM configuration in the UI/api/authentication-check/REST API endpoint for validating authentication tokensPlugins
PrimaryModel,OrganizationalModel, andNestedGroupModelto the plugins API, as well as their respective base classes for various resourcesOther Changes
is_stafffrom theUsermodelGFKSerializerFieldfor representing generic foreign keys in API serializers/api/extras/object-types/modelkey from webhook payload datacore.models.contenttypesload_yaml()andload_json()utility methods from theBaseScriptclassBaseModelas the global base class for modelsv4.4.10: - 2026-01-06Compare Source
Enhancements
Bug Fixes
ValueErrorexception when saving a site with an assigned prefixv4.4.9: - 2025-12-23Compare Source
Enhancements
Bug Fixes
devicetype_countfrom nested manufacturer to correct OpenAPI schemaparent_bayduring device bulk import when tags are presentAttributeErrorexception triggered by event rules associated with an object that supports file attachmentsmodulefield on ModuleBayon_delete=RESTRICTthe same asCASCADErear_port_idv4.4.8: - 2025-12-09Compare Source
Enhancements
Bug Fixes
{module}resolution of components of child modulesConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.