ci(tests) Verify runtime deps

[tony]

Changes

• Add runtime dependency check in CI using uv run --no-dev
• Run check before installing dev dependencies
• Print package version and basic functionality test results
• Document improvement in CHANGES

See also

• ci(tests) Verify runtime deps libvcs#486

Summary by Sourcery

Adds a CI job to verify runtime dependencies before installing dev dependencies, ensuring the package functions correctly with its declared runtime dependencies.

CI:

• Adds a CI job to verify runtime dependencies using uv run --no-dev before installing dev dependencies.

Tests:

• Adds a runtime dependency check that prints the package version and runs basic functionality tests.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request adds a runtime dependency check to the CI workflow using uv run --no-dev. This check is performed before installing dev dependencies to ensure that the project's runtime dependencies are correctly specified and installed. The pull request also prints the package version and runs a basic functionality test to verify the installation.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Added a job to test runtime dependencies in the CI workflow.	Uses uv run --no-dev to execute a Python script that imports key modules and prints version information. The check is run before installing dev dependencies. Includes a basic functionality test by importing and using key modules.	.github/workflows/tests.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @tony - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider adding a step to verify the package installs without errors using pip install . or uv pip install ..

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[tony]

Automated review finding. Recorded here so it is not lost. Nothing has been pushed to this branch and no fix is applied — this is a note, not a change request.

CI references __libvcs_version__ without importing it

.github/workflows/tests.yml uses __libvcs_version__ in the runtime-dependency verification step, but never imports it.

Failure scenario: the step raises NameError on every run and the job is permanently red — it never verifies the runtime dependency it exists to check.

Suggested fix:

+from libvcs import __version__ as __libvcs_version__

Worth noting for anyone triaging the same-family PRs: this one is specific to vcspull. The equivalent steps in libvcs, gp-libs, django-docutils, django-slugify-processor and g correctly reference only their own package's __version__ and are unaffected.