|
| 1 | +# Version 1.68.0 [2025-11-16] |
| 2 | + |
| 3 | +This is the fifth rollout out of several towards a near-future major |
| 4 | +release. This has been made possible due to a multi-year effort of |
| 5 | +internal re-designs, work with package maintainers, release, and |
| 6 | +repeat. This release fixes a few more regressions introduced in |
| 7 | +**future** 1.40.0 (2025-04-10) and 1.67.0 (2025-07-29). |
| 8 | + |
| 9 | +## Beta Features |
| 10 | + |
| 11 | + * Calling `clusterEvalQ()` on a FutureCluster, introduced in |
| 12 | + **future** 1.58.0 (2025-06-05), is now an error by default - it |
| 13 | + used to be just a warning. |
| 14 | + |
| 15 | +## Bug Fixes |
| 16 | + |
| 17 | + * `result()` on a canceled and interrupted cluster future returned |
| 18 | + the future instead of producing a FutureInterruptError. |
| 19 | + |
| 20 | + * The `cluster` backend failed when used with an `MPIcluster` as |
| 21 | + created by `parallel::makeCluster(..., type = "MPI")`. This bug was |
| 22 | + introduced in **future** (>= 1.40.0) [2025-04-10]. |
| 23 | + |
| 24 | + * Setting `R_FUTURE_PLAN=multisession` in an Renviron file, or a |
| 25 | + shell startup script, would result in a "fork bomb" when loading |
| 26 | + the **future** package. This happened because the setup of the |
| 27 | + future backend happened eagerly when the **future** package was |
| 28 | + loaded instead of being deferred to when the first future launched. |
| 29 | + This resulted in new, nested R workers being created recursively, |
| 30 | + until the machine ran out of resources. This bug was introduced in |
| 31 | + **future** (>= 1.67.0) [2025-07-29]. |
| 32 | + |
| 33 | + * ``value(..., reduce = structure(`+`, init = 42))`` is not |
| 34 | + supported, because `` `+` `` is a primitive function and one must |
| 35 | + not set attributes on primitive functions. `value()` detects this |
| 36 | + and produces an error suggestion to use `reduce = structure("+", |
| 37 | + init = 42)` instead. The latter still gave the same error, which is |
| 38 | + now fixed. |
| 39 | + |
| 40 | + |
1 | 41 | # Version 1.67.0 [2025-07-29] |
2 | 42 |
|
3 | 43 | This is the fourth rollout out of several towards a near-future major |
4 | 44 | release. This has been made possible due to a multi-year effort of |
5 | 45 | internal re-designs, work with package maintainers, release, and |
6 | | -repeat. This release fixes a few more regressions introduced in future |
7 | | -1.40.0 (2025-04-10). |
| 46 | +repeat. This release fixes a few more regressions introduced in |
| 47 | +**future** 1.40.0 (2025-04-10). |
8 | 48 |
|
9 | 49 | ## Significant Changes |
10 | 50 |
|
@@ -57,9 +97,9 @@ repeat. This release fixes a few more regressions introduced in future |
57 | 97 | This is the third rollout out of several towards a near-future major |
58 | 98 | release that I am really excited about. This has been made possible |
59 | 99 | due to a multi-year effort of internal re-designs, work with package |
60 | | -maintainers, release, and repeat. This release fixes a few |
61 | | -regressions introduced in future 1.40.0 (2025-04-10), despite passing |
62 | | -[all unit, regression, and system |
| 100 | +maintainers, release, and repeat. This release fixes a few regressions |
| 101 | +introduced in **future** 1.40.0 (2025-04-10), despite passing [all |
| 102 | +unit, regression, and system |
63 | 103 | tests](https://www.futureverse.org/quality.html). |
64 | 104 |
|
65 | 105 | ## New Features |
@@ -133,8 +173,8 @@ tests](https://www.futureverse.org/quality.html). |
133 | 173 | This is the second rollout out of three-four major updates, which is |
134 | 174 | now possible due to a multi-year effort of internal re-designs, work |
135 | 175 | with package maintainers, release, and repeat. This release fixes two |
136 | | -regressions introduced in future 1.40.0 (2025-04-10), despite passing |
137 | | -[all unit, regression, and system |
| 176 | +regressions introduced in **future** 1.40.0 (2025-04-10), despite |
| 177 | +passing [all unit, regression, and system |
138 | 178 | tests](https://www.futureverse.org/quality.html) of the Future API |
139 | 179 | that we have built up over the years. On the upside, fixing these |
140 | 180 | issues led to a greatly improved static-code analyzer for |
|
0 commit comments