⬆️ Update Motion-Project/motion to v4.7.0

[renovate]

This PR contains the following updates:

Package	Update	Change
Motion-Project/motion	minor	4.6.0 -> 4.7.0

---

Release Notes

Motion-Project/motion (Motion-Project/motion)

v4.7.0: Release 4.7.0

Compare Source

Release Notes: 4.7.0

The documentation for the 4.7.0 release can be found in the Motion 4.7.0 Guide

The following summarizes the changes implemented in version 4.7.0

• Fixes

  • Fix zombie reaping for Motion processes.
  • Fix network camera processing for non compliant codec.
  • Fix v4l2M2M encoding.
  • Fix fps conversion specifier.

• Enhancements/Revisions

  • Allow for large date time and event numbers.
  • Remove outdated MMAL camera code.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The primary change involves updating the MOTION_VERSION argument in the Dockerfile for the MotionEye project from 4.6.0 to 4.7.0. This upgrade signifies the adoption of a newer version of the Motion software, maintaining the overall structure of the Dockerfile while reflecting the version increment.

Changes

Files	Change Summary
motioneye/Dockerfile	Updated MOTION_VERSION from 4.6.0 to 4.7.0

Poem

In a world of code, we hop and play,
With MotionEye's version now bright as day!
From 4.6 to 4.7, we dance with glee,
Bugs all chased away, so happy are we! 🐇✨
Let’s build and create, our joy to unfurl,
Hooray for the changes that make our tails twirl!

---

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

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c17a920 and 9e045e2.

Files selected for processing (1)

• motioneye/Dockerfile (1 hunks)

Additional comments not posted (1)

motioneye/Dockerfile (1)

9-9: Version update approved.

The MOTION_VERSION has been successfully updated from 4.6.0 to 4.7.0. Ensure that the new version is tested for compatibility with the rest of the Dockerfile.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9e045e2 and af1d1b7.

Files selected for processing (1)

• motioneye/Dockerfile (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• motioneye/Dockerfile