Release 0.1.12

CHANGELOG.md

@@ -1,5 +1,8 @@
 # Changelog
 
+## 0.1.12 (2024-03-14)
+- Support `link: false` on `FLAME.call/3`, `FLAME.cast/3`, and `FLAME.place_child/3` for opt-in allowance of long-running FLAME operations (up to `:shutdown_timeout`) regardless of what happens to the caller process or caller node.
+
 ## 0.1.11 (2024-02-22)
 - Add ability to configure custom metadata for launch FlyBackend machine
 

README.md

@@ -28,8 +28,8 @@ end
 Here we wrapped up our CPU expensive `ffmpeg` operation in a `FLAME.call/2`. FLAME accepts a function and any variables that the function closes over. In this example, the `%Video{}` struct and `interval` are passed along automatically. The work happens in a temporary copy of the app. We can do any work inside the FLAME call because we are running the *entire application*, database connection(s) and all.
 
 `FLAME` provides the following interfaces for elastically scaled operations:
-  * `FLAME.call/2` - used for synchronous calls
-  * `FLAME.cast/2` - used for async casts where you don't need to wait on the results
+  * `FLAME.call/3` - used for synchronous calls
+  * `FLAME.cast/3` - used for async casts where you don't need to wait on the results
   * `FLAME.place_child/3` – used for placing a child spec somewhere to run, in place of `DynamicSupervisor.start_child`, `Task.Supervisor.start_child`, etc
 
 The `FLAME.Pool` handles elastically scaling runners up and down, as well as remote monitoring of resources. Check the moduledoc for example usage.

mix.exs

@@ -4,7 +4,7 @@ defmodule FLAME.Runner.MixProject do
   def project do
     [
       app: :flame,
-      version: "0.1.11",
+      version: "0.1.12",
       elixir: "~> 1.14",
       elixirc_paths: elixirc_paths(Mix.env()),
       start_permanent: Mix.env() == :prod,