-
Notifications
You must be signed in to change notification settings - Fork 419
chore(deps): update b3log/siyuan docker tag to v3.1.18 #2877
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
File renamed without changes.
File renamed without changes.
2 changes: 1 addition & 1 deletion
2
apps/siyuan/3.1.17/docker-compose.yml → apps/siyuan/3.1.18/docker-compose.yml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
There is an update to the
imagefield fromb3log/siyuan:v3.1.17tob3log/siyuan:v3.1.18, which suggests that there has been a new release available on Docker Hub for SiYuan. This could be due to bug fixes, feature improvements, or security updates.Potential Issues: There may not be any known issues with this specific version of SiYuan based solely on its name change. However, it's good practice to review the changelog for both versions to ensure no critical changes were made.
Optimization Suggestions:
Use Tag Constraints: Ensure your Kubernetes manifest (e.g.,
Deployment.yaml) specifies exact tags instead of using a range (v3.1.*). This allows better control over the image used and can help avoid unexpected behavior during upgrades.Environment Variables: If you need to set environment variables specific to different production environments (Dev/Staging/Production), consider encapsulating them within separate config maps or secrets rather than hardcoding in your deployment files. This improves maintainability and scalability.
Consider Upgrading Dependencies:** Check if there are any compatibility requirements between the updated SiYuan version and other components such as database drivers, plugins, or third-party tools being used in your SIYuan instance. Upgrade dependencies only in cases where they resolve conflicts or improve performance.
Backup Strategy: Ensure you have a robust backup process in place before making significant updates like these. A complete dump of all data plus configuration settings should be stored separately.
By addressing these areas, you can minimize downtime and ensure smooth operation of the SiYuan service after updating to v3.1.18.