PB-363 Start new development cycle

[atymoshchuk]

References

PB-363

Summary

Start new development cycle: increase version , update changelog, announce upcoming features.

Are there any open tasks/blockers for the ticket?

No

---

Reviewer checklist

Reviewer agreement:

• Reviewers assign themselves at the start of the review.
• Reviewers do not commit or merge the merge request.
• Reviewers have to check and mark items in the checklist.

Merge request checklist

• Conforms to the merge request title naming XP-XXX <a description in imperative form>.
• Each commit conforms to the naming convention XP-XXX <a description in imperative form>.
• Linked the ticket in the merge request title or the references section.
• Added an informative merge request summary.

Code checklist

• Conforms to the branch naming XP-XXX-<a_small_stub>.
• Passed scope checks.
• Added or updated tests if needed.
• Added or updated code documentation if needed.
• Conforms to Google docstring style.
• Conforms to XAIN structlog style.