fix: correct semantic release behaviour

[butler54]

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Documentation (change which affects the documentation site)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Quality assurance (all should be covered).

• [ ] My code follows the code style of this project.
• [ ] Documentation for my change is up to date?
• [ ] My PR meets testing requirements.
• [ ] All new and existing tests passed.
• [ ] All commits are signed-off.

Summary

The objective of this is to fix the build pipeline before there is a breakage. At this stage I have NOT had the change to thoroughly test the Uploading behaviour, however, forking and updating is going to be difficult.

This transitions to OIDC based authentication for upload as opposed to pypi authentication. The instructions here: https://docs.pypi.org/trusted-publishers/adding-a-publisher/ must be setup.

This will include ensure the github actions environment is setup.

Key links:

• Sonar coverage

Before you merge

• Ensure it is a 'squash commit'
• Ensure CI is currently passing
• Is this a merge to develop from any branch except main and ghpages

[butler54]

@vikas-agarwal76 - This will need some active participation on your part and/or others associated who now own the project in pypi.

[butler54]

@AleJo2995 - your breaking change didn't work either when testing.

BREAKING CHANGE: declarations need to be part of the body not the header of the commit - see https://python-semantic-release.readthedocs.io/en/latest/commit-parsing.html