## Description An adjustment to client build that will allow it to pass in case there are warnings. Current behavior is strict and fails build if there is a warning. We could suppress warnings, but would rather be aware that there is a potential problem. This relates to a problem described in the following [Slack thread](https://theappsmith.slack.com/archives/CPG2ZTXEY/p1741188291297589). Adjusting the build behavior seems like the best option. ## 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/13709134043> > Commit: 223772797d57326f8c1d4a022c6fb17bbbccb991 > <a href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=13709134043&attempt=1" target="_blank">Cypress dashboard</a>. > Tags: `@tag.Sanity` > Spec: > <hr>Thu, 06 Mar 2025 22:42:51 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 - **Chores** - Improved the client application build process with enhanced error handling to capture and respond to issues more effectively, ensuring that significant build failures are promptly addressed. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| config-test.json | ||
| config.json | ||
| config.yml | ||
| labeler.yml | ||
| pull_request_template.md | ||
| release-drafter-template.yml | ||
| reviewers.yml | ||
| semantic.yml | ||