IRRD 4.4.0 beta 1

First beta of 4.4.0: https://irrd.readthedocs.io/en/latest/releases/4.4.0/

IRRD 4.3.1

https://irrd.readthedocs.io/en/stable/releases/4.3.1/

IRRd 4.3.1 was released on August 17, 2023, and fixes several issues:

• Set members included through mbrs-by-ref / member-of did not have the correct source filter applied. This meant that members could be included in a set, even through the aut-num, route or route6 object were from a different IRR source.
• IRRD could incorrectly try to use synchronised serials even when route object preference was enabled. This could cause issues for mirrored sources when this setting was enabled, but RPKI and the scope filter were not. If this affected your setup, mirroring would break, but IRRD would log errors repeatedly.
• The PyYAML dependency was updated to 6.0.1 to resolve installation issues in certain environments.

IRRD 4.2.9

https://irrd.readthedocs.io/en/v4.2.9/releases/4.2.9/

IRRd 4.2.9 was released on August 17, 2023, and fixes several issues:

• Set members included through mbrs-by-ref / member-of did not have the correct source filter applied. This meant that members could be included in a set, even through the aut-num, route or route6 object were from a different IRR source.
• The PyYAML dependency was updated to 6.0.1 to resolve installation issues in certain environments.

IRRD 4.3.0 post 1

https://irrd.readthedocs.io/en/stable/releases/4.3.0/

4.3.0 was initially released on June 6th, 2023, but was yanked due to a packaging error on June 9th, leading to the release of IRRd 4.3.0.post1. The main visible issue from the error was that the documentation of 4.4 was published as 4.3.0. If you had previously installed 4.3.0 through PyPI/pip, you can keep running on that version, or update to 4.3.0.post1 without needing restarts or migrations, as the 4.3.0 and 4.3.0post1 PyPI packages have identical code.

IRRd 4.3.0 release candidate 1

Release candidate 1 for 4.3.0. Will be released as 4.3.0 unless any issues are reported.

https://irrd.readthedocs.io/en/latest/releases/4.3.0/

Changes from 4.3.0b2:

• [4.3.x] Fix #774 - Fix NRTM generator performance on PyPy (backport #777) by @mergify in #779
• [4.3.x] Fix #783 - Gracefully handle OSError for status page remote query (backport #788) by @mergify in #789
• [4.3.x] Ensure tmp files are deleted on failed import (backport #765) by @mergify in #791

IRRd 4.2.8

IRRd 4.2.8 was released on April 19th, 2023, and fixes an issue where NRTM queries could hang indefinitely on PyPy deployments (#774). This did not affect CPython deployments.

IRRd 4.3.0 beta 2

Second beta release of 4.3.0. Release notes: https://irrd.readthedocs.io/en/latest/releases/4.3.0/

Fixes from 4.3.0b1:

• Fixed a SQL deadlock issue and significant performance issue when performing initial imports (#771)

IRRd 4.3.0 beta 1

First beta release of 4.3.0. Release notes: https://irrd.readthedocs.io/en/latest/releases/4.3.0/

IRRd 4.2.7

IRRd 4.2.7 was released on February 15th, 2023, and has three changes:

• IRRd now has a new setting sources.{name}.nrtm_query_serial_range_limit
  to limit the maximum serial range a client may request in a single NRTM
  query. This is configured per source, and evaluated in addition to
  other access limits. By default, there is no limit.
  See the :doc:configuration documentation </admins/configuration>
  for details.
• Each IRRd process will now log a traceback of all threads when receiving
  a SIGUSR1 signal. The tracebacks are written to the normal logs, and
  can help IRRd developers understand more complex issues, particularly
  in hanging IRRd workers.
• Password hashes were visible in some email notifications (#722). The scope
  was limited. A notification could only be triggered by already
  knowing a valid password.

IRRd 4.2.6

IRRd 4.2.6 was released on November 18th, 2022, and fixes two issues:

• IRRD whois connections could stay stuck in FIN_WAIT2 state (#607), which may also have led to workers to stop responding (#693) to queries in some cases. This was addressed by adding a missing timeout to read calls on these connections.
• A few small changes were made to improve unclear log messages.