BREAKING CHANGE: Cut new release

[xmnlab]

Description

Related Issue

Checklist

• [ ] I've read the CODE_OF_CONDUCT.md document.
• [ ] I've read the CONTRIBUTING.md guide.
• [ ] I've used pre-commit hook locally.
• [ ] I've written tests for all new methods and classes that I created.
• [ ] I've written the docstring in Google format for all the methods and classes that I used.
• [ ] Semantic-release prefix title used:
  • Use the prefix chore(docs): for Examples / docs / tutorials / dependencies update
  • Use the prefix fix: for a bug fix (non-breaking change which fixes an issue).
  • Use the prefix chore(improvement): for an improvement (non-breaking change which improves an existing feature).
  • Use the prefix feat: for a new feature (non-breaking change which adds functionality).
  • Use the prefix breaking change: for a breaking change (fix or feature that would cause existing functionality to change).
  • Use the prefix chore(security): for a security fix.

Note: The title prefix can be also expanded with more information inside the parenthesis. Some examples for a full title (prefix + message):

• fix(login): Fix the login page.
• feat(forecast): Add a weather forecast page.
• chore(security-login): Add a weather forecast page.

[xmnlab]

@luabida it seems that the semantic release is case sensitive. it seems that we can add options for more cases, for example: fix = ["fix", "Fix", "Fixes"]. etc but I think that for now, it is better to use the default

[github-actions[bot]]

:tada: This PR is included in version 1.2.1 :tada:

The release is available on:

• 1.2.1
• GitHub release

Your semantic-release bot :package::rocket: