Update Grocy to 4.5.0

[sciafri]

https://github.com/grocy/grocy/releases/tag/v4.5.0

Proposed Changes

(Describe the changes and rationale behind them)

Related Issues

(Github link to related issues or pull requests)

Summary by CodeRabbit

• New Features

  • Upgraded to Grocy v4.5.0, bringing the latest upstream features and UI enhancements to users.

• Bug Fixes

  • Includes multiple stability, performance, and minor usability fixes delivered with Grocy v4.5.0.

• Chores

  • Bumped the bundled Grocy version to v4.5.0 to keep the application current with upstream improvements and fixes.

[coderabbitai]

Walkthrough

Updated the GROCY_VERSION build argument in grocy/Dockerfile from v4.4.2 to v4.5.0, changing the Git branch fetched during Docker build. No other logic or steps were altered.

Changes

Cohort / File(s)	Summary of Changes
Docker build version bump grocy/Dockerfile	Updated ARG GROCY_VERSION from "v4.4.2" to "v4.5.0" to fetch the new Grocy release during build.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

Hop hop! A tag we lift—v4.5.0 in sight,
Carrot-orange progress, crisp and light.
Docker hums a newer tune,
Pulls fresh leaves this sunny noon.
I twitch my ears—version bumped just right!

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[sciafri]

@coderabbitai please add the dependencies label so CI can pass.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Add the dependencies label to the current PR
gh pr edit --add-label "dependencies"

Length of output: 88

---

🏁 Script executed:

#!/bin/bash
# Add the dependencies label to PR #496
gh pr edit 496 --add-label "dependencies"

Length of output: 112

---

@sciafri I don't have the necessary permissions to add labels to PRs. The GitHub CLI returned a permission error: "Resource not accessible by integration (addLabelsToLabelable)".

You'll need to add the "dependencies" label manually through the GitHub web interface, or if you'd like me to be able to add labels in the future, you could grant the CodeRabbit GitHub app additional permissions for this repository.

To add the label manually:

1. Go to the PR page
2. Click on the gear icon next to "Labels" in the right sidebar
3. Select "dependencies" from the list

🐰💭

---

⛔ Permission issue

There was a permission issue. Please ask the repository administrator to refresh CodeRabbit's permissions at https://github.com/apps/coderabbitai/installations/50882955.

[sciafri]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

grocy/Dockerfile (1)

9-9: Process: add the "dependencies" label to unblock CI

Per PR discussion, this change is a dependency bump. Add the dependencies label so CI can proceed.

Do you want me to open a tracking comment with exact label text and rationale?

📜 Review details

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 73ff42b and c370cce.

📒 Files selected for processing (1)

• grocy/Dockerfile (1 hunks)

🔇 Additional comments (2)

grocy/Dockerfile (2)

9-9: Version bump wired correctly; build will fetch Grocy v4.5.0

Using GROCY_VERSION in the git clone step ensures the correct tag is pulled and cached properly in Docker layers. No other build logic impacted.

---

9-9: Upstream verification complete: v4.5.0 is compatible with our Dockerfile
All checks passed—no changes required.

• Tag v4.5.0 exists upstream
• composer.json requires PHP ≥8.2 and declares no ext-* dependencies
• Dockerfile’s runtime php82-* packages cover all needed extensions
• package.json is present at v4.5.0, so the yarn build step remains valid

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.