Release prep for 0.3.0: refresh stale release docs#15
Merged
Conversation
cran-comments rewritten for 0.3.0 (was still describing 0.2.0): R 4.6.0 test environment, the full additive changelog, and an explicit update-frequency note (four weeks since 0.2.0, driven by the downstream mx.client E2EE layer; batched into one release). README: drop the which-version-is-on-CRAN assertion (stale inside a tarball), correct the canonical-JSON assertion count to 107. DESCRIPTION Date refreshed. Also harden mx_upload(): tolerate non-JSON error bodies (proxy/HTML) so the status check raises mx_error_* instead of a jsonlite parse error.
Run on windows-hr: R CMD check --as-cran --no-manual, tests OK, 1 environmental NOTE (offline world-clock timestamp verification).
Run on windows-hr alongside the earlier 4.5.1 pass; the newer versions produce zero NOTEs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Codex's pre-submission review caught four stale-doc items plus one hardening nit; all fixed:
cran-comments.mdrewritten for 0.3.0 (was 0.2.0 content, R 4.5.3) — includes the update-frequency justification for the 4-week gap.mx_upload()tolerates non-JSON error bodies, so failures raisemx_error_*instead of a jsonlite parse error.Suite 183/0, check 0/0/0. This is the submission candidate;
check_win_devel()should be re-run for 0.3.0 beforesubmit_cran()so the win-builder line in cran-comments is current.