|
1 | | -## R CMD check results |
2 | | - |
3 | | -0 errors | 0 warnings | 1 note |
| 1 | +## Reason for this submission |
4 | 2 |
|
5 | | -* This is a new release. |
| 3 | +This is an urgent maintenance release requested by Yves Rosseel (lavaan |
| 4 | +maintainer). A new lavaan feature (`optim.fix.saturated`, default `TRUE` in |
| 5 | +the upcoming lavaan 0.7-1) causes 4 of mlstats' `method = "sem"` tests to |
| 6 | +fail, because those tests depended on lavaan converging on an inadmissible |
| 7 | +(out-of-range) standardized solution for certain degenerate/small-sample |
| 8 | +models. lavaan 0.7-1 now converges on an admissible solution instead for |
| 9 | +those same models. This is currently blocking lavaan 0.7-1's own submission |
| 10 | +to CRAN. The relevant tests have been adjusted accordingly (see NEWS.md); |
| 11 | +no user-facing behavior of mlstats itself has changed. The package's test |
| 12 | +suite passes with both lavaan 0.6-21 (current CRAN release) and lavaan |
| 13 | +0.7-1 (verified locally against the pre-release version from the |
| 14 | +maintainer's r-universe). |
6 | 15 |
|
7 | | -## Notes |
| 16 | +This release also bundles a handful of unrelated bug fixes and |
| 17 | +documentation/output improvements accumulated since 0.1.0 (see NEWS.md). |
8 | 18 |
|
9 | | -`devtools::check(cran = TRUE)` reports "unable to verify current time" in |
10 | | -some local runs; this is a network-reachability artifact of the local check |
11 | | -environment (it cannot reach the time-verification service) and is unrelated |
12 | | -to package content. |
13 | | - |
14 | | -## win-builder / R-hub |
| 19 | +## R CMD check results |
15 | 20 |
|
16 | | -Checked on win-builder (R-devel) and R-hub (Linux, macOS x86_64/arm64, |
17 | | -R-devel). All clean except: |
| 21 | +0 errors | 0 warnings | 2 notes |
18 | 22 |
|
19 | | -* win-builder flags "APA", "ICCs", "REWB", and "intraclass" as possibly |
20 | | - misspelled in DESCRIPTION. These are established abbreviations/terms in |
21 | | - the multilevel-modeling literature, not typos. |
| 23 | +* `checking CRAN incoming feasibility ... NOTE`: "Days since last update: 4". |
| 24 | + Expected, and the reason for the rush is explained above. |
| 25 | +* `checking for future file timestamps ... NOTE`: "unable to verify current |
| 26 | + time". This is a network-reachability artifact of the local check |
| 27 | + environment (it cannot reach the time-verification service) and is |
| 28 | + unrelated to package content; it also appeared on the 0.1.0 submission. |
0 commit comments