v2.4.1 — Active Journal/Changelog tab fix; track netbox-custom-objects v0.5.1

Highlights

• Fixes #15 — Active CSS class now appears on Journal/Changelog tabs on Custom Object detail pages. The 2.1.0 template-override refactor replaced upstream's hardcoded <li> blocks with {% model_view_tabs object %}, but upstream's view injects "journal" / "changelog" as a string while model_view_tabs compares against a ViewTab object — so the active class was never emitted. Fix renders Journal/Changelog as hardcoded <li> blocks and introduces {% plugin_extra_tabs %} to render registry-driven combined/typed tabs without duplicating the auto-registered Journal/Changelog views.
• Tracks netbox-custom-objects v0.5.1 — PluginConfig.min_version bumped 4.5.0 → 4.5.2 (mirrors upstream's #511 NetBox floor). Runtime gate now requires netbox-custom-objects >= 0.5.1. No plugin code-logic changes needed: our query helpers already filter by instance.pk so upstream's #508 fix doesn't affect us, and the M2M path_infos repair from #483 is applied inside CustomObjectType.get_model() (called per request, inherited for free).

Compatibility

• NetBox: 4.5.2 – 4.6.x
• netbox-custom-objects: ≥ 0.5.1 (enforced at startup via ImproperlyConfigured)

Upstream follow-up (not in this release)

The cleaner fix for the Journal/Changelog tab issue lives in netbox-custom-objects itself — CustomObjectJournalView.get() / CustomObjectChangeLogView.get() should pass "tab": self.tab (the ViewTab object) instead of the string literal. Worth filing as a one-liner against netboxlabs/netbox-custom-objects; once merged, the hardcoded <li> blocks and the plugin_extra_tabs tag can be retired and we go back to a single {% model_view_tabs object %}.

See CHANGELOG.md for the full entry with file-level references.