Better way to install uv

[mernst]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates CI and dev tooling: it changes the uv installation in .github/workflows/style.yml from running the remote install script via curl to using the reusable action astral-sh/setup-uv@v7. It also adds pymarkdownlnt>=0.9.33 to the development dependencies in pyproject.toml.

Pre-merge checks and finishing touches

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch setup-uv

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f2f4f08 and e693b40.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• pyproject.toml (1 hunks)

🔇 Additional comments (1)

pyproject.toml (1)

9-13: The package name pymarkdownlnt is correct and exists on PyPI as a Markdown linter (GitHub-Flavored/CommonMark-compliant). Version 0.9.33 is the latest release as of October 2025. No action needed regarding the package name.

The use of >=0.9.33 is acceptable here since it pins to the latest stable release; however, consider ~=0.9.33 or exact pinning (==0.9.33) if you prefer stricter control over dev-tool updates in CI.

---

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 and usage tips.}