Repository navigation
[UPDATE][fastnotesync][1.0.3] Upgrade Fast Note Sync Service 3.5.1 to 3.6.1 - #3911
Merged
Terminus-Gitbot merged 1 commit intoNov 7, 2026
Merged
Conversation
… 3.6.1 - chart version 1.0.2 -> 1.0.3; appVersion / versionName / image.version -> 3.6.1 - image tag is hardcoded in templates/fastnotesync.yaml:22 (values.yaml image.version is not referenced by the template), so both places are bumped to stay in sync - verified docker.io/haierkeys/fast-note-sync-service:3.6.1 exists in the registry tag list (198 tags, latest 3.x is 3.6.1) - add upgradeDescription (root + en-US + zh-CN): the app had none before, so the notes cover the whole 3.5.1 -> 3.6.1 span, including the 3.5.7 concurrent-save data loss fix, 3.6.0 manual conflict handling, and 3.6.1 reverse-proxy MCP support - no config or env var change; existing data and config volumes are reused as-is
Collaborator
|
Check passed, please wait for auto-merge. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Upgrade Fast Note Sync Service from
3.5.1to3.6.1in the Olares appfastnotesync, chart version1.0.2->1.0.3.Changes (6 files, +27 −6)
Chart.yamlversion: 1.0.2 -> 1.0.3,appVersion: 3.5.1 -> 3.6.1OlaresManifest.yamlmetadata.version -> 1.0.3,spec.versionName -> 3.6.1, addupgradeDescriptioni18n/en-US/OlaresManifest.yamlupgradeDescriptioni18n/zh-CN/OlaresManifest.yamlupgradeDescriptionvalues.yamlimage.version: 3.5.1 -> 3.6.1templates/fastnotesync.yaml:3.5.1 -> :3.6.1Note on the image reference: this chart does not reference
.Values.image.versionanywhere in its templates. The image tag is hardcoded attemplates/fastnotesync.yaml:22, so bothvalues.yamland the template had to be updated together. No template logic orvalues.yamlstructure was changed.Verification
docker.io/haierkeys/fast-note-sync-service:3.6.1exists — confirmed against the registry tag list (198 tags, latest3.xis3.6.1).Chart.yaml:version=metadata.version=1.0.3, andChart.yaml:appVersion=spec.versionName=image tag=3.6.1.upgradeDescriptionis identical between the root manifest andi18n/en-US, and the zh-CN version mirrors it line by line.git diff --checkclean; diff limited to the 6 files above.upstream/main(e1f5da09), no merge commit.Upgrade notes (what users see)
The app had no
upgradeDescriptionbefore, so the new entry covers the whole3.5.1 -> 3.6.1span:object not foundon Git pull and inaccurate WebSocket client IPs.No protocol-breaking change is announced in these releases; the client
2.2.0+requirement introduced in3.5.1still applies. This chart changes no configuration or environment variable — the existing data (storage) and config volumes are reused as-is.