Skip to content

chore(deps): update frooodle/s-pdf docker tag to v0.45.3 #3654

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

chore(deps): update frooodle/s-pdf docker tag to v0.45.3 #3654

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
434b04b
chore(deps): update frooodle/s-pdf docker tag to v0.45.3
renovate[bot] Apr 9, 2025
11448e0
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/stirling-pdf/0.45.2/data.yml → apps/stirling-pdf/0.45.3/data.yml
View file
Open in desktop
File renamed without changes.
2 changes: 1 addition & 1 deletion apps/stirling-pdf/0.45.2/docker-compose.yml → apps/stirling-pdf/0.45.3/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
services:
stirling-pdf:
image: frooodle/s-pdf:0.45.2
image: frooodle/s-pdf:0.45.3
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.

The code difference seems to only involve an update of the Docker image version from frooodle/s-pdf:0.45.2 to frooodle/s-pdf:0.45.3. There is no other change that could cause problems, such as changes to environment variables, network configurations, or missing commands.

Optimization Suggestions:

  • Consider updating any associated configuration files or scripts that reference these containers to use the new image tag (0.45.3) if necessary.
  • If you have multiple instances running this service with different container names, ensure they are updated accordingly.
  • Verify that all dependencies required by this service are still compatible with the new image version.

Expand Down