Include Github run numbered in release candidate version

[sogartar]

We can't make multiple different versions for the same day.

With this change the release candidates will have a version of the form
3.2.0rc20250205-0
3.2.0rc20250205-1
...
instead of just 3.2.0rc20250205.

[sogartar]

This is the same of a reverted change #458.

I have verified that the workflow passes fine.
I don't see the upload at https://iree.dev/pip-release-links.html.

[ScottTodd]

I have verified that the workflow passes fine.

Thanks! The version shows up as iree_turbine-3.2.0rc20250210.post73 though. Was that intentional?

See the documentation at https://packaging.python.org/en/latest/discussions/versioning/.

I'm also still not sure we really need this extra suffix given the extra complexity.

• If each package has its own extra suffix then manually updating the versions in a file like https://github.com/nod-ai/shark-ai/blob/main/requirements-iree-pinned.txt will be harder.
• iree-turbine has low commit volume (< 10 commits per day), so I would expect us to only very rarely be publishing multiple builds per day

I don't see the upload at https://iree.dev/pip-release-links.html.

That index is updated by an action in iree-org/iree, that runs when the IREE docs are updated or an IREE release is completed. The workflow can also be triggered manually.
https://github.com/iree-org/iree/blob/624a9fae4f8dd03becfaae69110411c84c4ed6e8/.github/workflows/publish_website.yml#L67-L82

[ScottTodd]

You can also test in your fork while still iterating. The test run in this repository pushed the iree_turbine-3.2.0rc20250210.post73-py3-none-any.whl package to https://github.com/iree-org/iree-turbine/releases/tag/dev-wheels. We can either keep that or delete it since "dev wheels" and nightly releases are best-effort and may occasionally do weird things.