feat: a continuous trigger on a batch build warns at validate; scaffold-composer schedules only builds a scheduler starts by fas89 · Pull Request #737 · Agenticstiger/forge-cli

feat(validate): warn on trigger.type continuous on a build forge-cli runs as a batch run

fas89

committed

21f7fba

fix(build-runners): the dbt and python runners refuse trigger.type continuous by name

fas89

committed

cfa1547

fix(scaffold-composer): no DAG for a contract no scheduler starts, and the cron of a scheduled build

fas89

committed

39618b7

docs(changelog): a continuous trigger on a batch build warns; scaffold-composer schedules only scheduled builds

fas89

committed

4b02f2a

fix(scaffold-composer): print the old DAG's path whole, so it copies

fas89

committed

c0d187e

fix(build-runners): fluid validate and fluid apply agree on a continuous build

fas89

committed

6453701

fix(scaffold-composer): name only a DAG it wrote, and keep the DAG for declared tasks

fas89

committed

2a09abe

docs(changelog): validate and apply agree on continuous builds; scaffold-composer keeps DAGs for declared tasks

fas89

committed

66e4bed

fix(build-runners): the python runner keeps every build it runs, continuous or not

fas89

committed

1c8daa4

docs(changelog): which continuous builds fluid apply leaves to their platform; when scaffold-composer names an old DAG

fas89

committed

9529b01

fix(validate): a continuous spark, glue or custom build is told to name its platform

fas89

committed

d098dde

Navigation Menu

Repository navigation

feat: a continuous trigger on a batch build warns at validate; scaffold-composer schedules only builds a scheduler starts - #737

feat: a continuous trigger on a batch build warns at validate; scaffold-composer schedules only builds a scheduler starts#737
fas89 wants to merge 11 commits into
mainfrom
feat/continuous-batch-scaffold

Commits on Oct 21, 2026

feat(validate): warn on trigger.type continuous on a build forge-cli runs as a batch run

fix(build-runners): the dbt and python runners refuse trigger.type continuous by name

fix(scaffold-composer): no DAG for a contract no scheduler starts, and the cron of a scheduled build

docs(changelog): a continuous trigger on a batch build warns; scaffold-composer schedules only scheduled builds

fix(scaffold-composer): print the old DAG's path whole, so it copies

fix(build-runners): fluid validate and fluid apply agree on a continuous build

fix(scaffold-composer): name only a DAG it wrote, and keep the DAG for declared tasks

docs(changelog): validate and apply agree on continuous builds; scaffold-composer keeps DAGs for declared tasks

fix(build-runners): the python runner keeps every build it runs, continuous or not

docs(changelog): which continuous builds fluid apply leaves to their platform; when scaffold-composer names an old DAG

fix(validate): a continuous spark, glue or custom build is told to name its platform