Repository navigation
chore(release): appwrite 1.0.0 - #16
Conversation
🟢 Tier S · Ready to merge
This release change versions the chart as 1.0.0 for Appwrite 2.3.0 and records the first-release feature summary in the changelog and Artifact Hub metadata. It updates the release checklist and version references in the guides, and makes the chart-label unit test use an explicit chart version.
📂 Walkthrough · 7
Reviewed |
The first release of the chart, for Appwrite 2.3.0. - CHANGELOG.md: the entries move to [1.0.0], rewritten as a summary of what the first release ships rather than the history of unreleased changes. - Chart.yaml: version 1.0.0, artifacthub.io/prerelease "false", and artifacthub.io/changes regenerated from the changelog. - docs/upgrading.md and docs/gitops.md name 1.0.0. - RELEASING.md: the first-release checklist is for 1.0.0, and the repository has to be public before the release pull request merges. - The chart-label unit test sets its own chart version, so version bumps don't break it.
6967677 to
124f33c
Compare
|
1.0.0 is published and verified (2026-10-14).
How it went: the first run (38530606243) pushed the chart and then failed on Still to do:
|
What
Cuts 1.0.0, the first release of the chart, for Appwrite 2.3.0. Nothing has been published before, so the SemVer promise starts here.
CHANGELOG.md: the entries move to[1.0.0], rewritten as a summary of what the first release ships (11 entries) rather than the history of unreleased changes.Chart.yaml:version: 1.0.0,artifacthub.io/prerelease: "false", andartifacthub.io/changesregenerated withmake changes.docs/upgrading.md,docs/gitops.md: name 1.0.0.RELEASING.md: the first-release checklist is for 1.0.0, and the repository must be public before this merges.tests/scheduling_test.yaml: the chart-label test sets its own chart version, so version bumps don't break it.Merging publishes the release: OCI push to
ghcr.io/appwrite/charts/appwrite, cosign signature, provenance attestation, GitHub releaseappwrite-1.0.0and Artifact Hub metadata (seeRELEASING.md).Before merging
GitHub Actions hasn't run since 2026-10-12: while the repository is private, jobs aren't started ("recent account payments have failed or your spending limit needs to be increased"). The release workflow also skips itself on a private repository. So, by an org owner or repository admin:
existingtest fixture, a<password>placeholder).main: require a pull request and the Lint and test checks (both Lint jobs, both Unit test jobs, kubeconform, Generated files are up to date, Chart metadata, Artifact Hub lint, Changelog).After merging
charts/appwritepackage public and link it to this repository. Until thenhelm installneeds a GHCR login; check withhelm registry logout ghcr.ioand thehelm show chartabove.oci://ghcr.io/appwrite/charts/appwrite), putrepositoryIDand an owner inartifacthub-repo.yml, and re-run the Release workflow, which then only pushes the metadata.RENOVATE_HOOK_*secrets (CONTRIBUTING.md, "Renovate pull requests").Testing
make testpasses locally: ct lint,helm lint --stricton everyci/scenario, 236/236 unit tests, kubeconform on Kubernetes 1.29–1.37, examples, generated files,check-changes.helm package, push to a local OCI registry, pull and render from it; the workflow's release-notes extraction produces the[1.0.0]section.Checklist
make testpasses locallymake generatewas run and the generated files are committeddocs/and files inexamples/updated for changes to how the chart is configuredCHANGELOG.mdandartifacthub.io/changesfor the release (this is the release pull request)Renamed or removed values go through Deprecating a value(none)