chore(appwrite): bump appwrite to 1.9.5#707
Conversation
github-actions
Bot
added
area:docs
area:tests
area:values
chart:appwrite
Standards Check (GR-079) — PASSEvery changed chart fully passes standards-check. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughThis PR updates the Appwrite and console image versions in chart metadata, default values, documentation, and deployment tests, and adds upgrade notes for the Appwrite 1.9.5 migration step. ChangesAppwrite/Console Image Version Bump
Estimated code review effort: 1 (Trivial) | ~5 minutes Related Issues: Suggested labels: dependencies, chart-update Suggested reviewers: helmforgedev-maintainers 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
🟢 Security Scan:
|
| Framework | Score |
|---|---|
| MITRE + NSA + SOC2 | 79.59956% |
✅ Security posture acceptable.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
charts/appwrite/README.md (1)
57-77: 🧹 Nitpick | 🔵 TrivialConsider documenting the required migration step for this upgrade.
Upstream Appwrite release notes for 1.9.5 explicitly state the migrate command must be run even when upgrading from 1.9.0. Users of this chart bumping from an older release won't see that warning here.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@charts/appwrite/README.md` around lines 57 - 77, Add a migration note to the Appwrite chart README’s default values/upgrade documentation section so users upgrading to this version know they must run the Appwrite migrate command, even when coming from 1.9.0. Update the README content near the existing configuration table and reference the chart’s Appwrite upgrade guidance so the required step is visible alongside the release defaults.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@charts/appwrite/README.md`:
- Around line 57-77: Add a migration note to the Appwrite chart README’s default
values/upgrade documentation section so users upgrading to this version know
they must run the Appwrite migrate command, even when coming from 1.9.0. Update
the README content near the existing configuration table and reference the
chart’s Appwrite upgrade guidance so the required step is visible alongside the
release defaults.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 6635c9c8-6dd3-4fb8-9601-085fb7e99c8d
📒 Files selected for processing (5)
charts/appwrite/Chart.yamlcharts/appwrite/README.mdcharts/appwrite/tests/deployment_api_test.yamlcharts/appwrite/tests/deployment_console_test.yamlcharts/appwrite/values.yaml
|
Handled the CodeRabbit top-level nitpick in 68cc996. Added Appwrite 1.9.5 upgrade notes to the chart README so users see the required upstream database migration step, including the Kubernetes Validation:
This CodeRabbit item was posted only in the review summary, so there is no resolvable review thread to close. |
1 participant
Closes #688.
Summary
Upstream Evidence
docker.io/appwrite/appwrite:1.9.5supportslinux/amd64andlinux/arm64.docker.io/appwrite/console:8.7.5supportslinux/amd64andlinux/arm64.Site Sync
Validation
make image-verify IMAGE=docker.io/appwrite/appwrite:1.9.5make image-verify IMAGE=docker.io/appwrite/console:8.7.5make deps-check CHART=appwritehelm unittest charts/appwritemake validate-chart CHART=appwritepassed fully: 19 layers, including k3d behavioral validation for default and all CI values scenarios.make standards-check CHART=appwritenode scripts/charts/template-standards-check.js --chart appwritemake release-check REPO=chartsmake attribution-check REPO=chartsNotes
The first k3d run hit Docker Hub pull QPS limits while pulling the new Appwrite image across many workloads. I imported
docker.io/appwrite/appwrite:1.9.5anddocker.io/appwrite/console:8.7.5into thek3d-helmforge-tests-wslcontainerd cache and reran the canonical gate successfully.Summary by CodeRabbit