chore(deps): update neosmemo/memos docker tag to v0.24.4

[renovate]

This PR contains the following updates:

Package	Update	Change
neosmemo/memos	patch	0.24.3 -> 0.24.4

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

usememos/memos (neosmemo/memos)

v0.24.4

Compare Source

What's Changed

• feat: automatically add a new table row in the editor when pressing enter by @​dzervas in https://github.com/usememos/memos/pull/4706
• feat: add infinite scrolling for memos by @​liltrendi in https://github.com/usememos/memos/pull/4715
• fix: make the save button disabled after a successful update by @​dabeeduu in https://github.com/usememos/memos/pull/4721
• fix(editor): Prevent race condition and ensure correct list continuation on Enter by @​jonfk in https://github.com/usememos/memos/pull/4716
• feat(rss): Use server title and description for RSS feed, if configured by @​maximilian-krauss in https://github.com/usememos/memos/pull/4717
• fix: inherits memo visibility for default comment visibility by @​maximilian-krauss in https://github.com/usememos/memos/pull/4728
• refactor: memo editor by @​johnnyjoygh in https://github.com/usememos/memos/pull/4730

New Contributors

• @​RealOrangeOne made their first contribution in https://github.com/usememos/memos/pull/4699
• @​dzervas made their first contribution in https://github.com/usememos/memos/pull/4706
• @​liltrendi made their first contribution in https://github.com/usememos/memos/pull/4715
• @​dabeeduu made their first contribution in https://github.com/usememos/memos/pull/4721
• @​eya46 made their first contribution in https://github.com/usememos/memos/pull/4719
• @​jonfk made their first contribution in https://github.com/usememos/memos/pull/4716
• @​maximilian-krauss made their first contribution in https://github.com/usememos/memos/pull/4717

Full Changelog: usememos/memos@v0.24.3...v0.24.4

---

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: Never, 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.

[f2c-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[f2c-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[wanghe-fit2cloud]

The code snippet appears to be updating an existing Docker Compose service named memos. The only change is that the image version has been updated from 0.24.3 to 0.24.4. This is a straightforward and safe upgrade. No other potential issues or optimized suggestions are necessary at this time. If you need further changes such as adding tags, labels, or environment variables, please specify those requirements.

[wanghe-fit2cloud]

The code difference changes the Docker image for the "memos" service from version 0.24.3 to 0.24.4. This update is minor in nature, as there are no apparent problems with the change. If this is part of an ongoing development cycle or security updates, it's good practice to verify that all necessary components still function correctly after updating to avoid downtime. However, without further context about dependencies, integration tests, or production readiness checks, I cannot provide specific recommendations beyond recommending thorough testing post-update.