Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maybe fix latest cran warnings #203

Merged
merged 2 commits into from
Nov 15, 2022
Merged

Maybe fix latest cran warnings #203

merged 2 commits into from
Nov 15, 2022

Conversation

paleolimbot
Copy link
Collaborator

@paleolimbot paleolimbot commented Nov 15, 2022

Fixes #202.

@codecov-commenter
Copy link

Codecov Report

Merging #203 (d9f2d2b) into main (865f8f0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #203   +/-   ##
=======================================
  Coverage   94.16%   94.16%           
=======================================
  Files          46       46           
  Lines        3495     3495           
=======================================
  Hits         3291     3291           
  Misses        204      204           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@edzer
Copy link
Member

edzer commented Nov 15, 2022

Shall I try a CRAN submission?

@edzer edzer merged commit 090f4f0 into main Nov 15, 2022
@paleolimbot
Copy link
Collaborator Author

Let me run through the release checklist! I'll do use_release_issue() this evening and plug through some of the checks.

@paleolimbot paleolimbot deleted the cran-fixes-latest branch November 16, 2022 17:18
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.

new CRAN message
3 participants