Repository navigation
chore(release): appwrite 2.0.0 - #23
Conversation
- CHANGELOG.md: [Unreleased] becomes [2.0.0] - 2026-10-14, with a pointer to the upgrade notes. - Chart.yaml: version 2.0.0, and artifacthub.io/changes regenerated. - docs/upgrading.md: chart 2.0.0 deploys Appwrite 2.5.0, and "To 2.0.0" covers the storage decision, the privileged executor, the moved S3 keys, the removed assistant and what Appwrite 2.4.0 and 2.5.0 change. - docs/gitops.md names 2.0.0.
chore(release): appwrite 2.0.0
🔵 Tier A · Mergeable after minor fixes
Cuts the Appwrite Helm chart 2.0.0 release, records its changes and upgrade guidance, and updates the chart-version references in the README and GitOps examples.
Fix with agent prompt### Issue 1
docs/gitops.md:283
**Argo CD example omits secrets required by 2.0 defaults**
With this revision, Functions/Sites and built-in S3 are enabled by default, but the example sets `appwrite.secrets.generate: false` without supplying the compute and S3 credentials those defaults require. Argo CD rendering therefore fails; please update the example with the managed secrets and references needed for these defaults, or disable/configure the affected features.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.📂 Walkthrough · 5
Reviewed |
![hansi-codes[bot]](https://avatars.githubusercontent.com/in/5046327?s=60&v=4){kind=small}
| repoURL: ghcr.io/appwrite/charts | ||
| chart: appwrite | ||
| targetRevision: 1.0.0 | ||
| targetRevision: 2.0.0 |
There was a problem hiding this comment.
Argo CD example omits secrets required by 2.0 defaults
With this revision, Functions/Sites and built-in S3 are enabled by default, but the example sets appwrite.secrets.generate: false without supplying the compute and S3 credentials those defaults require. Argo CD rendering therefore fails; please update the example with the managed secrets and references needed for these defaults, or disable/configure the affected features.
Prompt To Fix With AI
This is a comment left during a code review.
Path: docs/gitops.md
Line: 283
Comment:
**Argo CD example omits secrets required by 2.0 defaults**
With this revision, Functions/Sites and built-in S3 are enabled by default, but the example sets `appwrite.secrets.generate: false` without supplying the compute and S3 credentials those defaults require. Argo CD rendering therefore fails; please update the example with the managed secrets and references needed for these defaults, or disable/configure the affected features.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.🟡 Minor · documentation · Reply if this doesn't apply.
|
2.0.0 is published and verified (2026-10-14).
Upgrading from 1.0.0: docs/upgrading.md#to-200. Installs that hold files on the volume set |
1 participant
What
The release commit from #22, onto
main. #22 was merged intofeat/compute-by-default(its stacked base) before GitHub retargeted it tomain, somainhas #21's changes but still saysversion: 1.0.0. This branch isfeat/compute-by-defaultas it is now:mainpluscc81d9e(and #22's merge commit). The diff is exactly #22's:CHANGELOG.md[2.0.0],Chart.yamlversion: 2.0.0andartifacthub.io/changes, the chart README badge,docs/upgrading.md"To 2.0.0", anddocs/gitops.md.Merging publishes 2.0.0 (Chart.yaml changes on
main).The two Release runs on
mainsince #21 (the push, and a manual run at 10:36) found 1.0.0 already published (sha256:31b5abe6…), already signed and attested, and changed nothing. 2.0.0 isn't in the registry yet.Testing
Reviewed and tested as #22 (hansi-codes approved; every check green, including the upgrade from chart 1.0.0). The checks run again here.