## Description
Decoupled property registration code and lazily initialise it in the
property pane component.
Fixes #`Issue Number`
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.All"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15461239247>
> Commit: 9c70387f49a2f6dd53dbcd824a31b458aa4d0e2c
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15461239247&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.All`
> Spec:
> <hr>Thu, 05 Jun 2025 08:50:15 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
## Summary by CodeRabbit
- **New Features**
- Improved loading behavior in the property pane to ensure all controls
are fully ready before display, resulting in a smoother user experience.
- **Bug Fixes**
- Prevented the property pane from rendering incomplete or missing
controls during loading.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
On protected branches, we neither allow auto-commits nor expose the
results of the git status API. As a result, these two API calls are
redundant. Skipping them can reduce load times by approximately 30
seconds on protected branches.
Furthermore, since auto-commits are disabled for protected branches,
there's a high chance that the branch contains an outdated version of
the DSL. This often results in uncommitted changes in the file system
for those branches. Such uncommitted changes can slow down subsequent
checkouts to other branches, as Git needs to re-index these files before
performing a reset. These delays are even more pronounced when using an
EFS.
This PR removes the auto-commit and status API calls for protected
branches.
Fixes #`Issue Number`
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.Git"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15459263185>
> Commit: 2b04a0edf89088795192d6fb1a068bf868ae924f
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15459263185&attempt=2"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Git`
> Spec:
> <hr>Thu, 05 Jun 2025 07:51:10 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Added the ability to explicitly reset Git status for artifacts,
providing clearer feedback when working with protected branches.
- **Bug Fixes**
- Improved handling of protected branches by preventing unnecessary
status checks and auto-commit operations, ensuring protected branches
are not modified unintentionally.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Problem
With the introduction of cloud billing and multi-organization support,
users can now access Appsmith through organization-specific subdomains
(e.g., `testorg.appsmith.com`). However, when users attempt to access
non-existent domains (e.g., `domaindoesnotexist.appsmith.com`), the
system fails to return a user object, causing the application to get
stuck in an infinite loading state.
## 🔍 Root Cause
The issue was in the `LandingScreen` component's conditional logic:
```tsx
// Previous implementation ❌
if (props.user && window.location.pathname === BASE_URL) {
if (props.user.email === ANONYMOUS_USERNAME) {
return <Redirect to={AUTH_LOGIN_URL} />;
} else {
return <Redirect to={APPLICATIONS_URL} />;
}
}
```
**The problem:** When accessing a non-existent domain, `props.user` is
`null`/`undefined`, causing the condition `props.user &&
window.location.pathname === BASE_URL` to evaluate to `false`. This
prevented the redirect logic from executing, leaving users on a
perpetual loading screen instead of being properly redirected to the
login page.
## ✅ Solution
Updated the conditional logic to handle cases where the user object is
undefined:
```tsx
// Fixed implementation ✅
if (window.location.pathname === BASE_URL) {
if (!props.user || props.user.email === ANONYMOUS_USERNAME) {
return <Redirect to={AUTH_LOGIN_URL} />;
} else {
return <Redirect to={APPLICATIONS_URL} />;
}
}
```
### Key changes:
1. **Removed the `props.user &&` guard condition** - Now the redirect
logic always executes when on the base URL
2. **Added explicit null/undefined check** - The condition `!props.user
|| props.user.email === ANONYMOUS_USERNAME` properly handles both
scenarios:
- When no user object exists (non-existent domains)
- When the user is anonymous
## 📊 Impact
| Scenario | Before | After |
|----------|---------|-------|
| Valid org domain + authenticated user | ✅ Redirects to applications |
✅ Redirects to applications |
| Valid org domain + anonymous user | ✅ Redirects to login | ✅ Redirects
to login |
| **Non-existent org domain** | ❌ **Infinite loading screen** | ✅
**Redirects to login** |
| Direct access to login URL | ✅ Works as expected | ✅ Works as expected
|
## 🧪 Testing Scenarios
This fix addresses the following scenarios in the cloud billing
multi-org environment:
- [x] Valid organization domain with authenticated user → Redirects to
applications
- [x] Valid organization domain with anonymous user → Redirects to login
- [x] **Non-existent organization domain → Redirects to login (instead
of infinite loading)**
- [x] Direct access to login URL → Works as expected
## Automation
/ok-to-test tags="@tag.Authentication, @tag.Sanity"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15438685266>
> Commit: afee6b1b89b3bf2c65290a1cef9355e72c1ab14e
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15438685266&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Authentication, @tag.Sanity`
> Spec:
> <hr>Wed, 04 Jun 2025 10:09:08 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Bug Fixes**
- Improved user redirection on the landing screen to ensure users are
correctly routed based on their authentication status.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
> [!TIP]
> _Add a TL;DR when the description is longer than 500 words or
extremely technical (helps the content, marketing, and DevRel team)._
>
> _Please also include relevant motivation and context. List any
dependencies that are required for this change. Add links to Notion,
Figma or any other documents that might be relevant to the PR._
Fixes #`Issue Number`
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags=""
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!WARNING]
> Tests have not run on the HEAD
e467ca42e83258bc29f2f4c54ef64b69be7e53a1 yet
> <hr>Wed, 04 Jun 2025 06:27:38 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Tests**
- Temporarily disabled the "Verify Queries" test case in the client-side
regression test suite.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: “sneha122” <“sneha@appsmith.com”>
Before the options of dropdown control could load up, the dropdown
control was hitting `onChange` which was resetting the options for that
control.
This PR adds a check to look for selectionOptions before resetting the
options.
/ok-to-test tags="@tag.Sanity"
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
## Summary by CodeRabbit
- **Bug Fixes**
- Improved the behavior of multi-select dropdowns to ensure selected
values are only re-synced when valid options are present, preventing
unnecessary updates.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15319483195>
> Commit: caa978dc326fe017c06c7ceafe64f6f1890814fe
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15319483195&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity`
> Spec:
> <hr>Thu, 29 May 2025 09:01:42 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Description
<ins>Problem</ins>
When editing the Computed Value field of a column in the Table widget, a
closing round bracket `)` is automatically removed from specific
expressions upon losing focus, leading to broken expressions and
incorrect widget behavior.
<ins>Root cause</ins>
Incorrect handling of double curly braces and nested parentheses in the
`computedValue` parsing logic.
<ins>Solution</ins>
This PR handles the correction of expression parsing in
`ComputeTablePropertyControlV2` by updating the extraction logic to
support nested parentheses correctly. It also includes a test to ensure
this functionality works as expected.
Fixes#40265
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.Table"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15061326484>
> Commit: 156df279926fc8e39f194d46e868d46c62a1b2bf
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15061326484&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Table`
> Spec:
> <hr>Fri, 16 May 2025 06:11:17 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Bug Fixes**
- Improved handling of malformed expressions in table computed value
inputs, resulting in more consistent error output.
- Enhanced default computed value behavior to provide a fallback when
table data is empty, preventing errors.
- **Tests**
- Updated and expanded test cases for computed value extraction,
including new input variations and revised expectations for malformed
expressions.
- **Chores**
- Added a migration step to update older computed values for correct
display in widgets.
- Incremented DSL version to include latest migration updates.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Fixes a bug where the organization's `displayName` and `slug` fields
were not being properly stored in the Redux state when fetching the
current organization configuration.
## Changes
- Added `displayName` and `slug` fields to the
`FETCH_CURRENT_ORGANIZATION_CONFIG_SUCCESS` reducer handler
- These fields were already defined in the `OrganizationReduxState`
interface but were missing from the actual state update
## Automation
/ok-to-test tags="@tag.Sanity"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15286413781>
> Commit: cca1886b0d8dd24a9193dab5a0a5a7a3c004cda2
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15286413781&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity`
> Spec:
> <hr>Tue, 27 May 2025 22:31:26 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Organization details now display additional information, including
display name and slug, when viewing organization configuration.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
### Summary
This PR updates the styling of the user full name input field on the
onboarding screen to match the styling of the radio button groups,
creating a more consistent and polished UI.
### Problem
The full name input field in the onboarding form had inconsistent
styling compared to the radio button groups, which created a visually
disjointed user experience.
### Solution
- Created a styled version of `FormTextField` that matches the styling
of radio buttons
- Added proper spacing with a dedicated `InputSection` component
- Removed unnecessary vertical spacing elements
- Ensured consistent typography, sizing, and spacing across form
elements
### Changes
- Added `StyledFormTextField` with custom CSS to match radio button
styling:
- Same font size and weight for labels
- Consistent height, padding, and border-radius
- Full width input field
- Created `InputSection` for consistent vertical spacing
- Replaced original `FormTextField` with the styled version
- Removed redundant `Space` components
### Screenshots
![Before](
<img width="1449" alt="Screenshot 2025-05-22 at 6 50 04 AM"
src="https://github.com/user-attachments/assets/54384e0d-4874-4550-8415-54b15a8e9b13"
/>
) | ![After](
<img width="1452" alt="Screenshot 2025-05-22 at 6 39 38 AM"
src="https://github.com/user-attachments/assets/01b8fd1e-0c47-4d8f-abe7-4f47a31366b6"
/>
)
## Automation
/ok-to-test tags="@tag.Sanity, @tag.Authentication"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15205128744>
> Commit: 6e26d5ad7afef489697362b9202d7fd3be5b63a0
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15205128744&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity, @tag.Authentication`
> Spec:
> <hr>Fri, 23 May 2025 08:33:29 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Added a required full name field to the non-super user profiling form,
displayed when cloud billing is enabled.
- **Style**
- Improved input field appearance and adjusted vertical spacing for a
cleaner form layout.
- **Refactor**
- Streamlined form styling by introducing new styled components and
localizing spacing definitions.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
<img width="658" alt="Screenshot 2025-05-23 at 11 32 51 AM"
src="https://github.com/user-attachments/assets/bdbd051d-7135-41b1-8789-921547a91802"
/>
Fixes https://github.com/appsmithorg/appsmith/issues/40741
## Automation
/ok-to-test tags="@tag.All"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15203473904>
> Commit: 76b7112333792f4612b5ef6e4524552c99fe88a8
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15203473904&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.All`
> Spec:
> <hr>Fri, 23 May 2025 07:28:05 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Enhanced the "Navigate To" section to adjust available tabs and
default selection based on the IDE type, offering a tailored experience
for UIPackage IDE users.
- **Improvements**
- Improved loading state handling by considering additional action
sources, resulting in more accurate widget loading indicators.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
### Purpose
This PR enhances the List Widget's template handling system to better
support meta widgets, especially when used within UI modules. It ensures
proper widget name handling and template identification across different
contexts.
### Key Changes
1. Added `isTemplate` property to widget static and DSL structure props
to identify template widgets
2. Introduced `getTemplateMetaWidgets` selector to identify and manage
template meta widgets
3. Enhanced the List Widget to properly handle template meta widgets by:
- Preserving original widget names for template meta widgets
- Preventing template meta widgets from being treated as regular meta
widgets
- Improving widget name handling in form submissions
4. Added proper type definitions and documentation for template meta
widget functionality
### Technical Impact
- Better support for List Widget templates in UI modules
- Improved widget name handling for meta widgets
- Better separation between template and regular meta widgets
PR for https://github.com/appsmithorg/appsmith-ee/pull/7567
## Automation
/ok-to-test tags="@tag.All"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15153885090>
> Commit: d838448c2b1e880f55b5b99476e3a19a2153b21f
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15153885090&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.All`
> Spec:
> <hr>Wed, 21 May 2025 06:15:33 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Improved handling of template widgets, allowing original widget names
to be preserved and used where applicable.
- Enhanced filtering and processing of template meta widgets in List and
Form widgets for more accurate data mapping and rendering.
- Added support for identifying and managing template widgets across the
app's widget structure.
- **Bug Fixes**
- Prevented template widgets from being incorrectly rendered or included
in meta widget generation.
- **Refactor**
- Updated internal widget processing to consistently manage and cache
flattened child canvas widgets, improving reliability and
maintainability.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
<ins>Problem</ins>
The table widget skipped validations for number columns when users typed
quickly and pressed Enter, accepting invalid values despite min/max
constraints.
<ins>Root cause</ins>
The validation logic had an early exit if the value was empty and the
column wasn't required. This incorrectly allowed empty values even when
min/max constraints were set. Due to async evaluations and timing
differences, a quick backspace followed by a new input and Enter led to
premature validation success.
<ins>Solution</ins>
This PR handles a refactor of the validation logic in `TableWidgetV2` to
improve clarity and correctness.
- Consolidates checks for required fields and regex validations.
- Ensures column type validations accurately reflect constraints like
min/max.
- Prevents premature validation passes caused by async evaluation race
conditions.
Fixes #`Issue Number`
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.Table"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15160290045>
> Commit: b3022119656954765a79b1e03c5af2a4338a89c4
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15160290045&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Table`
> Spec:
> <hr>Wed, 21 May 2025 11:35:27 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Bug Fixes**
- Enhanced validation for editable table cells to better enforce
required fields and regex patterns.
- Improved handling of empty values in required and non-required cells
for more accurate validation feedback.
- **Tests**
- Refactored and reorganized validation test suites for improved clarity
and maintainability without changing validation behavior.
- Updated end-to-end tests to improve timing and synchronization by
removing fixed waits and relying on automatic retries.
- Adjusted inline editing validation tests to reflect updated error
visibility expectations during editing.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
If a user's session times out and the user navigates to a new page in an
application the user was not navigated to the login page. This change
makes sure that the user profile is updated in the redux store on page
change and the page response is validated using the response
interceptors.
This bug was introduced in [this
PR](https://github.com/appsmithorg/appsmith/pull/36096).
Fixes #`Issue Number`
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.All"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15155628540>
> Commit: a3349cda620d3af78d2604f9edea151f6f15408e
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15155628540&attempt=2"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.All`
> Spec:
> <hr>Wed, 21 May 2025 08:31:39 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Bug Fixes**
- Improved error handling when loading published page resources,
ensuring better management of API errors and user profile updates.
- **Refactor**
- Updated internal handling of API response error codes for consistency.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Handling the case when reactive actions feature flag is turned off and
the run behaviour is Automatic. We are updating the run behaviour in UI
alone (not DB) to show page load instead in this case.
Fixes [#40703](https://github.com/appsmithorg/appsmith/issues/40703)
## Automation
/ok-to-test tags="@tag.All"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15144630350>
> Commit: ae4b5b6dafdb6ddc729828f46987afc68a634643
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15144630350&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.All`
> Spec:
> <hr>Tue, 20 May 2025 19:22:57 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Updated dropdown and function settings to respect feature flags,
ensuring certain options are shown or hidden based on feature
availability.
- **Bug Fixes**
- Improved handling of run behavior selection when specific feature
flags are disabled, automatically adjusting selections to maintain
consistent user experience.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
<ins>Problem</ins>
Inbuilt email validation was not functioning correctly for all valid
email formats (e.g. `rahul+3@appsmith.com`), leading to incorrect
validation failures in the Input widget.
<ins>Root cause</ins>
Outdated or overly restrictive email validation regex in
`InputWidgetV2`.
<ins>Solution</ins>
This PR handles updating the email validation regex in `InputWidgetV2`
to support modern and valid email formats.
It also refactors and enhances the validation test suite to improve
coverage across input types (NUMBER, TEXT, EMAIL, PASSWORD) and
validation scenarios (required, custom, and regex), improving accuracy,
readability, and maintainability.
Fixes #`Issue Number`
_or_
Fixes https://github.com/appsmithorg/appsmith-ee/issues/7550
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.Input"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15133467577>
> Commit: 35d061427857620e3c3a4a2b6e5a7d1b532652aa
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15133467577&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Input`
> Spec:
> <hr>Tue, 20 May 2025 09:29:25 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Bug Fixes**
- Improved email validation to support a wider range of valid email
formats.
- **Tests**
- Expanded and reorganized input validation tests to cover more input
types and edge cases, ensuring more robust validation across NUMBER,
TEXT, EMAIL, and PASSWORD fields.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Updating the dropdown width for the run behavior settings of JS object
Fixes [#40657](https://github.com/appsmithorg/appsmith/issues/40657)
## Automation
/ok-to-test tags="@tag.JS, @tag.IDE"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15113084468>
> Commit: 8b29ef23202e1ae2c1c0c05012ee2f94ec6a85d2
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15113084468&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.JS, @tag.IDE`
> Spec:
> <hr>Mon, 19 May 2025 13:26:04 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Added an option to control whether the dropdown menu width matches the
select input width, or to set a custom width for dropdown menus.
- **Style**
- Improved popover content width handling for more consistent display.
- Adjusted minimum width of select input in function settings for a more
compact appearance.
- Dropdown menus in function settings now have a fixed width for better
usability.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
This PR implements the multi-organization login page UI to improve the
authentication experience for users within organizations.
## Changes
- Add new message constants for multi-org login footer in messages.ts
- Update OrganizationReduxState interface to include displayName and
slug properties
- Modify Container component to accept React.ReactNode for title prop
- Implement organization-specific title and subtitle on login page
- Add footer with contextual options for users:
- "Not the right organization?" - Allows users to enter a different
organization URL
- "Not part of the organization?" - Redirects to the sign-up page
- "Looking to create one?" - Redirects to organization creation
## How to Test
1. Enable the `license_multi_org_enabled` feature flag
2. Access the login page through an organization subdomain
3. Verify that the organization name appears in the title
4. Verify that the organization slug appears in the subtitle
5. Test the footer links to ensure they redirect to the correct pages
## Automation
/ok-to-test tags="@tag.Sanity, @tag.Authentication"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15110788513>
> Commit: a16c118b747331c152aff2f85fd021f63b041ecc
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15110788513&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity, @tag.Authentication`
> Spec:
> <hr>Mon, 19 May 2025 11:28:08 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Enhanced login page to support multi-organization environments,
including dynamic titles, subtitles, and a new footer with contextual
messages and links for different organization scenarios.
- **Improvements**
- Login page title now supports rich content, allowing for more flexible
display.
- Organization information now includes display name and slug for
improved context in multi-org scenarios.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
This PR fixes an issue where the left side content in the authentication
screen wasn't displaying properly when the multi-organization feature
was enabled.
## Fix
Updated the condition in the `UserAuth` container to correctly display
the left side content when the multi-org feature flag is enabled.
## Testing
* Verified the left side content appears correctly with multi-org
enabled.
* Ensured the component still behaves correctly on mobile devices.
* Confirmed the UI renders properly with and without branding enabled.
## Automation
/ok-to-test tags="@tag.Sanity, @tag.Authentication"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15109876659>
> Commit: 4f88a93734ff4a6f71b5fed22dd8364a14486093
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15109876659&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity, @tag.Authentication`
> Spec:
> <hr>Mon, 19 May 2025 10:38:49 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Refactor**
- Updated the conditions for displaying the left side content on the
user authentication page, which may change when this content is visible
to users based on organization and branding settings.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
This PR allows module private entities i.e queries and JS objects to be
listed in the action selectors of a UI module.
The selectors return`[]` in CE and is extended in EE
PR for https://github.com/appsmithorg/appsmith-ee/pull/7455
## Automation
/ok-to-test tags="@tag.All"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15061113685>
> Commit: 176563bb507a71b9d8164c2d518150b7d644f698
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15061113685&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.All`
> Spec:
> <hr>Fri, 16 May 2025 06:26:21 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Expanded action and JS collection selection to include both page-level
and module-level options in relevant dropdowns and hooks.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Updating the styles for JS settings popover
Fixes#40657
## Automation
/ok-to-test tags="@tag.JS"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15045634120>
> Commit: 0346eec44945dee8b0a98ece911e23f36709c5b2
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15045634120&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.JS`
> Spec:
> <hr>Thu, 15 May 2025 13:49:10 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Added the ability to customize the width of the settings popover in
toolbars.
- **Style**
- Improved text wrapping for function names in the function settings
panel.
- Adjusted spacing and set a minimum width for dropdown selectors to
enhance layout consistency.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
<ins>Problem</ins>
Table failed to load data for a page when network or query failures
occurred with infinite scroll enabled.
<ins>Root cause</ins>
There was no fallback or handling mechanism for offline scenarios or
query failures, causing the table to enter an unusable state.
<ins>Solution</ins>
This PR handles enhancing offline data handling for the table when
infinite scroll is enabled.
We ensure that a data fetch request for the next page is triggered
regardless of the scenario.
* For example, if we are on page 2 and attempt to navigate to page 3,
but the network request fails due to being offline or a timeout, we
recognize that we lack data for page 3. If the user reverse scrolls and
then resumes scrolling toward page 3, we will issue a new request.
* This process relies on accurately tracking the current page and the
user's scrolling intent, while also checking the data we have already
received.
Fixes#40579
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.Table"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15011754024>
> Commit: 9c48e7cd795cfa6e10f35151a46fa62c42be0e0f
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15011754024&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Table`
> Spec:
> <hr>Wed, 14 May 2025 04:22:05 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
## Summary by CodeRabbit
- **New Features**
- Improved infinite scroll in tables with enhanced data caching,
reducing redundant data requests and improving performance during
pagination.
- Table components now leverage cached data for smoother scrolling and
more efficient page loading.
- **Performance**
- Optimized table rendering to prevent unnecessary re-renders when
cached data remains unchanged.
- **Bug Fixes**
- Prevented updates to end-of-data status when offline, avoiding
incorrect data state during connectivity issues.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
<ins>Problem</ins>
Table search results included irrelevant search results.
<ins>Root cause</ins>
System columns were not excluded in the search logic, causing them to be
considered during filtering.
<ins>Solution</ins>
This PR handles the exclusion of system columns from the table search
logic, ensuring only relevant user-visible columns are considered during
filtering. This improves the accuracy and clarity of search results.
Fixes#39469
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.Table"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/15011289429>
> Commit: 0ca8bca0d058575be52458ae53c095818cab36c8
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15011289429&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Table`
> Spec:
> <hr>Wed, 14 May 2025 03:41:27 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Bug Fixes**
- Improved search functionality in tables by excluding system columns
from search results, ensuring more accurate filtering.
- **Tests**
- Added and reorganized tests to validate search behavior, focusing on
exclusion of system and hidden columns from search results.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
/ok-to-test tags="@tag.Sanity"
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/14994848262>
> Commit: 64bdb8cd0606bbc4c1b11d69b2d0e7cd7b5dd78a
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14994848262&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity`
> Spec:
> <hr>Tue, 13 May 2025 11:39:41 UTC
<!-- end of auto-generated comment: Cypress test results -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Introduced a new feature flag for AI agent instances, allowing for
more granular control over AI agent-related functionality.
- **Refactor**
- Updated various components and selectors to use the new AI agent
instance feature flag and related selectors, replacing previous flags
and logic.
- Separated agent and non-agent template handling for clearer template
management.
- Improved feature flag override capabilities, enabling dynamic
overrides via external sources.
- Added new selectors to better represent AI agent app and creation
states.
- Refined UI components and modals to reflect updated AI agent state
flags.
- Enhanced user authentication and signup flows with updated feature
flag conditions.
- **Bug Fixes**
- Ensured consistent UI behavior and conditional rendering based on the
updated feature flag logic.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Update the field for widget in AI chat widget
## Automation
/ok-to-test tags="@tag.Sanity"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/14970367321>
> Commit: ce4a027e3892b8610a46ce07b6632b6f9a64c6c8
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14970367321&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity`
> Spec:
> <hr>Mon, 12 May 2025 11:35:44 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
## Summary by CodeRabbit
- **New Features**
- Updated AI chat widget configuration to use dynamic query references,
enhancing flexibility and tracking.
- **Chores**
- Upgraded the DSL migration system to support the latest version.
- **Bug Fixes**
- Improved reliability when creating or updating data sources by
ensuring actions complete before proceeding.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
<ins>Problem</ins>
Existing columns could be lost during data updates when infinite scroll
was enabled, leading to inconsistent table display.
<ins>Root cause</ins>
New column data from paginated responses was replacing the existing
column state instead of merging with it.
<ins>Solution</ins>
This PR handles enhancing the column merging logic in infinite scroll
mode by combining new columns with existing ones, ensuring consistent
and complete column display across paginated data updates.
Fixes#40457
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.Table"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/14905173364>
> Commit: cb86d0f940cc97d8823b521ddd454e72eeb25f32
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14905173364&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Table`
> Spec:
> <hr>Thu, 08 May 2025 11:53:39 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Bug Fixes**
- Improved handling of table columns when infinite scroll is enabled,
ensuring columns remain consistent and preventing data issues as new
pages are loaded.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
<ins>Problem</ins>
App was crashing when the data source configuration was undefined or in
an error state.
<ins>Root cause</ins>
The code attempted to access properties from an undefined data source
config (e.g., MongoDB), leading to runtime errors.
<ins>Solution</ins>
This PR handles adding an optional check before accessing the data
source config to prevent crashes when the config is undefined or in an
error state.
Fixes #`Issue Number`
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.JSONForm, @tag.PropertyPane, @tag.GenerateCRUD,
@tag.Datasource, @tag.Sanity, @tag.Widget"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/14905964982>
> Commit: bcd0f9d2d009bcf07bb10afda1a30ff1a93bc9ae
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14905964982&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.JSONForm, @tag.PropertyPane, @tag.GenerateCRUD,
@tag.Datasource, @tag.Sanity, @tag.Widget`
> Spec:
> <hr>Thu, 08 May 2025 13:32:39 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Bug Fixes**
- Improved stability when accessing data source tables, preventing
potential errors if data source information is missing.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Fixing partial export spec
Fixes [#39833](https://github.com/appsmithorg/appsmith/issues/39833)
## Automation
/ok-to-test tags=""
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!CAUTION]
> If you modify the content in this section, you are likely to disrupt
the CI result for your PR.
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
## Description
<ins>Problem</ins>
Table would show inconsistent views or appear empty when infinite scroll
setting changed or component height was modified.
<ins>Root cause</ins>
Page number was not reset properly during changes to infinite scroll or
component height, causing the table to render an incorrect or empty
state.
<ins>Solution</ins>
This PR handles improving the reset logic for the table when infinite
scroll is enabled or component height changes. It refactors the reset
conditions, introduces variables to track relevant state changes, and
ensures the table resets correctly to maintain consistent behavior.
Fixes#40411
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.Table"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/14903775919>
> Commit: efe1c54169d21708cb519e749047ff207fffeb0e
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14903775919&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Table`
> Spec:
> <hr>Thu, 08 May 2025 10:36:21 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Refactor**
- Improved the logic for resetting the table when infinite scroll is
enabled or when the component height changes, resulting in clearer and
more consistent behavior. No visible changes to features or exported
entities.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
/ok-to-test tags="@tag.Anvil"
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/14900550928>
> Commit: a3a3579aaac44d2cfdfa956d46024145c4bfdad9
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14900550928&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Anvil`
> Spec:
> <hr>Thu, 08 May 2025 07:22:28 UTC
<!-- end of auto-generated comment: Cypress test results -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Style**
- Introduced a named container ("flex-container") to relevant CSS
classes for improved container query support.
- Updated container queries to explicitly reference the new container
name, enabling more precise and scoped responsive styling.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
<ins>Problem</ins>
Table pagination would not reset properly when infinite scroll was
reset, leading to incorrect data display or user being stuck on a
non-existent page.
<ins>Root cause</ins>
The `resetTableForInfiniteScroll` method did not reset the page number,
causing the table to continue from an outdated page index.
<ins>Solution</ins>
This PR handles resetting the page number to 0 in the
`resetTableForInfiniteScroll` method, ensuring the table starts from the
first page during infinite scroll resets for consistent pagination
behavior.
Fixes#40594
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.Table"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/14884926062>
> Commit: ec11d1637f68bcdcdf42dbb8b8078bdf468f40f1
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14884926062&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Table`
> Spec:
> <hr>Wed, 07 May 2025 14:22:58 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Bug Fixes**
- Resolved an issue where resetting the table with infinite scroll did
not return to the first page. Now, the table correctly resets to the
first page when infinite scroll is used.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
PR for https://github.com/appsmithorg/appsmith-ee/pull/7306
## Automation
/ok-to-test tags="@tag.All"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/14830581904>
> Commit: 6a2c282f6c7ae2f8040b7f573d850e30e217bba8
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14830581904&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.All`
> Spec:
> <hr>Mon, 05 May 2025 07:57:49 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Added a loading state to indicate when a page setup process is in
progress.
- Introduced a selector to access the page setup loading state.
- Updated page saving process to handle layout payload generation
asynchronously.
- Added support for updating meta widget properties with dynamic path
computation.
- **Bug Fixes**
- Improved error handling to prevent unhandled exceptions during state
updates.
- **Chores**
- Enhanced property controls by merging enterprise edition controls with
the existing set.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Fixes#39932
| Before | After |
|--------|--------|
| <img width="674" alt="Screenshot 2025-05-07 at 10 38 06"
src="https://github.com/user-attachments/assets/052adffd-7d90-47c2-95ea-cc15e4fa89b1"
/> | <img width="676" alt="Screenshot 2025-05-07 at 10 36 39"
src="https://github.com/user-attachments/assets/80056605-1bda-4c02-ad4f-8827f93bc2ca"
/> |
## Automation
/ok-to-test tags="@tag.Sanity"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!IMPORTANT]
> 🟣🟣🟣 Your tests are running.
> Tests running at:
<https://github.com/appsmithorg/appsmith/actions/runs/14879153124>
> Commit: f691f26b504269eaaa960626392789db7ff7f0f3
> Workflow: `PR Automation test suite`
> Tags: `@tag.Sanity`
> Spec: ``
> <hr>Wed, 07 May 2025 08:48:38 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [x] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Style**
- Adjusted the brightness of subtle neutral background and foreground
colors in light mode for improved visual appearance.
- **Tests**
- Updated expected color values in tests to match the new brightness
adjustments.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Adds a new AI integrations form and a feature flag to control it
## Automation
/ok-to-test tags="@tag.Sanity"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/14852368949>
> Commit: 047893cddfa36128ca4b07263ef2e49afba40fe1
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14852368949&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity`
> Spec:
> <hr>Tue, 06 May 2025 06:16:52 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Introduced a new AI Chat Integrations form control component.
- Added a feature flag to enable or disable AI Chat Integrations.
- **Chores**
- Registered the new form control type and component in the form control
registry.
- Updated feature flag override capabilities to include the new AI Chat
Integrations flag.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Slightly more subtle and nicer-looking border.
## Automation
/ok-to-test tags="@tag.Sanity"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/14837454433>
> Commit: ba34566ae70e97803acd3ecf3a8fe726633a4fac
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14837454433&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity`
> Spec:
> <hr>Mon, 05 May 2025 14:09:11 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [x] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Style**
- Adjusted the subtle neutral border color in light mode to appear less
bright, affecting the appearance of outlined buttons.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
> [!TIP]
> _Add a TL;DR when the description is longer than 500 words or
extremely technical (helps the content, marketing, and DevRel team)._
>
> _Please also include relevant motivation and context. List any
dependencies that are required for this change. Add links to Notion,
Figma or any other documents that might be relevant to the PR._
Fixes #`Issue Number`
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.All"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/14789475280>
> Commit: 8c69931e4d5fb6b319883e8d1ba33f553029f346
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14789475280&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.All`
> Spec:
> <hr>Fri, 02 May 2025 07:00:53 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Introduced a new feature flag to control the computation cache
capability.
- **Enhancements**
- Added checks to ensure computation caching only occurs when the
corresponding feature flag is enabled.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Adds support for disabling widget renaming in the property pane through
a `isRenameDisabled` property. When enabled, it displays a tooltip
explaining this limitation when hovering over the widget name.
Additionally, this PR hides module widgets from the widget card
selection by filtering out widgets whose type starts with
"MODULE_WIDGET_".
Fixes https://github.com/appsmithorg/appsmith/issues/40495
## Automation
/ok-to-test tags="@tag.Widget"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/14794711021>
> Commit: 3f94eafdef52b4d0543de99f9472fb3970ee415e
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14794711021&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Widget`
> Spec:
> <hr>Fri, 02 May 2025 13:12:08 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Added the ability to disable renaming for certain widget titles,
displaying a tooltip when renaming is not allowed.
- **Improvements**
- Widgets identified as module widgets are now excluded from the widget
cards list in the UI.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Updating fixtures to replace executeOnLoad with reactiveActions
Fixes [#39833](https://github.com/appsmithorg/appsmith/issues/39833)
## Automation
/ok-to-test tags=""
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!CAUTION]
> If you modify the content in this section, you are likely to disrupt
the CI result for your PR.
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
## Description
Updating the spelling for `runBehaviour`
Fixes #
## Automation
/ok-to-test tags=""
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!CAUTION]
> If you modify the content in this section, you are likely to disrupt
the CI result for your PR.
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
## Description
> [!TIP]
> _Add a TL;DR when the description is longer than 500 words or
extremely technical (helps the content, marketing, and DevRel team)._
>
> _Please also include relevant motivation and context. List any
dependencies that are required for this change. Add links to Notion,
Figma or any other documents that might be relevant to the PR._
Fixes #`Issue Number`
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags="@tag.Sanity"
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/14776408755>
> Commit: acd4de6042b9ca6e4112d9e59371096d8e8a2b93
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14776408755&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity`
> Spec:
> <hr>Thu, 01 May 2025 14:26:46 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Enhanced telemetry with improved log capture, allowing for structured
logging with customizable log levels and additional context.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
