Prepare release v0.0.10

[vinikatyal]

Description

• What is this PR about?

Screenshots/Results

• Add a screenshot of the changes or code responses

Reference Links

• Links to JIRA issue, links, Slack discussions, etc.

Checklist

This PR includes the following (tick all that apply):

• Tests added/updated for new/changed functionality
• Bug Fix (explain the bug in the description)
• Refactoring or optimizations (no functional changes)
• Documentation updated (README, docstrings, etc.)
• Build or deployment related changes
• Dependency updates (requirements.txt/pyproject.toml)
• Setup change (update README/setup instructions if required)
• Code style checks passed (PEP8, flake8, black, etc.)
• Type hints added/updated (if applicable)
• Pre-commit hooks run (if configured)

[vinikatyal]

Hi @kaushik-himself is this release number fine?

[kaushik-himself]

@vinikatyal you need to follow the release process defined in our docs: https://github.com/fiddlecube/compliant-llm/blob/main/docs/releaseguide.md#release-process

• first, create a pre-release and test it
• patch version needs to be updated: first 0.0.10-alpha1
• this will release an alpha version to test pypi:
• follow the steps to push the commit and also the tag to origin to release the alpha version to test pypi
• if the tests succeed, move ahead with the release
• else, fix the issues and create a new alpha version, say 0.0.10-alpha2

Release:

• Same steps as pre-release. but version doesn't have the -alphaN at the end.
• this will push a new version to pypi
• install and test the new version by running pip install compliant-llm==0.0.10.

Note: as soon as you push the git tag to origin, the version is released.

We can block time on the calendar to do this over a meeting, if that will make it easier.