chore: sync uv.lock with release-please's version bump

[fzipi]

Summary

release-please's python release-type bumps pyproject.toml's version field but has no notion of uv.lock. On #141 this left uv.lock's embedded secrules-parsing version at 0.2.4 while pyproject.toml moved to 0.4.1, which fails the uv sync --locked step in the regression matrix (failing job):

error: The lockfile at `uv.lock` needs to be updated, but `--locked` was provided.

This targets #141's branch directly and just runs uv lock — one-line diff, uv sync --locked and uv run pytest both pass locally (149 passed, 11 xfailed).

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Advanced

Run ID: d144ff9e-7680-4f7e-bc54-c2d0f3d83ae8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}