v7.0.1 - Post-Release Fixes for v7.0.0.

INEX installed v7.0.0 in production during a maintenance window earlier this week, and we observed a small number of issues that are corrected in this release.

All UI and unit testing have passed for this release details in 53cf8f8.

Improvements and Fixes Relating to v7.0.0

• [UI] Some typo fixes where contributed in #939, which prompted a more thorough review in ed795f2.
• [BF] The dotEnv parser needs to treat zero and one as ints and not bools. If they need an interpretation as bool values, the phpDotEnv parser will take care of that 9b92b3c.
  • Recommended Action: if you saved your configuration via the new UI settings page, check for anything that should be 0 or 1 which will have been incorrectly replaced with false or true respectively, and manually edit your .env to change these back.
• [BF] Incorrect config keys for PeeringDB OAuth settings within the new settings UI 317b9c1. No action required, as this would not affect existing values in .env files.
• [BF] Inverted checkboxes in the new settings UI did not accept changes e5b0efd. No action required, as this would simply not have allowed a change and mostly affected enabling / disabling frontend components.
• [BF] A logic error in the left-hand side menu hide the IRRDB Configuration menu item 9c887fc.
• [IM] Revert changes to Bird2 route collector config, as it contained some syntax that is incompatible with older versions of Bird2 10a30b1. This also introduces a new, second Bird2 template for use with more modern versions of Bird2, designed explicitly for route collectors.
  • The new template is api/v4/router/collector/bird2-2025/standard and it is included in new unit testing.
  • Recommended Action: if you upgraded to v7.0.0, and used the route collector templates without issue, you are most likely running a version of Bird2 >= 2.14. In this case, you can safely change the template for the route collectors to the new template above.
  • Route server and AS112 template improvements will follow in later versions of IXP Manager in this way.
• [BF] Fix to the physical interface diagnostic test suite which accessed an incorrectly named database row for the port speed 92b9c6a.
• Third-party packages have been updated.

Other Improvements and Fixes

• [HK] File housekeeping - some old files were removed, and others were rearranged 7d0610f.
• [HK] The master branch was renamed to main, and various links were updated 3ebe888.
• [UI|BF] The looking glass generated a JavaScript error when the BGP summary table was empty 196807e.

Upgrade Instructions

We have yet to document specific upgrade instructions within the v7.x.y release tree. In the meantime, the instructions for upgrading within the v6 release tree can be used, replacing v6.x.y in step 3 with v7.0.1. As v7.0.1 release does not include any database migrations, steps 6 and 11 can be safely skipped.