-
Notifications
You must be signed in to change notification settings - Fork 391
chore(deps): update linuxserver/freshrss docker tag to v1.26.3 #4048
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| services: | ||
| freshrss: | ||
| image: linuxserver/freshrss:1.26.2 | ||
| image: linuxserver/freshrss:1.26.3 | ||
| container_name: ${CONTAINER_NAME} | ||
| restart: always | ||
| networks: | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The only difference is that in the updated file, For optimization suggestions:
Keep up-to-date with any community discussions or official announcements about software versions that might involve breaking changes or recommended practices post-upgrade. |
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code difference you provided appears to be for updating an
imagetag in a Docker Compose configuration file. The specific change is from version 1.26.2 to version 1.26.3 of the LinuxServer.io FreshRSS container.There are no known immediate discrepancies that would cause issues with this update. It generally indicates a bug fix or enhancement in the new version if there was one available. However, if you need further confirmation about any changes made in this release, I recommend checking the FreshRSS GitHub repository or contacting their support team directly for detailed information about updates between versions.