⬆️ 🛠️(deps): update dependency pytest-cov to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pytest-cov (changelog)	^5.0.0 -> ^6.0.0

---

Release Notes

pytest-dev/pytest-cov (pytest-cov)

v6.0.0

Compare Source

• Updated various documentation inaccuracies, especially on subprocess handling.
• Changed fail under checks to use the precision set in the coverage configuration.
  Now it will perform the check just like coverage report would.
• Added a --cov-precision cli option that can override the value set in your coverage configuration.
• Dropped support for now EOL Python 3.8.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

Summary by Sourcery

Build:

• Update pytest-cov dependency from version 5.0.0 to 6.0.0 in pyproject.toml.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the pytest-cov dependency from version 5.0.0 to 6.0.0 in the project's test dependencies. The update includes changes to fail-under precision handling and drops support for Python 3.8.

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

File-Level Changes

Change	Details	Files
Update pytest-cov dependency version	Bump pytest-cov version from ^5.0.0 to ^6.0.0 Remove support for Python 3.8 Update fail-under checks to use coverage configuration precision Add new --cov-precision CLI option	pyproject.toml

---

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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.

[llamapreview]

Auto Pull Request Review from LlamaPReview

1. Overview

1.1 PR Summary

• Business Value and Requirements Alignment: The PR updates the pytest-cov dependency to version 6.0.0, ensuring the project leverages the latest features and improvements, including better precision handling and documentation updates. This aligns with maintaining high-quality testing standards.
• Key Components Modified: pyproject.toml
• Impact Assessment: Potential impact on test coverage reporting and configuration, especially for environments using Python 3.8, which is now unsupported.
• System Dependencies and Integration Impacts: Dropping support for Python 3.8 could affect systems still using this version.

1.2 Architecture Changes

• System Design Modifications: None.
• Component Interactions: None.
• Integration Points: None.

2. Detailed Technical Analysis

2.1 Code Logic Deep-Dive

Core Logic Changes

• File Path: pyproject.toml - [tool.poetry.group.test.dependencies]
  • Submitted PR Code:

    [tool.poetry.group.test.dependencies]
    pytest = "^7.0"
    -pytest-cov = "^5.0.0"
    +pytest-cov = "^6.0.0"
    pytest-asyncio = "^0.23.0"
    pytest-mock = "^3.11.1"
    pytest-loguru = "^0.4.0"
    eth_tester = "^0.9.0b2"

  • Analysis:
    • Current Logic and Potential Issues: The update introduces changes in fail-under precision handling and drops support for Python 3.8, which could impact systems still using Python 3.8.
    • Edge Cases and Error Handling: The change in precision handling for fail-under checks might affect existing test configurations relying on the older behavior.
    • Cross-Component Impact: None.
    • Business Logic Considerations: Ensures the project uses the latest features and improvements from pytest-cov.
  • LlamaPReview Suggested Improvements: None.
  • Improvement Rationale: None.

3. Critical Findings

3.1 Potential Issues

• 🔴 Critical Issues

  • Issue Description: Dropped support for Python 3.8.
  • Impact:
    • Technical Implications: Systems still using Python 3.8 will not be able to use the updated pytest-cov dependency.
    • Business Consequences: Potential disruption for teams or environments still on Python 3.8.
    • User Experience Effects: Developers need to upgrade to a supported Python version.
  • Recommendation:
    • Specific Code Changes: Ensure all environments are upgraded to Python 3.9 or later.
    • Configuration Updates: Update deployment and development environments to use a supported Python version.
    • Testing Requirements: Verify that all tests pass with the new Python version.

• 🟡 Warnings

  • Warning Description: Update test configurations to use the new precision handling for fail-under checks.
  • Potential Risks:
    • Performance Implications: None.
    • Maintenance Overhead: Minor updates to test configurations.
    • Future Scalability: Ensures future test configurations are aligned with the latest pytest-cov features.
  • Suggested Improvements:
    • Implementation Approach: Review and update test configurations to use the new precision handling.
    • Migration Strategy: Gradually update test configurations and monitor for any issues.
    • Testing Considerations: Run comprehensive tests to ensure the new precision handling does not introduce regressions.

3.2 Code Quality Concerns

• Maintainability Aspects: The change is straightforward and easy to maintain.
• Readability Issues: None.
• Performance Bottlenecks: None.

4. Security Assessment

• Authentication/Authorization Impacts: None.
• Data Handling Concerns: None.
• Input Validation: None.
• Security Best Practices: None.
• Potential Security Risks: None.
• Mitigation Strategies: None.
• Security Testing Requirements: None.

5. Testing Strategy

5.1 Test Coverage

• Unit Test Analysis: Ensure all tests pass with the new pytest-cov version.
• Integration Test Requirements: Verify that the new precision handling for fail-under checks does not introduce regressions.
• Edge Cases Coverage: Test environments using Python 3.8 to ensure they are upgraded to a supported version.

5.2 Test Recommendations

Suggested Test Cases

# Example test case to verify precision handling
def test_coverage_precision():
    # Assuming a function that uses coverage reporting
    result = coverage_report()
    assert result.precision == expected_precision

• Coverage Improvements: Focus on test configurations that rely on fail-under checks.
• Performance Testing Needs: None.

6. Documentation & Maintenance

• Documentation Updates Needed: Add notes on the dropped support for Python 3.8 and the new precision handling for fail-under checks.
• Long-Term Maintenance Considerations: Ensure all developers are aware of the changes and how to use the new features.
• Technical Debt and Monitoring Requirements: None.

7. Deployment & Operations

• Deployment Impact and Strategy: Ensure all environments are upgraded to a supported Python version before deploying the updated dependency.
• Key Operational Considerations: Monitor test results to ensure the new precision handling does not introduce issues.

8. Summary & Recommendations

8.1 Key Action Items

1. Critical Changes (P0):

   • Ensure all environments are upgraded to Python 3.9 or later.

2. Important Improvements (P1):

   • Update test configurations to use the new precision handling for fail-under checks.

3. Suggested Enhancements (P2):

   • Update internal documentation to reflect the changes in pytest-cov version 6.0.0.

8.2 Future Considerations

• Technical Evolution Path: Continue to monitor and update dependencies to leverage the latest features and improvements.
• Business Capability Evolution: Ensure the project maintains high-quality testing standards.
• System Integration Impacts: Be mindful of future Python version deprecations and plan upgrades accordingly.

---

💡 LlamaPReview Community
Have feedback on this AI Code review tool? Join our GitHub Discussions to share your thoughts and help shape the future of LlamaPReview.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.04%. Comparing base (4c7f459) to head (c035897).
Report is 1 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #754   +/-   ##
=======================================
  Coverage   81.04%   81.04%           
=======================================
  Files          12       12           
  Lines         633      633           
=======================================
  Hits          513      513           
  Misses        120      120           

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