Skip to content

chore(deps): update dgtlmoon/changedetection.io docker tag to v0.49.16 #3817

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

chore(deps): update dgtlmoon/changedetection.io docker tag to v0.49.16 #3817

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7ba2d93
chore(deps): update dgtlmoon/changedetection.io docker tag to v0.49.16
renovate[bot] May 5, 2025
7f634bd
Update app version [skip ci]
May 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
2 changes: 1 addition & 1 deletion apps/changedetectionio/0.49.15/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ services:
- "${PANEL_APP_PORT_HTTP}:5000"
volumes:
- "./data:/datastore"
image: dgtlmoon/changedetection.io:0.49.15
image: dgtlmoon/changedetection.io:0.49.16
labels:
createdBy: "Apps"

@wanghe-fit2cloud wanghe-fit2cloud May 5, 2025

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

The difference between the two lines of code is that the container will now use image version dgtlmoon/changedetection.io:0.49.16 instead of dgtlmoon/changedetection.io:0.49.15. This suggests an update to the Docker image, likely due to bug fixes or new features in versions 0.49.15 and above.

Potential Issues:

  • If v0.49.16 contains security patches, vulnerabilities may have been addressed.
  • Any new changes or improved functionality might be available in this release.

Optimization Suggestions (if applicable):
While not specified here, consider reviewing the updated Dockerfile for any changes related to runtime configurations (e.g., environment variables), resource limits (CPU/Memory), restart policies, etc. Always ensure that any updates comply with your deployment needs and infrastructure constraints.

Expand Down