CLI commands with `--run-command` used to always start a separate
headless process, even when the target project was already open in the
editor. They now goes to the live window so results
(for example imported extensions) appear in memory right away, without
reopening the project.
- Replace the third-party `[email protected]` with the official Esoteric Software runtime for PixiJS v7 (`@esotericsoftware/[email protected]`).
- The new runtime only fully supports skeletons exported from **Spine 4.2**. Older exports (e.g. 4.0) may partially render but mesh deformations won't work due to a Spine JSON schema change (`deform` → `attachments`).
- Add `--run-command` CLI flag that executes any Command Palette command after loading a project.
In CLI mode all blocking dialogs (autosave, changelog, confirmations) are auto-resolved, the window is hidden, and the process exits with a meaningful exit code.
- This enables CI pipelines to run exports (e.g. `EXPORT_HTML5_EXTERNAL`) using only the editor distribution - no installation or display required.
- Diagnostic Report previously only scanned layout (scene) events and external events for validation errors. This PR extends the report to also scan events inside extension functions - including top-level ("free") functions, behavior functions, and object functions - detecting missing instructions and invalid parameters.
- Store-installed extensions are excluded from the scan
- Disabled ("commented out") events and their sub-events are skipped everywhere, not just in extensions.
- Add a shortcut (**F7** by default) and command in the command palette to open diagnostic report at any time
- The report now scans project for missing actions/conditions/expressions from extensions and reports invalid parameters (shown with red underline in Events Sheet)
- Click on error location to navigate directly to the event
* This adds support for configurable toolbar buttons in the GDevelop desktop editor that execute npm scripts from the project's package.json in external terminal windows. Buttons are defined in the `gdevelop-settings.yaml` file in the project directory.
For example, create a `gdevelop-settings.yaml` in your project root:
```
toolbarButtons:
- name: "Build"
icon: "🔨"
npmScript: "build"
- name: "Test"
icon: "🧪"
npmScript: "test"
```
* Add `clearCanvas` field to `RuntimeScene` class and pass it to `PIXI.Renderer.render` as `clear` option to support multi-scene rendering.
* Show in developer changelog
Gleb Volkov