Sync with big-bear-casaos

[dragonfire1119]

Ran the sync script to update the repository with the latest changes from big-bear-casaos.

Summary by CodeRabbit

• New Features
  • Upgraded versions for several applications, including Mealie (from 1.11.0 to 1.12.0), Ghost (from 5.89.3-alpine to 5.90.0-alpine), and Nextcloud (from 29.0.4-apache to 29.0.5-apache), indicating potential new features, bug fixes, and performance improvements.
• Bug Fixes
  • Incremented versions may include various bug fixes related to the applications mentioned above.
• Chores
  • Updated Docker Compose configurations to reflect the new image versions for respective applications.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes involve updating the version numbers across multiple application configuration files and their corresponding Docker Compose files. Each application, including Appsmith, Ghost, Ghostfolio, Mealie, n8n, and Nextcloud, reflects an incremented version indicating potential enhancements, bug fixes, or performance improvements. The overall configurations remain structurally unchanged, focusing solely on version updates.

Changes

Files	Change Summary
servapps/appsmith/config.json, servapps/appsmith/docker-compose.yml	Version updated from 1.31.1 to 1.36.1 in both files.
servapps/ghost/config.json, servapps/ghost/docker-compose.yml	Version updated from 5.89.3-alpine to 5.90.0-alpine in both files.
servapps/ghostfolio/config.json, servapps/ghostfolio/docker-compose.yml	Version updated from 2.104.1 to 2.105.0 in both files.
servapps/mealie/config.json, servapps/mealie/docker-compose.yml	Version updated from 1.11.0 to 1.12.0 in both files.
servapps/n8n/config.json, servapps/n8n/docker-compose.yml	Version updated from 1.55.3 to 1.56.1 in both files.
servapps/nextcloud/config.json, servapps/nextcloud/docker-compose.yml	Version updated from 29.0.4-apache to 29.0.5-apache in both files.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant App
    participant Docker

    User->>App: Request Application
    App->>Docker: Pull Latest Image
    Docker-->>App: Latest Image Retrieved
    App-->>User: Application Running with New Version

Loading

Poem

In the garden of code, we hop with delight,
Versions are blooming, all shiny and bright.
From one to the next, we dance in a line,
With features and fixes, our future is fine!
So here’s to the changes, a cheer and a clap,
Happy coding, dear friends, let’s take a long nap! 🐇✨

---

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