Added automatic version updates with bump

[MartelliEnrico]

A new secret BUMP_TOKEN must be created to run workflows on the PRs openend by bump. See https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/triggering-a-workflow#triggering-a-workflow-from-a-workflow

Closes #270

Summary by CodeRabbit

• New Features

  • Introduced an automated workflow for updating dependencies, scheduled to run daily.
  • Added a new shell script for updating SHA256 hashes based on URL templates.

• Improvements

  • Enhanced Dockerfile for better handling of the libwebp library with versioning and checksum verification.
  • Updated unit test workflow to specify a new version of FFmpeg.

[coderabbitai[bot]]

📝 Walkthrough

📝 Walkthrough

Walkthrough

The pull request introduces a new automated workflow for updating dependencies, specifically for the libwebp library, along with a Dockerfile for building the application. A shell script named hashupdate is also added to facilitate the updating of SHA256 hashes for specified files. These changes enhance the management of dependencies and improve the reliability of the build process.

Changes

Files	Change Summary
.github/workflows/bump.yaml	New workflow for automated dependency updates, triggered daily and manually, using wader/bump/action@master for updating dependencies.
.github/workflows/unit-test.yml	Updated FFmpeg version to '7.0.2' in the Setup FFmpeg step.
Dockerfile	Updated to handle libwebp library with versioning and checksum verification. Introduced new arguments for version, URL, and SHA256 checksum, and modified download and extraction commands accordingly.
hashupdate	New shell script for updating SHA256 hashes based on a URL template, ensuring error handling and automating the hash update process.

Assessment against linked issues

Objective	Addressed	Explanation
Use bump to keep libwebp up to date (#270)	✅

🐰 In the garden where bunnies play,
New workflows bloom, brightening the day.
With hashes updated and libraries neat,
Our code hops forward, a joyful feat!
Dependencies managed, all in a row,
Thanks to the changes, watch our project grow! 🌼

---

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.