NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
A service that provides HTTP caching to the response data for Angel3
Last release 4 days ago
05 Oct 2026
Ships fairly regularly
a new release about every 6 months
Nearly every release is documented
notes for 15 of 15 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
15 releases · first in 2021
One column per quarter.
fix: CacheService.read now stores a cache miss with cache.update, under the requested id.
CacheService.read now stores a cache miss with cache.update, under the requested id.ResponseCache now stores only responses that are safe to share: status 200, no cookies, and not marked Cache-Control: no-store or private. Requests with an Authorization header bypass the cache. Responses that are not cached no longer get Cache-Control: public headersResponseCache memory is now bounded by maxEntries (default 1024), evicting expired then least recently used entries; previously every distinct URL (including query strings) added an entry and a lock that were never removedCacheService writes now update (modify, update) or evict (remove) the entry in the shared cache service, so other instances using the same cache no longer serve stale or deleted recordsCacheService.update now calls database.update instead of database.modifyCacheService.read no longer throws on params without a query, uses the cache for reads without params, and falls back to the database when the cache is unavailableResponseCache now caches normal responses: handleRequest buffers the response on a cache miss, so handlers no longer need res.useBuffer() (previously only buffered responses were cached, so most never were)ResponseCache now answers 304 Not Modified (no body) when the client's copy is current, instead of resending the full body with 200. A client sending back the exact Last-Modified value is recognized (dates are compared in whole seconds), and one with an older copy gets the cached response instead of bypassing the cachecacheSerializationResults now works: results are cached per object instance across requests, shouldCache is consulted, timeout is honoured, a result is reused only for the same serializer, and async serializers are supportedcache_test.dart deterministic and corrected two assertions that expected the old behaviourResponseCache(maxEntries: ...)pool and meta dependencies, and the unused glob dev dependency- Require Dart >= 3.13
- Require Dart >= 3.12.0
Updated dependencies to the latest release
lints to 6.0.0Updated dependencies to the latest release
lints to 5.0.0* Require Dart >= 3.3 * Updated lints to 4.0.0
lints to 4.0.0* Updated repository link
* Updated lints to 3.0.0 * Fixed linter warnings
lints to 3.0.0Updated: angel3_container_generator
- Require Dart >= 2.17
- Require Dart >= 2.16 - Added ORM MySQL
Updated linter to package:lints
package:lints* Updated README * Added home page link * All 7 unit tests passed
Fixed: Return 200 with cached data instead of 403
200 with cached data instead of 403Published all packages with angel3_ prefix
angel3_ prefixYour coding agent can read these notes before it upgrades. Set up the MCP server →