chore(deps): update nocobase/nocobase docker tag to v1.6.37

[renovate]

This PR contains the following updates:

Package	Update	Change
nocobase/nocobase	patch	1.6.36 -> 1.6.37

---

Warning

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

---

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 provided diff shows an minor update from version 1.6.36 to 1.6.37. Here are some observations and considerations:

@@ -1,6 +1,6 @@
 services:
   nocobase:
-    image: nocobase/nocobase:1.6.36
+    image: nocobase/nocobase:1.6.37
     container_name: ${CONTAINER_NAME}
     restart: always

This change only updates the Docker image tag for the NoCobase service from 1.6.36 to 1.6.37, which is a simple bug fix or upgrade without any significant changes needing consideration. The other fields (container_name and restart) remain unchanged.

No additional irregularities, potential issues, or optimization suggestions are apparent from this diff. This update can be safely applied if you need to take advantage of any features or fixes included in the newer version without any disruptions to your current configuration.