This week, we announced the brand new 1.6 version, which features major updates to the Functions ecosystem, including local development, an updated CLI, support for Go, and more. And, just like every major release before that, Appwrite 1.6 is a testament to the power of open-source collaboration. With over 40 developers contributing, we've been able to push for a faster, better, smoother product for everyone in the community.
We're incredibly grateful for the dedication and hard work of our community. Every contribution, big or small, has made a significant impact.
Therefore, we’d like to conclude Init by celebrating the people who made 1.6 possible — our open-source contributors. Thank you for helping us build a better Appwrite.
Thanks to all the contributors
We appreciate the work of everyone involved, from coding and translations to documentation. We’d like to extend our deepest thanks to:
@ItzNotABug who:
added a theme on SPA Init in #1190
fixed redirecting back to the dashboard during password recovery in #1188
fixed PNPM commands in the Contributing guide in #1256
removed unnecessary bullet point marker in #1240
fixed the tooltip location in #1275
fixed input label alignment in #1234
fixed cancel icon shifting in #1207
fixed failing GitHub install on preview instances in #1282
removed unnecessary plus icon in #1283
deleted expired tags per project in #8239
added tests to validate headers aren’t being overridden in #8228
added default to collection attributes in #8271
fixed document APIs that don't support redirects in #8233
fixed the domain check in #8472
updated Appwrite versions in #884
@blackviking27 who fixed the wizard footer overlapping with the language indicator in #1152
@iamAyushChamoli who fixed syntax for Android in documentation in #1238
@Anush008 who
@navjotNSK who added Hong Kong in translations by in #8179
@2002Bishwajeet who fixed setting the target field if the existing target document is false by in #8236
@Achraf112Ben who added Darija (Moroccan Arabic) translation file in #7501
@Snehasis4321 who fixed push notifications not working for node in #282
@kunalArya1 who fixed variable names and logging in Web and React Native docs templates in #890
@MarkPerkins who removed force unwrapping of incoming URL parameters in #887
@naman1608 who improved inline docs for Android SDK templates in #873
@svenopdehipt who updated the Flutter code to use js_interop in #810
@us3r001 who fixed the jsonSerialize return type in PHP query template in #869
@Im-Madhur-Gupta who added inline doc comments to the Web SDK template in #721
@adarshjhaa100 who created a hint to run Init and deploy commands in #720
@zlmr who:
@StarZeus who helped fix an Appwrite CLI login issue regarding the setting of cookies in #802
@theemaster who updated .NET SDK to allow null value in user model in #800
@KillTrot who changed GetValues to TryGetValues when parsing Content-Type header in the .NET SDK in #806
@svenopdehipt who added support for vision OS and fixed warnings & errors in #777
How you can contribute
Open source is at the core of Appwrite. We believe in building in the open, sharing our code, and welcoming contributions from the community. Many of our engineers came from the open-source community at Appwrite and stayed for the long run.
If you would like to play a more substantial role in the development of Appwrite, here are some ways you can make a difference:
Share your suggestions in the issues listed on our GitHub repo.
Make bug fixes and feature contributions by creating pull requests.
Raise feedback and new ideas about Appwrite in our GitHub Discussions.
Participate with other Appwrite developers in our Discord community.
Share your Appwrite project with our community on the Built With Appwrite platform.
Add any Appwrite-related educational content on our awesome-appwrite repo.
Together, let’s continue to build Appwrite through the power of open-source, and help every developer build like a team of hundreds.
