Use latest FFmpeg version available

[rob93c]

Summary by CodeRabbit

• Chores
  • Updated the workflow for unit tests to use a different action for FFmpeg setup and switched to the latest version.
  • Removed the unit test workflow configuration, Dockerfile, and Qodana configuration files.
  • Adjusted the Dockerfile to retrieve the latest FFmpeg version instead of a fixed version.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request involves modifications to the unit test workflow configuration and Dockerfile, primarily focusing on FFmpeg dependency management. The changes include updating the FFmpeg setup action, switching to the latest version of FFmpeg, and removing specific configuration files. The workflow's core structure remains consistent, with adjustments to how FFmpeg is retrieved and configured across different components.

Changes

File	Change Summary
.github/workflows/unit-test.yml	- Switched FFmpeg setup action from FedericoCarboni/setup-ffmpeg@v3 to AnimMouse/setup-ffmpeg@v1 - Changed FFmpeg version from '7.0.2' to master
Dockerfile	- Updated FFmpeg dependency from version 7.0.2 to latest tag
Bumpfile	- Removed .github/workflows/unit-test.yml - Removed Dockerfile - Removed qodana.yaml

Suggested Reviewers

• MartelliEnrico

Suggested Labels

bug, cicd

Possibly Related PRs

• Update libwebp and improve updates configuration #308: Changes in Dockerfile FFmpeg version directly related to workflow configuration updates

Poem

🐰 A rabbit's tale of code so bright,
FFmpeg dancing with all its might,
From fixed version to master's gleam,
Workflows flowing like a stream,
Updating paths with bunny delight! 🚀

---

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.

[coderabbitai]

Actionable comments posted: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7518ec3 and 6cc9723.

📒 Files selected for processing (3)

• .github/workflows/unit-test.yml (1 hunks)
• Bumpfile (0 hunks)
• Dockerfile (1 hunks)

💤 Files with no reviewable changes (1)

• Bumpfile

🔇 Additional comments (1)

.github/workflows/unit-test.yml (1)

Line range hint 13-89: Well-structured workflow configuration

The overall workflow design is robust with:

• Comprehensive matrix testing across different operating systems
• Proper separation of concerns between test and analysis jobs
• Appropriate handling of artifacts and permissions