- patch release, following a change of the web service the package is a
client for: the German Reference Corpus behind the default KorAP instance
was re-released (DeReKo-KorAP-2026-II) and renamed the
textClassmetadata field, which the package fetched by default. We apologise for submitting again so soon after 1.4.0, but without this release users of the default instance lose the topic domain of their search results - fixed long running searches being aborted after 10 minutes by curl's low-speed limit, regardless of the configured request timeout
- failed and incomplete searches are now reported by a warning instead of silently yielding 0 or too few hits
- clearer, correctly estimated progress output in verbose mode
- no new dependencies
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
R CMD check succeeded
- local Fedora 44 with R version 4.6.1 (2026-06-24)
- win-builder with R 4.6.1 (2026-06-24 ucrt)
- win-builder with R Under development (unstable) (2026-09-21 r90579 ucrt)
- github workflow on Ubuntu with R Under development (unstable) (2026-09-22 r90584)
- github workflow on Ubuntu with R 4.6.1
- github workflow on Ubuntu with R 4.5.3
- github workflow on macOS (ARM64) with R 4.6.1
- github workflow on Windows Server 2025 with R 4.6.1
- feature release
- changed values of two association scores, both described in NEWS.md:
logDice()is now computed as defined by Rychlý (2008), so that its values are comparable to those of other tools, and the contingency table ofll()is now scaled by the window size as a whole rather than in its row total alone collocationAnalysis()now discards collocates occurring less often than expected by chance, which its newminObservedExpectedRatioparameter controls- result caching via
cacheAsextended fromcollocationAnalysis()to the other query functions, withcacheAsInfo(),blessCacheAs()andwithCachedResults()around it - fixed collocation analysis silently dropping KWIC snippets whose markup did
not have one particular shape, and a crash in
findExample()(#14) - dropped the
PTXQCdependency, and with itrmzqc,jsonvalidateandV8, the only dependency that required alibv8installation - no new dependencies
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
R CMD check succeeded
- local Fedora 44 with R version 4.6.1 (2026-06-24)
- win-builder with R 4.6.1 (2026-06-24 ucrt)
- win-builder with R Under development (unstable) (2026-09-08 r90509 ucrt)
- github workflow on Ubuntu with R Under development (unstable) (2026-09-08 r90509)
- github workflow on Ubuntu with R 4.6.1
- github workflow on Ubuntu with R 4.5.3
- github workflow on macOS 26.6.2 (ARM64) with R 4.6.1
- github workflow on Windows Server 2022 with R 4.6.1
- gitlab pipeline on Ubuntu 24.04 (rocker/tidyverse) with R 4.6.1
- resubmission of 1.3.0, fixing the NOTE reported by the incoming pretest on
r-devel-linux-x86_64-debian-gcc and -clang:
Rd files without \usage: 'KorAPConnection-class.Rd' \arguments should not be documented without \usage.KorAPConnection()is now documented as the constructor function it is, instead of as the S4 class generator (whose formals are just...), so that its Rd file has a \usage section derived from the actual formals. No Rd file documents \arguments without \usage any more. - feature release
- new result caching option for collocation analyses
- new, experimental support for comparing collocation analyses across several virtual corpora
- no new dependencies
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
R CMD check succeeded
- local Fedora 44 with R version 4.6.1
- win-builder with R 4.6.1
- win-builder with R Under development (unstable) (2026-08-27 r90452 ucrt)
- github workflow on Ubuntu with R Under development (unstable) (2026-06-21 r90185)
- github workflow on Ubuntu with R 4.6.1
- github workflow on Ubuntu with R 4.5.3
- github workflow on macOS 26 (ARM64) with R 4.6.1
- github workflow on Windows with R 4.6.1
- bug fix and rpy2 compatibility release
- xml2 dependency added
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
R CMD check succeeded
- local Fedora 42 with R version 4.5.1
- github workflow on Windows with R 4.5.1
- github workflow on macOS 15.5 with R 4.5.1 for macOS (ARM64)
- github workflow on Ubuntu with R 4.6.0
- github workflow on Ubuntu with R 4.5.1
- github workflow on Ubuntu with R 4.4.3
- win-builder workflow using R Under development (unstable) (2025-10-08 r88906 ucrt)
- new function to fetch annotations
- improved test coverage
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
R CMD check succeeded
- local Fedora 42 with R version 4.5.1
- github workflow on Windows with R 4.5.1
- github workflow on macOS 15.5 with R 4.5.1 for macOS (ARM64)
- github workflow on Ubuntu with R 4.6.0
- github workflow on Ubuntu with R 4.5.1
- github workflow on Ubuntu with R 4.4.3
- win-builder workflow using R Under development (unstable) (2025-09-09 r88803 ucrt)
- bug fixes
- overhauled, less class centric documentation
- improved test coverage
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
R CMD check succeeded
- local Fedora 42 with R version 4.5.1
- github workflow on Windows with R 4.5.1
- github workflow on macOS 14.7.6 with R 4.5.1 for macOS (ARM64)
- github workflow on Ubuntu with R 4.6.0
- github workflow on Ubuntu with R 4.5.1
- github workflow on Ubuntu with R 4.4.3
- win-builder workflow using R Under development (unstable) (2025-02-18 r87748 ucrt)
- switched to httr2 resulting in simplified authorization
- minimum R version bumped to 4.1.0
- changes made it time for v1.0.0
- fixed compatibility with upcoming ggplot2 3.6.0
- fixed CRAN check notes on unstated dependencies in ‘demo’
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
R CMD check succeeded
- local Fedora 41 with R version 4.4.2
- local Debian 12 with R Under development (unstable) (2025-02-19 r87757)
- github workflow on Windows with R 4.4.2
- github workflow on macOS 14.7.2 with R 4.4.2 for macOS (ARM64)
- github workflow on Ubuntu with R 4.4.2
- github workflow on Ubuntu with R 4.3.3
- github workflow on Ubuntu with R Under development
- win-builder workflow using R Under development (unstable) (2025-02-18 r87748 ucrt)
- release with some new functions and internal changes that should not affect CRAN compatibility
- fixed CRAN check notes on Rd
\link{}targets without package anchors
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
R CMD check succeeded
- local Fedora 41 with R version 4.4.2
- github workflow on Windows with R 4.4.2
- github workflow on macOS 14.7.2 with R 4.4.2 for macOS (ARM64)
- github workflow on Ubuntu with R 4.4.2
- github workflow on Ubuntu with R 4.3.3
- github workflow on Ubuntu with R Under development
- win-builder workflow using R Under development (unstable) (2024-05-01 r86507 ucrt)
- release with minor fixes to ensure R 4.4.0 compatibility
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
R CMD check succeeded
- local Fedora 40 with R versions 4.3.2 and 4.4.0
- github workflow on Windows with R 4.4.0
- github workflow on macOS 14.4.1 with R 4.4.0
- github workflow on Ubuntu with R 4.3.3
- github workflow on Ubuntu with R 4.4.0
- github workflow on Ubuntu with R Under development (4.5.0)
- win-builder workflow using R Under development (unstable) (2024-05-01 r86507 ucrt)
- release with some new features and internal changes that should not affect CRAN compatibility
0 errors ✔ | 0 warnings ✔ | 0 notes ✔
R CMD check succeeded
- local Fedora 39 with R version 4.3.2
- github workflow on Windows with R 4.3.2
- github workflow on macOS with R 4.3.2
- github workflow on Ubuntu with R 4.3.2
- github workflow on Ubuntu with R 4.2.3
- github workflow on Ubuntu with R Under development (unstable) (2024-01-23 r85822)
- win-builder workflow on Windows with R-devel (2024-01-23 r85822 ucrt)
- macOS builder on macOS 13.3.1 with R 4.3.0
- new release to fix R 4.3 compatibility issues with
collocationAnalysismethod (see #12)
- Fixed CRAN policy violation (Packages which use Internet resources should fail gracefully...) pointed out in email from Prof Brian Ripley on Sat, 15 Apr 2023 16:20:19 +0100 by gracefully failing on invalid json api responses, via: https://github.com/KorAP/RKorAPClient/commit/04814f2be215f08a3777310af2202d14457c2e7c, https://github.com/KorAP/RKorAPClient/commit/f650629fa69ab10979f2ffe2652da77599caaf70
- Replaced our log.info function with log_info to avoid name clashes
- Reduced timeouts in tests to make sure they don't sum up to over 10s.
- Fixed dontrun position in misc.R example making sure that examples run in <5s.
- Wrapped the last remaining web api query example in \dontrun.
- Fixed CRAN policy violation (writing to the user's home filespace) pointed out in CRAN email from 2022-09-07 10:19 via https://github.com/KorAP/RKorAPClient/commit/35eecca9d1fd43b441692a56bbd2aea94a7c3ed9
- All CRAN requests (email from 2022-09-06 08:36) are now resolved:
- documentation completed and improved for
hc_add_onclick_korap_search,hc_freq_by_year_ci,KorAPConnectionclass - proper cache directory used in
regional.Rdemo - fixed and improved tempdir and path handling in
light-verb-construction-ca.RandrecursiveCA.Rdemos - fixed documentation for re-exported magrittr::
%>%(pipe function)
- documentation completed and improved for
- Concerning potential reasons why RKorAPClient was archived (already resolved in previous version):
- CRAN Package Check (NOTE) from 2022-08-12 https://cran-archive.r-project.org/web/checks/2022/2022-08-12_check_results_RKorAPClient.html
Check Details
Version: 0.7.2
Check: HTML version of manual
Result: NOTE
Found the following HTML validation problems:
RKorAPClient-package.html:23:4: Warning: attribute "align" not allowed for HTML5
RKorAPClient-package.html:23:4: Warning:
attribute "align" not allowed for HTML5
has been fixed by upgrading Roxygen to 7.2.1.
* I did not receive any email notification about the issue or the removal from CRAN.
* With respect to previous *problems with emails from CRAN* (`cransubmit@xmbombadil.wu.ac.at`)
in February/March 2022 our mail admin said that the CRAN emails were classified
as spam by SpamAssasin because of:
```
FROM_NOT_REPLYTO=2,
FROM_NOT_REPLYTO_SAME_DOMAIN=5
```
thus receiving a spam score > 6.31. As a hot fix we whitelisted `cransubmit@xmbombadil.wu.ac.at`
and reported the problem to the CRAN admins there. Maybe this is the reason why I didn't receive
and email notification about the NOTE.
* Could you send me the bounce message which might contain more information why I did not receive the notification mail?