🌟 Release Highlights
This release simplifies cache-memory configuration by removing restrictive default file type limitations, making persistent storage more flexible for AI agents.
✨ What's New
Simplified Cache-Memory Configuration - Cache-memory now allows all file types by default when cache-memory: true is specified without explicit allowed-extensions. Previously, only .json, .jsonl, .txt, .md, and .csv files were allowed by default, requiring manual configuration for other file types. This change:
- Reduces boilerplate - No need to specify
allowed-extensionsfor common use cases where agents need to store varied data formats - Maintains security options - Explicit
allowed-extensionsrestrictions still work when you need them - Improves workflow clarity - Validation steps are automatically omitted when all files are allowed, reducing compiled workflow size
Example - Before (required configuration):
cache-memory:
enabled: true
allowed-extensions: [".json", ".xml", ".log", ".dat"] # Had to list every typeExample - After (simpler default):
cache-memory: true # All file types allowed by defaultMigration: Existing workflows with explicit allowed-extensions continue to work unchanged. Remove the allowed-extensions field to adopt the new permissive default.
🔧 Technical Details
- Updated
DefaultAllowedMemoryExtensionsfrom restricted list to empty array ([]) - Workflow compiler skips validation step generation when no restrictions are configured
- Recompiled 77 workflow lock files to remove unnecessary validation steps
- All existing tests updated and passing
For complete details, see the CHANGELOG.
Generated by Release
What's Changed
- [WIP] Change default allowed extensions in cache-memory to empty by @Copilot in #15263
Full Changelog: v0.43.12...v0.43.13