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

[renovate]

This PR contains the following updates:

Package	Update	Change
nocobase/nocobase	patch	1.6.34 -> 1.6.36

---

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.

Details

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.

Details

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 changes provided involve updating the version of the NoCobase service from 1.6.34 to 1.6.36. This update suggests an upgrade to the latest stable release available at that time. However, there are no apparent issues with this change and it can generally be considered safe if compatible with your existing environment configurations.

If you have specific requirements or constraints related to security updates, deployment strategies, or resource usage, additional considerations might be necessary:

1. Security Updates: Ensure that all dependencies and vulnerabilities remain addressable after upgrading to mitigate any potential risks.

2. Deployment Strategy Adjustments: Depending on how NoCobase is deployed (e.g., through Docker Compose), Kubernetes, etc.), adjustments may be needed to handle new environments seamlessly.

3. Resource Usage Analysis: Review whether the updated version necessitates increased resources or changes in CPU/GPU allocation to ensure continued performance within acceptable limits.

Overall, the change seems straightforward and should function without major issues given typical scenarios where software versions are upgraded for stability improvements.