Repository navigation
[UPDATE][neodb][1.0.8] Upgrade NeoDB 0.19.6.3 to 0.20.0 - #3917
Merged
Merged
Conversation
- chart version 1.0.7 -> 1.0.8; appVersion / versionName / image.neodb.tag -> 0.20.0 - all neodb containers reference .Values.image.neodb, so values.yaml is the only place the tag lives; the typesense (26.0) and busybox (1.37.0) sidecars are untouched - verified docker.io/neodb/neodb:0.20.0 exists in the registry tag list - spans seven upstream releases: 0.19.7 performance, 0.19.8 DM UI plus opt-in Mastodon streaming with security hardening, 0.19.9.1 recommendation API, 0.19.10 article/review redesign, 0.19.11 multi-line replies, 0.19.12 catalog import and dedup, 0.19.13 stop bots creating sessions, 0.20.0 federated catalog search toggle - rewrite upgradeDescription to cover the full span and flag that Django migrations run in the init-container on startup and that the database should be backed up first
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 NeoDB from
0.19.6.3to0.20.0in the Olares appneodb, chart version1.0.7->1.0.8.Changes (5 files, +26 −14)
Chart.yamlversion: 1.0.7 -> 1.0.8,appVersion: 0.19.6.3 -> 0.20.0OlaresManifest.yamlmetadata.version -> 1.0.8,spec.versionName -> 0.20.0, rewriteupgradeDescriptioni18n/en-US+i18n/zh-CNupgradeDescriptionvalues.yamlimage.neodb.tag: "0.19.6.3" -> "0.20.0"No template change: every neodb container (app, migration init-container, workers) references
{{ .Values.image.neodb.repository }}:{{ .Values.image.neodb.tag }}. Thetypesense(26.0) andbusybox(1.37.0) sidecars are untouched.Spans seven upstream releases
The chart's
migrationinit-container runs bothtakahe-manage migrateandneodb-manage migratewith|| exit 1before the app starts. A failed migration therefore blocks the container from starting, not a partial boot.Users should back up the database before upgrading. This is stated in the
upgradeDescriptionin all three manifests.Verification
docker.io/neodb/neodb:0.20.0exists — confirmed in the registry tag list (291 tags,0.20.xpresent).Chart.yaml:version=metadata.version=1.0.8;Chart.yaml:appVersion=spec.versionName=image.neodb.tag=0.20.0.0.19.6.3remains intemplates/orvalues.yaml.upgradeDescriptionidentical in structure across root / en-US / zh-CN (8 entries each).git diff --checkclean; diff limited to the 5 files above.upstream/main(9fe20f45), no merge commit.