[WIP] Fix installation error when using uv with st3215 (#1)

[Jamie-BitFlight]

• Fix invalid version - change from 'IN_PROGRESS' to '0.0.1'
• Add .gitignore and remove build artifacts

[Mickael-Roger]

Thanks for this PR.

I'm not sure to understand why you change IN_PROGRESS for 0.0.1. IN_PROGRESS is used by the github action job to change the version on the fly.

Is there any reason ?

[Jamie-BitFlight]

Oh, try and install it using the git ref. It currently fails.

And after being built the artifacts aren't ignored.

If it's set as a version like 0.0.1 or 0.0.0 it keeps the syntax of the schema valid and the parsers don't cry when using it.

[Jamie-BitFlight]

I didn't see the GitHub action job. I should have modified that in tandem with this to version it without needing the workaround you have in place.

[Jamie-BitFlight]

Have a look at how I do automated versioning and publishing on this python project https://github.com/bitflight-devops/mcp-json-yaml-toml

That creates releases automatically on merge to main based on the conventional commit messages.

I use hatch for bundles with hatch-vcs to make the version it publishes match the git tag.

And I use a 'version.py' file that seamlessly identifies its version when in local editable install mode or bundled and published packages.

All this means that there's no extra files edited to set a version like you are trying to do here. But you always have a real version in place based on the git commit. Instead of a static value that gets replaced as you bundle and publish.

[Mickael-Roger]

I will update the job according to