[Bug] Incorrect version formatting in pyproject.toml when using inline update with uv

Hi here,

I often use uv in my projects, so I built my own VS Code extension based on PR !283 (closed).
It works great for showing inline package versions!

However, I noticed an issue with the inline update button when editing pyproject.toml: it generates malformed dependency strings. Here’s what happens step by step:

1. Initial state

   dependencies = ["django"]

2. After first click → adds a wildcard without a proper operator

   dependencies = ["django*"]

3. Now click again → inserts the version number but omits the == operator

   dependencies = ["django6.0.0"]  # ❌ invalid syntax

4. Expected behavior → should include a valid version specifier, e.g.

   dependencies = ["django==6.0.0"]  # ✅ or possibly ">=6.0.0"

This currently breaks pyproject.toml parsing with tools like uv or pip.

To address this, I’ve added a small fix on top of PR !283 (closed). The patched version is available here:
🔗 Release v1.22.4-pypi-fix
(branch: feat-pypi-fix-01, just one commit ahead of PR !283 (closed))

I’ll also upload a video showcasing the improvement in my patched version compared to the current master branch — made possible thanks to @amerino.informatica ’s contribution.

---

❓ Question:
Since this fix builds directly on PR !283 (closed), I’d like to ask:

Should I open a new merge request with this patch, or would it be better to coordinate with the author of PR !283 (closed) to include the fix there?

Thanks for maintaining this useful extension—I’m happy to help refine or test further!