Release v2.4.2
Appsmith v2.4.2 includes security updates for bundled dependencies including Bouncy Castle, fixes for page cloning performance to prevent memory exhaustion, improved UI consistency for Ask AI and OAuth2 fields, and enhancements to Git and deployment tools. Appsmith AI reaches end-of-life on September 30, 2026, and users must migrate to direct provider datasources.
🗑️ Feature Removal Reminder - September 30, 2026 - EOL
Appsmith AI reaches end of life on September 30th, 2026.
As announced in v2.3 and v2.4, you can no longer add new Appsmith AI datasource connections or queries. Existing ones stop working on that date — whether or not you have upgraded.
Migrate remaining Appsmith AI queries to a direct provider datasource (OpenAI, Anthropic, or Google AI) before September 30th.
🔐 Security
- Updated bundled dependencies to address reported vulnerabilities, including Bouncy Castle. (#42265)
🛠️ Reliability
- Cloning a page with many actions no longer loads the page document once per action, which could exhaust server memory. (#42228)
- Used fixed Segment user IDs for instance-start and Redis-compile events so those calls no longer inflate Monthly Tracked Users. (#42246)
🎨 UI & Widget Improvements
- Restored Ask AI visibility for Developer-role users. (#42274)
- Moved the OAuth2 “Authorization expires in” field next to Scope(s) on authenticated API datasources. (#42191)
🔧 Git, Deployment & Configuration
appsmithctl enable-form-loginnow passes the full Redis URL (auth, port, and TLS) when evicting the cached organization. (#42235)
Source: original entry ↗