tests(ci) Check runtime deps import correctly

[tony]

Resolves #573

Add a step to verify the package can be imported and used without dev dependencies installed. This helps catch missing runtime dependencies before they reach users.

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

Example Output

libtmux version: 0.44.2
libtmux Server: <Server(socket_path=/tmp/tmux-1000/default)>

Why?

• Catches missing runtime dependencies early in CI
• Prevents publishing packages with incomplete requirements
• Verifies package works in clean environment
• Inspired by @ppentchev's suggestion in fix(typings) Move typing-extensions into TypeGuard #572

Verification

Summary by Sourcery

Add a check for runtime dependencies import.

Bug Fixes:

• Check runtime dependencies are imported correctly

CI:

• Add a step to the test workflow to check that runtime dependencies are imported correctly

Summary by Sourcery

Add a check to the CI workflow to verify that the package can be imported and used without development dependencies installed. This check helps catch missing runtime dependencies before they reach users by running a basic functionality test and printing the package version.

CI:

• Verify that runtime dependencies are correctly imported before installing development dependencies in the CI workflow using uv run --no-dev

Documentation:

• Document the runtime dependency check improvement in the changelog

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request adds a CI job to verify that the package can be imported and used without dev dependencies installed. This helps catch missing runtime dependencies before they reach users. The CI job uses uv run --no-dev to exclude dev dependencies and runs before installing dev dependencies. A note was also added to the changelog documenting the improvement.

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

File-Level Changes

Change	Details	Files
Added a CI job to test runtime dependencies using uv run --no-dev.	Added a new job to the test workflow. The job runs before installing dev dependencies. The job imports the package and prints the package version and server information. The job uses uv run --no-dev to exclude dev dependencies.	.github/workflows/tests.yml
Added a note to the changelog about the runtime dependency check.	Added a line to the changelog documenting the improvement.	CHANGES

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#573	Ensure CI tests run without extra dependency groups to catch missing runtime dependencies.	✅
#573	Verify that the package can be imported and used without dev dependencies installed.	✅

Possibly linked issues

• CI: Run libtmux without extra dep groups #573: The PR addresses the issue by adding a runtime dependency check in CI to catch missing dependencies.

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.80%. Comparing base (efdc59c) to head (f66abaf).
Report is 3 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #574   +/-   ##
=======================================
  Coverage   88.80%   88.80%           
=======================================
  Files          36       36           
  Lines        4075     4075           
  Branches      385      385           
=======================================
  Hits         3619     3619           
  Misses        308      308           
  Partials      148      148           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sourcery-ai]

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

Overall Comments:

• Consider using sys.executable instead of hardcoding python in the test command.
• It might be helpful to add a comment explaining why the runtime dependencies test is run before installing dev dependencies.

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.}