Skip to content

chore(deps): update nocobase/nocobase docker tag to v1.6.17 #3649

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
Apr 9, 2025
Merged

chore(deps): update nocobase/nocobase docker tag to v1.6.17 #3649

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
9edcd85
chore(deps): update nocobase/nocobase docker tag to v1.6.17
renovate[bot] Apr 9, 2025
12dec47
Update app version [skip ci]
Apr 9, 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.6.16/data.yml → apps/nocobase/1.6.17/data.yml
View file
Open in desktop
File renamed without changes.
2 changes: 1 addition & 1 deletion apps/nocobase/1.6.16/docker-compose.yml → apps/nocobase/1.6.17/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.16
image: nocobase/nocobase:1.6.17
container_name: ${CONTAINER_NAME}
restart: always
networks:
Copy link
Copy Markdown
Member

@wanghe-fit2cloud wanghe-fit2cloud Apr 9, 2025

Choose a reason for hiding this comment

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

No major issues detected with the code provided. The primary change is an update to the version from 1.6.16 to 1.6.17, which may warrant further testing to ensure compatibility with your current configuration and settings. Additionally, it might be beneficial to monitor system performance after updating this service, as there could be minor changes affecting resource usage or behavior. If you encounter any unexpected behaviors, consider reverting the image version temporarily or creating rollback steps if necessary.

Expand Down