## Description
We are implementing this to control Dependabot alerts and prevent
flagging of the TinyMCE library, which we are maintaining at version
6.8.3.
* Additionally, we have reverted the change that checks for TinyMCE
version updates in the pre-commit hook. Managing this within the
Dependabot configuration file is a better approach.
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/14770091908>
> Commit: bc960270a70184b00bfee7789dd3ae3d0c2cf7b5
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=14770091908&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity`
> Spec:
> <hr>Thu, 01 May 2025 05:43: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
- **Chores**
- Added automated dependency update configuration to streamline npm
package management, with specific rules for update frequency, labeling,
and commit message formatting.
- **Refactor**
- Simplified pre-commit checks by removing restrictions related to
TinyMCE version changes.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Add a comprehensive GitHub issue template for project estimation that
includes:
- Project overview and dependencies
- Technical considerations and requirements
- Resource allocation and risk management
- CI/CD, testing, and deployment planning
- Documentation and post-release activities
This template will help teams create more thorough and standardized
project estimates.
## 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 -->
> [!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
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **New Features**
- Introduced a comprehensive project estimation template with structured
sections for users to provide detailed information on project overview,
dependencies, scope, technical considerations, CI/CD processes, testing,
release strategy, documentation, resource allocation, risk management,
and post-release activities.
<!-- 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 -->
> [!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
Refactor release client build step so that it does not fail on warnings.
## 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/13810276720>
> Commit: 1e7aeaeb24f4de71bab0c70bce385904f93fee82
> Workflow: `PR Automation test suite`
> Tags: `@tag.Sanity`
> Spec: ``
> <hr>Wed, 12 Mar 2025 11:30:35 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**
- Enhanced the build process to better capture and handle errors,
ensuring that any issues during the build are flagged promptly.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## 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 -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Chores**
- Streamlined the automated build and testing process by removing an
obsolete workflow trigger, enhancing overall efficiency.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Enabled server unit tests on TBD
Fixes #`Issue Number`
## Automation
/ok-to-test tags=""
### 🔍 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
- **Tests**
- Integrated server-side tests into our build process to further
validate critical functionalities and ensure a smoother, more reliable
experience.
- **Chores**
- Updated the build and deployment workflows to enforce thorough
pre-release validations, leading to more stable and robust releases for
our users.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
Disable server unit test in TBD
Fixes #`Issue Number`
## Automation
/ok-to-test tags=""
## 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
- **Chores**
- Streamlined our automated build and test workflows by simplifying test
dependencies.
- Enhanced the release process efficiency by removing an outdated
testing step from our continuous integration pipeline.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
/ok-to-test tags="@tag.Snowflake"## 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 -->
> [!TIP]
> 🟢🟢🟢 All cypress tests have passed! 🎉🎉🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/13448661796>
> Commit: d4e4d31e4e5086fcf4d93e76a3f7346b1301e81f
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=13448661796&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Snowflake`
> Spec:
> <hr>Fri, 21 Feb 2025 02:33:22 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**
- Enhanced our automated testing configuration by including secure
integration credentials in the test workflows.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Signed-off-by: Laveena Enid <laveena@appsmith.com>
