Mention that future.mirai::mirai_multisession is now also supporting progress updates

Author: HenrikBengtsson

DESCRIPTION

@@ -1,5 +1,5 @@
 Package: progressr
-Version: 0.15.1-9009
+Version: 0.15.1-9010
 Title: An Inclusive, Unifying API for Progress Updates
 Description: A minimal, unifying API for scripts and packages to report progress updates from anywhere including when using parallel processing.  The package is designed such that the developer can to focus on what progress should be reported on without having to worry about how to present it.  The end user has full control of how, where, and when to render these progress updates, e.g. in the terminal using utils::txtProgressBar(), cli::cli_progress_bar(), in a graphical user interface using utils::winProgressBar(), tcltk::tkProgressBar() or shiny::withProgress(), via the speakers using beepr::beep(), or on a file system via the size of a file. Anyone can add additional, customized, progression handlers. The 'progressr' package uses R's condition framework for signaling progress updated. Because of this, progress can be reported from almost anywhere in R, e.g. from classical for and while loops, from map-reduce API:s like the lapply() family of functions, 'purrr', 'plyr', and 'foreach'. It will also work with parallel processing via the 'future' framework, e.g. future.apply::future_lapply(), furrr::future_map(), and 'foreach' with 'doFuture'. The package is compatible with Shiny applications.
 Authors@R: c(person("Henrik", "Bengtsson",

README.md

@@ -772,14 +772,15 @@ requires **plyr** (>= 1.8.7).
 
 ### Near-live versus buffered progress updates with futures
 
-As of April 2025, there are five types of **future** backends that are
+As of August 2025, there are six types of **future** backends that are
 known(*) to provide near-live progress updates:
 
  1. `sequential`,
  2. `multicore`,
  3. `multisession`, and
  4. `cluster` (local and remote)
- 4. `future.callr::callr`
+ 5. `future.callr::callr`
+ 6. `future.mirai::mirai_multisession`
 
 Here "near-live" means that the progress handlers will report on
 progress almost immediately when the progress is signaled on the

incl/OVERVIEW.md

@@ -764,14 +764,15 @@ requires **plyr** (>= 1.8.7).
 
 ### Near-live versus buffered progress updates with futures
 
-As of April 2025, there are five types of **future** backends that are
+As of August 2025, there are six types of **future** backends that are
 known(*) to provide near-live progress updates:
 
  1. `sequential`,
  2. `multicore`,
  3. `multisession`, and
  4. `cluster` (local and remote)
- 4. `future.callr::callr`
+ 5. `future.callr::callr`
+ 6. `future.mirai::mirai_multisession`
 
 Here "near-live" means that the progress handlers will report on
 progress almost immediately when the progress is signaled on the

vignettes/progressr-intro.md

@@ -775,14 +775,15 @@ requires **plyr** (>= 1.8.7).
 
 ### Near-live versus buffered progress updates with futures
 
-As of April 2025, there are five types of **future** backends that are
+As of August 2025, there are six types of **future** backends that are
 known(*) to provide near-live progress updates:
 
  1. `sequential`,
  2. `multicore`,
  3. `multisession`, and
  4. `cluster` (local and remote)
- 4. `future.callr::callr`
+ 5. `future.callr::callr`
+ 6. `future.mirai::mirai_multisession`
 
 Here "near-live" means that the progress handlers will report on
 progress almost immediately when the progress is signaled on the