build: update mathematics to 4.3 and physics to 11.1

[phc1990]

Summary by CodeRabbit

• New Features
  • Updated dependencies to newer versions, potentially introducing enhancements and new features.
• Chores
  • Adjusted version specifications for open-space-toolkit-mathematics and open-space-toolkit-physics.
  • Updated Dockerfile to reflect the new major version of the Open Space Toolkit Physics library.

[coderabbitai]

Walkthrough

The changes involve updating the version specifications for two dependencies in the requirements.txt file located in the bindings/python directory. The version of open-space-toolkit-mathematics has been increased from ~4.2 to ~4.3, and the version for open-space-toolkit-physics has been updated from ~10.1 to ~11.1. Additionally, the CMakeLists.txt file and the Dockerfile have been modified to reflect these version updates for the Open Space Toolkit Physics package.

Changes

File	Change Summary
bindings/python/requirements.txt	Updated open-space-toolkit-mathematics from ~4.2 to ~4.3; updated open-space-toolkit-physics from ~10.1 to ~11.1
CMakeLists.txt	Updated FIND_PACKAGE ("OpenSpaceToolkitPhysics" "10" REQUIRED) to FIND_PACKAGE ("OpenSpaceToolkitPhysics" "11" REQUIRED)
docker/development/Dockerfile	Updated ARG OSTK_PHYSICS_MAJOR from "10" to "11"; maintained structure for dependency installation and user management

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant RequirementsFile
    participant CMakeLists
    participant Dockerfile
    participant DependencyManager

    User->>RequirementsFile: Update versions
    User->>CMakeLists: Update package version
    User->>Dockerfile: Update major version
    RequirementsFile->>DependencyManager: New versions specified
    CMakeLists->>DependencyManager: New package version required
    Dockerfile->>DependencyManager: Install updated dependencies
    DependencyManager->>User: Install updated dependencies

Loading

🐇 "In the garden of code, we hop with glee,
Versions updated, oh what a spree!
Mathematics and physics, now fresh and bright,
Let’s dance with the changes, all day and night!" 🌼

Possibly related PRs

• chore: update to Physics 10.0.0 #445: The changes in this PR involve updating the version of the OpenSpaceToolkitPhysics dependency in both CMakeLists.txt and bindings/python/requirements.txt, which directly relates to the version updates made in the main PR for the same dependency.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8440551 and ee7ee1a.

📒 Files selected for processing (2)

• CMakeLists.txt (1 hunks)
• docker/development/Dockerfile (1 hunks)

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

• CMakeLists.txt

🔇 Additional comments (2)

docker/development/Dockerfile (2)

151-151: ⚠️ Potential issue

Update mathematics major version to match requirements.txt

While updating physics to version 11, the mathematics version update (4.2 -> 4.3) mentioned in requirements.txt is not reflected in the Dockerfile's OSTK_MATHEMATICS_MAJOR argument.

Apply this diff to maintain consistency:

-ARG OSTK_PHYSICS_MAJOR="11"
+ARG OSTK_MATHEMATICS_MAJOR="4"  # Should be updated if 4.3 requires a different major version
+ARG OSTK_PHYSICS_MAJOR="11"

Likely invalid or redundant comment.

---

151-151: Verify compatibility between component versions

The major version bump for physics (10 -> 11) might introduce breaking changes. Please ensure:

1. Compatibility between physics 11.1 and mathematics 4.3
2. Review of the changelog for any breaking changes
3. Impact on downstream dependencies

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.12%. Comparing base (229ab1c) to head (ee7ee1a).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #465   +/-   ##
=======================================
  Coverage   91.12%   91.12%           
=======================================
  Files          85       85           
  Lines        8639     8639           
=======================================
  Hits         7872     7872           
  Misses        767      767           

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