<commit_before>=====================
Centreon Broker 3.0.6
=====================

*********
Bug fixes
*********

Do not allow write filters on inputs
====================================

The consequence of setting filters on inputs was that event loop could
occur. In this release, inputs can only one way of filters, therefore
preventing event loops.

Retention file hardening
========================

Some users reported issues with retention files. In this release the
most important classes managing retention files were refactored and unit
tested.

=====================
Centreon Broker 3.0.5
=====================

*********
Bug fixes
*********

Fix a crash by memory corruption
================================

In some cases, the current pointer to the next in-memory event to
process can be corrupted. On high-volume platforms this usually leads<commit_msg>doc: update 3.0.6 release notes.<commit_after>=====================
Centreon Broker 3.0.6
=====================

*********
Bug fixes
*********

Do not allow write filters on inputs
====================================

The consequence of setting filters on inputs was that event loop could
occur. In this release, inputs can only one way of filters, therefore
preventing event loops.

Retention file hardening
========================

Some users reported issues with retention files. In this release the
most important classes managing retention files were refactored and unit
tested.

Fix inherited BA downtimes on non-default instance
==================================================

In previous versions BA downtime inheritance only worked with the
default Centreon instance created during installation (with ID 1). In
some cases (recreated instance, Poller Display) the instance ID was not
1 and prevented BA downtime inheritance from working.

=====================
Centreon Broker 3.0.5
=====================

*********
Bug fixes
*********

Fix a crash by memory corruption
================================

In some cases, the current pointer to the next in-memory event to
process can be corrupted. On high-volume platforms this usually leads
{'fraction_non_alphanumeric': 0.24516737388024518, 'fraction_numerical': 0.008015087223008015, 'mean_word_length': 5.75796178343949, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '945893', 'n_tokens_mistral': 502, 'n_tokens_neox': 447, 'n_words': 245}