The update-toast.yml workflow should only run when new litestar releases are cut. Research (and if possible implement) the usage of repository_dispatch or similar event kickoffs for workflows that will let us dynamically do this.
i wonder if we can use repository_dispatch to dynamically do this instead of killing trees
The
update-toast.yml
workflow should only run when new litestar releases are cut. Research (and if possible implement) the usage ofrepository_dispatch
or similar event kickoffs for workflows that will let us dynamically do this.i wonder if we can use repository_dispatch to dynamically do this instead of killing trees
_Originally posted by @JacobCoffee in https://github.com/litestar-org/litestar.dev/pull/24#discussion_r1558817572_