NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
A wrapper around the Appwrite Function Context.
Last release 24 days ago
15 Sep 2026
Release timing varies
gaps range from 3 weeks to 9 months
Nearly every release is documented
notes for 3 of 3 stable releases
Nothing withdrawn
no release was ever pulled
10 months old
3 releases · first in 2025
One column per month.
Added response header support to text, json, binary, redirect, html, success, and error responses, matching the current Open Runtimes Dart runtime sig
text, json, binary, redirect, html, success, and error responses, matching the current Open Runtimes Dart runtime signatures.ExecutionResponse.binary now accepts List<int> instead of Uint8List, and html/success/error now route through the public text() method.ExecutionRequest.query is now Map<String, String> (was Map<String, dynamic>), matching the runtime.ExecutionContext.log/error now accept Object? instead of String, matching the runtime.RequestHeaders.event is now String? (was dynamic); RequestHeaders map-style accessors (values, entries, forEach) now use Object? instead of dynamic.RequestHeaders.requireValue<T>() now gives a clearer error when the header is missing entirely, versus present with the wrong type.EnvVar.deploymentType, EnvVar.cpus, EnvVar.memory, and nullable VCS metadata getters (vcsRepositoryId, vcsRepositoryBranch, vcsCommitHash, etc.) for currently documented Appwrite environment variables.EnvVar.parseOptionalString() plus testable parseBoolValue/parseIntValue/parseDoubleValue helpers.main(context) parameter can no longer be final), and gave example/ its own pubspec.yaml so it resolves and analyzes cleanly.package:lints/recommended.yaml in analysis_options.yaml (previously present only as a comment) and added a unit test suite.Add optional HTTP status code parameters to ExecutionResponse helpers
- Initial release
Your coding agent can read these notes before it upgrades. Set up the MCP server →