Thanks for your PR @MANASAB805,
Three things to consider:

1. We should actually avoid --allow-dirty flag to make sure our lock file matches the dependencies, otherwise the build might fail or is not binary identical between the releases and the repository
2. We need to run the dry run prior to the publish job, as just running the dry run directly before the publish doesn't help us avoid conflicts, as the release branch has been already merged then (so we have to run the dry run in the test workflow and only if we are on a release branch (starting with patter release/**). We can skip the dry run for all other feature branches, as this is expected to fail as of local development settings
3. Please rebase the branch to release/0.0.7 in order to allow us adding this to the new release cycle

Could you make those adaptions? If done we would be good to merge your contribution.

FYI see https://github.com/unyt-org/datex-core/blob/feat/fmt/CONTRIBUTING.md

@jonasstrehle I've made the requested changes:

• Moved the dry-run to the test workflow
• Removed the --allow-dirty flag
• Configured it to only run on release branches
• Rebased onto release/0.0.7

The PR is now ready for review. Let me know if you'd like any adjustments!