Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bugfix] Update motioneye to 0.43.1b2. #488

Merged
merged 1 commit into from
Jun 22, 2024

Conversation

RubenNL
Copy link
Contributor

@RubenNL RubenNL commented Jun 12, 2024

Proposed Changes

Updated Motioneye to 0.43.1b2, fixing some small issues, including the one linked below.

Related Issues

#476

I've tested the docker build doesn't cause any errors, but I can't figure out how to test this on my hassio instance, so I haven't tested it at runtime.

Changelog in the motioneye repo: https:/motioneye-project/motioneye/releases/tag/0.43.1b2

Copy link

coderabbitai bot commented Jun 12, 2024

Walkthrough

The motioneye Dockerfile has been updated to use version 0.43.1b2 instead of 0.43.1b1. This change ensures that the Docker image will build and run using the latest beta version of motioneye, likely including bug fixes or new features introduced in this newer version.

Changes

Files Change Summary
motioneye/Dockerfile Updated MOTIONEYE_VERSION from 0.43.1b1 to 0.43.1b2

Poem

In the Dockerfile, a change so slight,
A version bump to set things right,
From b1 to b2, we now ascend,
To keep our motioneye up to trend.
With this new update, we cheer and hop,
For better streams that never stop! 🐇✨


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
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 5b11e15 and edf237f.

Files selected for processing (1)
  • motioneye/Dockerfile (1 hunks)
Files skipped from review due to trivial changes (1)
  • motioneye/Dockerfile

@RubenNL RubenNL changed the title Update motioneye to 0.43.1b2. [bugfix] Update motioneye to 0.43.1b2. Jun 12, 2024
@frenck frenck added the dependencies Upgrade or downgrade of project dependencies. label Jun 21, 2024
Copy link
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @RubenNL 👍

../Frenck

@frenck frenck merged commit 9d95846 into hassio-addons:main Jun 22, 2024
13 of 14 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jun 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Upgrade or downgrade of project dependencies.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants