fix: update backend release workflow to use app token for GitHub actions

Author: Lasim

.github/workflows/backend-release-pr.yml

@@ -30,6 +30,8 @@ jobs:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
+          # Use the app token for checkout as well
+          token: ${{ secrets.APP_INSTALLATION_TOKEN }}
       - name: git config
         run: |
           git config user.name "${GITHUB_ACTOR}"
@@ -42,7 +44,7 @@ jobs:
       - run: npm ci
       - name: Prepare release
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.APP_INSTALLATION_TOKEN }}
           TYPE_ARG: ${{ fromJSON('{"auto":"", "patch":"patch", "minor":"minor", "major":"major"}')[github.event.inputs.type] }}
           BETA_ARG: ${{ github.event.inputs.beta == 'true' && '--preRelease=beta' || '' }}
         run: npm run release -- $TYPE_ARG --ci --verbose --no-git.push --no-git.commit --no-git.tag --no-github $BETA_ARG
@@ -60,6 +62,8 @@ jobs:
         uses: peter-evans/create-pull-request@v7
         id: cpr
         with:
+          # This is the key change - use the app token
+          token: ${{ secrets.APP_INSTALLATION_TOKEN }}
           branch: backend-release
           delete-branch: true
           commit-message: 'chore(backend): release v${{ steps.package-version.outputs.current-version}}'

package-lock.json

@@ -26,21 +26,25 @@ To perform the initial setup of the database, use the following endpoint:
 
 **For SQLite:**
 The server will automatically manage the database file location. The request body should be:
+
 ```json
 {
   "type": "sqlite"
 }
 ```
+
 The SQLite database file will be created and stored at: `services/backend/persistent_data/database/deploystack.db`.
 
 **For PostgreSQL:**
 The request body should be:
+
 ```json
 {
   "type": "postgres",
   "connectionString": "postgresql://username:password@host:port/mydatabase"
 }
 ```
+
 Replace the `connectionString` with your actual PostgreSQL connection URI.
 
 **Important:** After the initial database setup via this API, you **must restart the backend server** for the changes to take full effect and for the application to connect to the newly configured database.
@@ -158,6 +162,8 @@ Tables defined by plugins are automatically created when the plugin is loaded an
 - Include proper foreign key constraints for relational data
 - Add explicit types for all columns
 - Always use migrations for schema changes in development and production
+- **Important**: When adding foreign key relationships, update the dialect-specific schema files (e.g., `src/db/schema.sqlite.ts`) rather than the central `schema.ts` file, as Drizzle Kit uses these files for migration generation
+- Never manually create migration files - always use `npm run db:generate` to ensure proper migration structure
 
 ## Inspecting the Database
 
@@ -168,6 +174,7 @@ You can inspect the SQLite database directly using various tools:
   ```bash
   sqlite3 services/backend/persistent_data/database/deploystack.db
   ```
+
   (Assuming the command is run from the project root directory)
 
 - **Visual Tools**: [DB Browser for SQLite](https://sqlitebrowser.org/) or VSCode extensions like SQLite Viewer

services/backend/DB.md

@@ -84,10 +84,12 @@ services/backend/
 The `services/backend/persistent_data/` directory is designated for storing all data that needs to persist across application restarts or deployments.
 
 **Purpose:**
+
 - To provide a single, consistent location for all persistent backend data.
 - When developing backend features that require data persistence (e.g., database files, configuration files that should not be in version control but are generated/modified at runtime), use this directory exclusively.
 
 **Examples of data stored here:**
+
 - SQLite database file (e.g., `persistent_data/database/deploystack.db`)
 - Database selection configuration (e.g., `persistent_data/db.selection.json`)