Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wanghe-fit2cloud merged 2 commits into from
May 29, 2025
Merged

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

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4535d5f
chore(deps): update nocobase/nocobase docker tag to v1.6.36
renovate[bot] May 29, 2025
bd460df
Update app version [skip ci]
May 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/nocobase/1.6.34/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
services:
nocobase:
image: nocobase/nocobase:1.6.34
image: nocobase/nocobase:1.6.36
container_name: ${CONTAINER_NAME}
restart: always
networks:
Copy link
Member

@wanghe-fit2cloud wanghe-fit2cloud May 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Expand Down
Loading