Relocate requirements files so dependabot can find them

[bdraco]

The tests requirements were being ignored by dependabot

https://github.com/dependabot/dependabot-core/blob/main/python/lib/dependabot/python/file_fetcher.rb

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (04119d9) to head (a33ffb6).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1046   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           17        17           
  Lines         2681      2681           
=========================================
  Hits          2681      2681           

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

[codspeed-hq]

CodSpeed Performance Report

Merging #1046 will not alter performance

_{Comparing requirements_files_dependabot (a33ffb6) with main (04119d9)}

Summary

✅ 2 untouched benchmarks

[coderabbitai]

Walkthrough

The changes update references to the project’s dependency definition files. The CI workflow configuration now uses requirements/base.txt and requirements/test.txt instead of the old requirements.txt and requirements_test.txt in several steps, including cache restoration and dependency installation. In addition, the MANIFEST.in file and setup.py have been modified to reference requirements/base.txt instead of requirements.txt. No modifications were made to the publicly exported interfaces.

Changes

File(s)	Change Summary
.github/workflows/ci.yml	Updated CI steps: replaced requirements.txt and requirements_test.txt with requirements/base.txt and requirements/test.txt, and modified the PIP cache key accordingly.
MANIFEST.in, setup.py	Changed dependency references: removed inclusion/opening of requirements.txt and replaced it with requirements/base.txt.

Sequence Diagram(s)

sequenceDiagram
    participant CI as CI Workflow Runner
    participant Cache as PIP Cache
    participant PIP as Package Installer

    CI->>Cache: Restore cache using updated key
    CI->>CI: Set up Python environment
    CI->>PIP: Install dependencies from requirements/base.txt & requirements/test.txt
    PIP-->>CI: Return installation result

Loading

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 04119d9 and a33ffb6.

📒 Files selected for processing (3)

• .github/workflows/ci.yml (3 hunks)
• MANIFEST.in (1 hunks)
• setup.py (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• MANIFEST.in

🧰 Additional context used

📓 Path-based instructions (1)

setup.py (1)

Pattern **: - Do not generate or add any sequence diagrams

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: py 3.13 on ubuntu-latest (use_cython)
• GitHub Check: Run benchmarks

🔇 Additional comments (3)

setup.py (1)

41-41: LGTM! Path updated correctly.

The requirements file path has been updated to match the new location, aligning with the PR objective to make requirements files discoverable by Dependabot.

.github/workflows/ci.yml (2)

75-75: LGTM! Cache key updated correctly.

The cache key has been updated to use the new requirements file paths, ensuring proper cache invalidation when requirements change.

---

84-84: LGTM! Requirements paths updated consistently.

The pip install commands have been updated consistently across all environments (with and without cython) and jobs (CI and benchmarks) to use the new requirements file paths.

Also applies to: 92-92, 148-148

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.