Merge next v33 - Githubissues

lucasmoura commented 3 months ago

Why is this needed?

Now that we have released version 32, we need to merge to main all the changed we did for release 33

Check if we are not loosing any work in this merge, specially on the enable refactor, given the main conflict on the marge happened for that work

github-actions[bot] commented 3 months ago

Jira: This PR is not related to a Jira item. (The PR title does not include a SC-#### reference)

GitHub Issues:

Launchpad Bugs: No Launchpad bugs are fixed by this PR. (No commits have LP: #### references)

Documentation: The changes in this PR do not require documentation changes.

👍 this comment to confirm that this is correct.

github-actions[bot] commented 3 months ago

🌎 This PR changes translatable messages. 🌏

Please select which scenarios apply. For further explanation, please read our policy on message changes.

[ ] New messages are being added.
- We will ask translators to take a look and add translations if they have time, but it will not block this PR.
[ ] Existing messages are being changed.
- ⚠️ Please add a comment with justification of why messages are being altered.
- If the changes are trivial (e.g. a typo fix), then translations must be preserved.
- If the changes are substantial, then we will ask translators to take a look and update translations if they have time, but it will not block this PR.
[ ] Existing messages are being deleted.
- No special action needed.