Update requirements.txt

[JarbasAl]

test that all works as expected with ovos-config 1.0.0+

Summary by CodeRabbit

• Chores
  • Upgraded the ovos-config package to version 1.0.5 for improved functionality.
  • Updated the skill-ddg package to version 0.2.2 for enhanced capabilities.

[coderabbitai]

Walkthrough

This pull request updates the version constraints for the ovos-config package in requirements/requirements.txt and the skill-ddg in requirements/skills-internet.txt. The minimum version of ovos-config is increased from 0.0.13 to 1.0.5, while the version for skill-ddg is raised from 0.1.9 to 0.2.2. The entry for ovos-skill-ip remains unchanged, but its formatting is adjusted for consistency.

Changes

File(s)	Summary
requirements/requirements.txt	Updated ovos-config version constraint from >=0.0.13,<2.0.0 to >=1.0.5,<2.0.0.
requirements/skills-internet.txt	Updated skill-ddg version from >=0.1.9,<1.0.0 to >=0.2.2,<1.0.0; formatted ovos-skill-ip.

Suggested labels

packaging

Poem

I’m just a bunny with a joyful beat,
Hopping over changes oh so neat,
Upgraded bounds in the code so bright,
Turning old carrots into new delight,
With every hop, our code takes flight! 🐇
Celebrate adjustments, small yet sweet!

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 25e9b0d and 5daf8be.

📒 Files selected for processing (1)

• requirements/skills-internet.txt (1 hunks)

---

Note

🎁 Summarized by CodeRabbit Free

Your organization has reached its limit of developer seats under the Pro Plan. For new users, CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please add seats to your subscription by visiting https://app.coderabbit.ai/login.If you believe this is a mistake and have available seats, please assign one to the pull request author through the subscription management page using the link above.

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.59%. Comparing base (23f0bab) to head (5daf8be).
Report is 214 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #666      +/-   ##
==========================================
- Coverage   75.33%   69.59%   -5.75%     
==========================================
  Files          15       15              
  Lines        3094     1674    -1420     
==========================================
- Hits         2331     1165    -1166     
+ Misses        763      509     -254     

Flag	Coverage Δ
end2end	53.70% <ø> (?)
unittests	46.05% <ø> (-29.29%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.