Skip to content

5.11.0

Latest
Compare
Choose a tag to compare
@lunkwill42 lunkwill42 released this 03 Oct 12:43
· 63 commits to master since this release

Removed

  • Dropped support for Python 3.7 (#2790)

Added

  • Post lifecycle event when power supplies or fans are removed (#2982)
  • Post lifecycle event when a module or chassis is deleted via the status or device history tools (#2983)
  • Database model for representing Organizationally Unique Identifiers (OUI) to identify vendors for MAC addresses
  • Script for populating database with OUIs and corresponding vendors from IEEE (#2945)
  • Module for generating JWTs (#2948)
  • Documentation for configuring and using JWT tokens in NAV API (#2618)

Changed

  • Upgraded dependencies after dropping support for Python 3.7 (#2790)
  • Changed Sphinx version to 7.4.7 (#2826)
  • Changed required PostgreSQL version to 13 (#2892)
  • Moved the test suite's web crawler complexity away from the test discovery phase to the test phase itself. This reduces the number of generated test cases from N to 2 (where N is the number of reachable NAV pages) (#2966)
  • Link to the doc for using docker for development from the README and mention what ports are used when using docker for development (#2978)
  • Many user-facing forms of the web user interface have been refactored in order to remove a dependency that keeps NAV incompatible with Python 3.11. This should not affect looks or functionality. This work is still ongoing in the master branch and we hope it will be complete by NAV version 5.12.

Fixed

  • Correctly delete an IP Device's existing function value when empty field value is submitted in the IP Device IP Device edit form (#2269)
  • Fixed crash bug when reordering filters within a filter group in Alert Profiles (#2979)
  • Fixed IPAM API crash bug that caused unnecessary error reports sent as e-mail to site admins (#2989)
  • Fixed bad tooltip grammar in ipdevinfo "degraded aggregate link" badge
  • Make the test suite easier to run under MacOS
  • Skip tests when 3rd party requirements are missing, instead of outright failing

Security

  • Ensure that CSRF token info is preserved when refactoring crispy forms to non-crispy equivalents. This means that flat_form.html and _form_content.html templates will include CSRF token info if form method is set to POST. (#3056)