Skip to content

chore(deps): update nocobase/nocobase docker tag to v1.7.2 #4072

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
Jun 5, 2025
Merged

chore(deps): update nocobase/nocobase docker tag to v1.7.2 #4072

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
11deb27
chore(deps): update nocobase/nocobase docker tag to v1.7.2
renovate[bot] Jun 5, 2025
08c8df0
Update app version [skip ci]
Jun 5, 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
0 apps/nocobase/1.7.1/data.yml → apps/nocobase/1.7.2/data.yml
View file
Open in desktop
File renamed without changes.
2 changes: 1 addition & 1 deletion apps/nocobase/1.7.1/docker-compose.yml → apps/nocobase/1.7.2/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.7.1
image: nocobase/nocobase:1.7.2
container_name: ${CONTAINER_NAME}
restart: always
networks:
Copy link
Member

@wanghe-fit2cloud wanghe-fit2cloud Jun 5, 2025

Choose a reason for hiding this comment

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

The provided code snippet shows a Docker Compose configuration file with an update to the image property of the nocobase service. There are no known irregularities or potential issues with this change, assuming that version 1.7.2 is compatible with other configurations and dependencies used in your project.

If there were optimizations needed, they would likely involve considering the following:

  1. Environment Variables: Ensure that ${CONTAINER_NAME} is consistently defined throughout you application's environment setup, so it uses the correct value without errors.

  2. Health Checks: Implementing proper health checks can be beneficial to monitor if the container starts correctly and recover from failures efficiently.

  3. Resource Limits: If necessary, set appropriate resource limits (CPU, memory) to manage performance.

  4. Volumes/Networks/Cribs/Namespace Isolation: Verify whether additional volumes, networks, cribs, or namespace isolation configurations are required based on your application's requirements.

Overall, the change from image nocobase/nocobase:1.7.1 to nocobase/nocobase:1.7.2 appears straightforward and doesn't require significant adjustments. However, keeping these best practices in mind might help ensure smoother operations in production environments.

Expand Down