(version v2.7.0 had issues, skip straight to v2.7.1)
Breaking changes
The contact field on assets is removed and replaced by NetBox's standard contact assignments, which allow several contacts per asset, each with a role. The database migration moves existing values automatically into assignments under a new contact role named "Asset contact (migrated)", which you can rename or reassign afterwards. All API and GraphQL integrations, scripts, export templates and CSV imports referencing Asset.contact must be updated to use contact assignments instead. The asset filters contact_id and contact_group_id are replaced by NetBox's contact, contact_group and contact_role (all by ID); requests using the old names are not rejected and return unfiltered results. CSV imports that still contain a contact column fail with an "unexpected column header" error.
What's Changed
- update GraphQL query classes to use strawberry_django.field for single-object fields by @matejv in #306
- Graphql fixes by @matejv in #307
- NetBox 4.7 fixes: audit flow 500, silent bulk-add validation, changelog message, min_version bump by @cruse1977 in #302
- netbox 4.7 - additional fixes by @matejv in #304
- feat: allow contacts to be assigned to assets by @c-perronnet in #303
- Fix incorrect dependencies on squashed migrations by @svalouch in #305
New Contributors
- @cruse1977 made their first contribution in #302
- @c-perronnet made their first contribution in #303
- @svalouch made their first contribution in #305
Additional thank you to Maksym Ototiuk for reporting the issue in #306
Full Changelog: v2.6.1...v2.7.1