fix: manifest and automations

[JarbasAl]

Summary by CodeRabbit

Release Notes

• New Features

  • Introduced a new workflow for automated unit tests, enhancing testing coverage and efficiency.

• Bug Fixes

  • Removed outdated Python version from build tests to streamline compatibility.
  • Eliminated the package audit step to reduce workflow complexity.

• Chores

  • Updated packaging configuration to include necessary locale and text files.
  • Restructured requirements management in the setup process for better dependency handling.

• Documentation

  • Enhanced clarity in test cases through updated import statements and structure adjustments.

• Removals

  • Deleted the install tests workflow to simplify the testing framework.
  • Removed specific unit test for validating skill installation to streamline testing efforts.
  • Removed a test method that reduced coverage of skill creation tests.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request involve modifications to GitHub Actions workflows, including the removal of the install_tests workflow and the introduction of a new unit_tests workflow. The build_tests.yml has been updated to focus on specific Python versions, while the MANIFEST.in file now includes localization and text files. The setup.py file has been restructured to dynamically load requirements. Additionally, several test files have been deleted or modified, reflecting changes in the testing framework and structure.

Changes

File	Change Summary
.github/workflows/build_tests.yml	Updated Python version matrix by removing 3.7; deleted steps related to pypa/gh-action-pip-audit.
.github/workflows/install_tests.yml	Deleted the entire workflow file that defined install tests for various components.
.github/workflows/unit_tests.yml	Added new workflow for unit tests, running on Python 3.9 and 3.10 with several defined steps for testing.
MANIFEST.in	Updated to include all files in the locale directory and all text files in the root directory.
setup.py	Rearranged imports, changed resource_base_dirs to a single string, and added get_requirements function.
test/osm_tests.py	Deleted the file containing unit tests for skill installation.
test/test_skill_loading.py	Updated imports, changed directory structure in setUpClass, and removed test_from_func method.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub Actions
    participant Test Environment

    User->>GitHub Actions: Push code or create pull request
    GitHub Actions->>Test Environment: Trigger unit tests
    Test Environment->>Test Environment: Setup Python 3.9/3.10
    Test Environment->>Test Environment: Install dependencies
    Test Environment->>Test Environment: Run unit tests
    Test Environment->>GitHub Actions: Return test results
    GitHub Actions->>User: Notify test results

Loading

🐰 "In the garden, changes bloom,
Workflows dance, dispelling gloom.
Python versions now refined,
New tests added, old ones resigned.
With each commit, we hop and cheer,
For a brighter path, the future's near!" 🐇

Warning

Rate limit exceeded

@github-actions[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 9 minutes and 21 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between cf826b6 and 87f5f18.

---

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