Skip to content

Prepare chat.api 0.2.0 for CRAN - #29

Merged
TroyHernandez merged 6 commits into
mainfrom
cran-0.2.0-prep
Nov 10, 2026
Merged

TroyHernandez merged 6 commits into
mainfrom
cran-0.2.0-prep

Conversation

@TroyHernandez

Copy link
Copy Markdown
Contributor

Prepares the 0.2.0 CRAN update.

Changes

  • Remove the call surface: chat_call_join(), chat_call_leave(), chat_call_media(), chat_call_updates(), the calls capability, $calls from chat_poll(), and the .call seam of chat_matrix(). mx.client 0.3.0 ships without mx_call_*. None of this reached CRAN; the code is kept on livekitr-calls.
  • Raise the Suggests floors to mx.client (>= 0.3.0) and mx.crypto (>= 0.3.0), and name those versions in the install messages.
  • Qualify setNames() in matrix_decrypted_attachments() (check NOTE).
  • Guard the encrypted markdown edit test, which errored where mx.client is absent.
  • Bump to 0.2.0 and merge the development NEWS entries into one section.
  • Rewrite cran-comments.md for the update.
  • CI: take mx.api and mx.crypto from CRAN; pin mx.client to its 0.3.0 release commit until CRAN carries it.
  • tools/check_tarball.sh allows NEWS.md.

Verification

R CMD check --as-cran --run-donttest, Ubuntu 24.04.5, R 4.6.1, isolated library:

Library Status Assertions
mx.api 0.4.0, mx.crypto 0.3.0, mx.client 0.3.0 OK 1,476
mx.client and mx.crypto absent OK 1,122

Installed tests with an empty HOME left no files under it. CRAN lists no reverse dependencies.

Before submission

  • mx.client 0.3.0 must be on CRAN.
  • Add win-builder results to cran-comments.md.

mx.client 0.3.0 ships without mx_call_join, mx_call_handle, and
mx_call_leave, so chat_call_join(), chat_call_leave(), chat_call_media(),
and chat_call_updates() have nothing to drive. They go, along with the
calls capability flag, the calls element of chat_poll()'s result, the
.call testing seam, and the call diagnostics in the crypto path. None of
it reached CRAN.

The code is kept on the livekitr-calls branch until livekitr is on CRAN.
Encrypted edits and the guard that keeps bodiless decrypted events out
of the message list stay.
The Suggests floors named development versions (mx.client 0.2.1.4,
mx.crypto 0.2.2.2) that CRAN never carried. Both become 0.3.0, the
releases that include encrypted attachment support, and the messages
that tell a user what to install name the same versions.
matrix_decrypted_attachments() called setNames() without its namespace,
which R CMD check reports as an undefined global. The encrypted markdown
edit test called mx.client's renderer unguarded, so the tests errored
where mx.client is absent. tools/check_tarball.sh now allows NEWS.md,
which the package ships.
CRAN carries mx.api 0.4.0 and mx.crypto 0.3.0, so the drat and the
pinned mx.crypto commit go. mx.client 0.3.0 is not on CRAN yet; it stays
pinned to its release commit until it is.
@TroyHernandez
TroyHernandez merged commit 1083d93 into main Nov 10, 2026
2 checks passed
@TroyHernandez
TroyHernandez deleted the cran-0.2.0-prep branch November 10, 2026 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant