## Description - Added server bump from 11 to 12 to support an autocommit for git directory structural change 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 --> > [!IMPORTANT] > 🟣 🟣 🟣 Your tests are running. > Tests running at: <https://github.com/appsmithorg/appsmith/actions/runs/15038406686> > Commit: de3f46bb37c29ebb91adc6fd8c82da6e284d5526 > Workflow: `PR Automation test suite` > Tags: `@tag.All` > Spec: `` > <hr>Thu, 15 May 2025 06:43:48 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 application structure during schema migration, enabling better organization of source modules by package. - **Improvements** - Enhanced support for autocommit of structural changes in the git directory. - Updated schema version to ensure compatibility with the latest migration. - **Deprecation** - Removed deprecated status from the run behaviour field in layout updates. - **Other Changes** - Adjusted visibility of certain fields for improved data handling and migration consistency. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: “sneha122” <“sneha@appsmith.com”> |
||
|---|---|---|
| .. | ||
| .run | ||
| appsmith-git | ||
| appsmith-interfaces | ||
| appsmith-plugins | ||
| appsmith-server | ||
| envs | ||
| mongo-seed | ||
| reactive-caching | ||
| scripts | ||
| .gitignore | ||
| build.sh | ||
| buildpack-run.sh | ||
| pom.xml | ||
| Procfile | ||
| README.md | ||
| system.properties | ||
Appsmith Server
This is the server-side repository for the Appsmith framework.
For details on setting up your development machine, please refer to this Setup Guide.