Release 0.5.14

Author: adamw

README.md

@@ -23,13 +23,13 @@ the project!
 To test Ox, use the following dependency, using either [sbt](https://www.scala-sbt.org):
 
 ```scala
-"com.softwaremill.ox" %% "core" % "0.5.13"
+"com.softwaremill.ox" %% "core" % "0.5.14"
 ```
 
 Or [scala-cli](https://scala-cli.virtuslab.org):
 
 ```scala
-//> using dep "com.softwaremill.ox::core:0.5.13"
+//> using dep "com.softwaremill.ox::core:0.5.14"
 ```
 
 Documentation is available at [https://ox.softwaremill.com](https://ox.softwaremill.com), ScalaDocs can be browsed at [https://javadoc.io](https://www.javadoc.io/doc/com.softwaremill.ox).

generated-doc/out/index.md

@@ -2,7 +2,7 @@
 
 Safe direct-style concurrency and resiliency for Scala on the JVM. Requires JDK 21 & Scala 3.
 
-To start using Ox, add the `com.softwaremill.ox::core:0.5.13` [dependency](info/dependency.md) to your project. 
+To start using Ox, add the `com.softwaremill.ox::core:0.5.14` [dependency](info/dependency.md) to your project. 
 Then, take a look at the tour of Ox, or follow one of the topics listed in the menu to get to know Ox's API!
 
 In addition to this documentation, ScalaDocs can be browsed at [https://javadoc.io](https://www.javadoc.io/doc/com.softwaremill.ox).

generated-doc/out/info/dependency.md

@@ -4,10 +4,10 @@ To use ox core in your project, add:
 
 ```scala
 // sbt dependency
-"com.softwaremill.ox" %% "core" % "0.5.13"
+"com.softwaremill.ox" %% "core" % "0.5.14"
 
 // scala-cli dependency
-//> using dep com.softwaremill.ox::core:0.5.13
+//> using dep com.softwaremill.ox::core:0.5.14
 ```
 
 Ox core depends only on the Java [jox](https://github.com/softwaremill/jox) project, where channels are implemented. There are no other direct or transitive dependencies.

generated-doc/out/integrations/cron4s.md

@@ -3,7 +3,7 @@
 Dependency:
 
 ```scala
-"com.softwaremill.ox" %% "cron" % "0.5.13"
+"com.softwaremill.ox" %% "cron" % "0.5.14"
 ```
 
 This module allows to run schedules based on cron expressions from [cron4s](https://github.com/alonsodomin/cron4s).

generated-doc/out/integrations/kafka.md

@@ -3,7 +3,7 @@
 Dependency:
 
 ```scala
-"com.softwaremill.ox" %% "kafka" % "0.5.13"
+"com.softwaremill.ox" %% "kafka" % "0.5.14"
 ```
 
 `Flow`s which read from a Kafka topic, mapping stages and drains which publish to Kafka topics are available through

generated-doc/out/integrations/mdc-logback.md

@@ -3,7 +3,7 @@
 Dependency:
 
 ```scala
-"com.softwaremill.ox" %% "mdc-logback" % "0.5.13"
+"com.softwaremill.ox" %% "mdc-logback" % "0.5.14"
 ```
 
 Ox provides support for setting inheritable MDC (mapped diagnostic context) values, when using the [Logback](https://logback.qos.ch)

generated-doc/out/integrations/otel-context.md

@@ -3,7 +3,7 @@
 Dependency:
 
 ```scala
-"com.softwaremill.ox" %% "otel-context" % "0.5.13"
+"com.softwaremill.ox" %% "otel-context" % "0.5.14"
 ```
 
 When using the default OpenTelemetry context-propagation mechanisms, which rely on thread-local storage, the context

generated-doc/out/streaming/flows.md

@@ -171,7 +171,7 @@ To obtain a `org.reactivestreams.Publisher` instance, you'll need to add the fol
 bring the `toReactiveStreamsPublisher` method into scope:
 
 ```scala
-// sbt dependency: "com.softwaremill.ox" %% "flow-reactive-streams" % "0.5.13"
+// sbt dependency: "com.softwaremill.ox" %% "flow-reactive-streams" % "0.5.14"
 
 import ox.supervised
 import ox.flow.Flow

generated-doc/out/structured-concurrency/fork-join.md

@@ -136,4 +136,12 @@ completed.
 ## Customizing thread creation
 
 By default, for each fork a new virtual thread is created using `Thread.ofVirtual().factory()`. This can be customized
-globally using `oxThreadFactory`.
+globally using `oxThreadFactory`.
+
+## Integrating structured concurrency with other libraries
+
+When integrating with libraries which manage their own threads, e.g. reactive libraries, it is sometimes necessary to
+be able to start forks from such library-managed threads. For this purpose, the `inScopeRunner` method can be used.
+
+A runner obtained from a scope-managed thread can be passed to other threads, and used to start forks within the
+concurrency scope, as long as it's not complete, from arbitrary threads.