Prepare chat.api 0.1.0 for CRAN - #24
Merged
Merged
Conversation
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
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.
Prepare the first CRAN release as 0.1.0, with published Matrix dependency
floors, runnable examples, and portable package tests. Consolidate the
prerelease NEWS entries under 0.1.0 and record submission checks in
cran-comments.md.
CI installs every suggested adapter package from CRAN, builds the Matrix
packages from published sources to avoid binary lag, verifies their versions,
and fails on check warnings. Linux installs the libcurl headers needed by its
source dependencies. Tests use temporary user directories and handle Windows
permissions and normalized upload paths on macOS.
Validation:
New submission NOTE; 1,414 assertions passed with all suggested packages.
submission NOTE; all 1,413 Windows assertions passed.
both pass with Status: OK, using mx.api 0.3.1, mx.client 0.2.1, and
mx.crypto 0.2.2.
CRAN submission remains pending a clean Windows R-release recheck. Its last
run passed 1,403 assertions but warned about mx.crypto::mxc_signing_key_public;
the builder's older mx.crypto skipped the 10 newer crypto assertions.
The required export is present in CRAN source mx.crypto 0.2.2. The final
archive includes the normalized upload-path test fix and needs a Windows
R-release check before Troy submits it to CRAN.