Suggestion: Please tag your git repository to match the release history on PyPI

[ftnext]

crawl4ai version

0.4.247

Expected Behavior

We can check the git tag corresponding to the PyPI release history.

Current Behavior

We can only check a very small number of git tags.
https://github.com/unclecode/crawl4ai/tags

I am struggling to grasp what has changed in each version.
This library has a great idea and I think it can deliver more value to users by following the common manners of OSS.

Is this reproducible?

Yes

Inputs Causing the Bug

Steps to Reproduce

# FYI: Sharing my OSS release workflow
I use GitHub Codespaces.

1. test passed
2. Bump up library version commit
3. git tag
4. push the tag to origin
5. (Draft GitHub release and publish)
6. `uvx build`
7. `uvx twine upload dist/*`

Code snippets

OS

Windows, macOS, Linux

Python version

3.13

Browser

No response

Browser version

No response

Error logs & Screenshots (if applicable)

No response