feat: epic issues to create release 0.13.2

[jotamorais]

This PR contains issues combined through epic #1757 to create release 0.13.2

[jotamorais]

@braaar Looks like I no longer have access to push to develop branch nor to create tags/releases.
While I request for such access, can you please review/test all the issues I've merged into this PR? The only one left out from that list in the epic issue, was the #1754 as it was it caused merge conflicts and after fixing the conflicts, it caused 8 tests to fail.

[braaar]

@braaar Looks like I no longer have access to push to develop branch nor to create tags/releases. While I request for such access, can you please review/test all the issues I've merged into this PR? The only one left out from that list in the epic issue, was the #1754 as it was it caused merge conflicts and after fixing the conflicts, it caused 8 tests to fail.

I must admit I'm a bit confused by this PR. Isn't it more practical to squash and merge each individual PR separately?

It's really hard to get an overview over what changes are included in this PR, let alone review and fix failing tests. In the PR description, your link seems to be wrong (it just links back to this PR).

Also, 0.13.2 is already released.Do we want to make a bugfix/docs release as 0.13.3 and then do a feature release with 0.14.0, or just go straight to 0.14 with all the changes in one release?

[NoNameProvided]

Closing this as invalid, release PR should be from develop to master.

Looks like I no longer have access to push to develop branch nor to create tags/releases.

You should have but one code-review is mandatory.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.