8a3c192301
- Add scheduling scope section to README explaining global vs project execution scopes - Document scope resolution rules: scope=global for cross-project, scope=project for per-project - Add operational guidance for multi-project setups (backups, insight extraction vs CI, deployments) - Update architecture.md to mention scoped automations/routines in store and API descriptions - Add scheduling scope section to settings-reference.md covering cron defaults and interaction with autoBackup and insightExtraction settings - Add changeset for @gsxdsm/fusion minor release documenting scoped scheduling feature
13 lines
593 B
Markdown
13 lines
593 B
Markdown
---
|
|
"@gsxdsm/fusion": minor
|
|
---
|
|
|
|
Add scoped scheduling support for automations and routines
|
|
|
|
Schedules and routines now support `global` and `project` execution scopes:
|
|
- **Global** schedules run across all projects (e.g., backups, cross-project maintenance)
|
|
- **Project** schedules run within a single project only (e.g., per-project CI, deployments)
|
|
- Backward-compatible default: omitted scope resolves to `project` with `projectId="default"`
|
|
- Dashboard Scheduled Tasks modal includes a Global/Project scope toggle
|
|
- API endpoints accept `?scope=global` or `?scope=project&projectId=<id>`
|