-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
v1.7.5.1 release candidate #3910
Conversation
90f0bc5
to
2f434ff
Compare
Note that 837307f has a false positive error because the routine is being overly opinionated about using 837307f was submitted to CRAN and is awaiting response |
Hi, do you have any updates on this? I have a package that calls isTruthy and that will be removed from CRAN tomorrow, but if this goes through I won't need to change anything (possibly just re-submit if they don't accept the new shiny version on time). Thanks, |
We submitted it to CRAN a week ago, and their automatic reverse dependency checks had an error in the vignette for a package. I think that error had nothing to do with Shiny, and I emailed CRAN twice about it, but still haven't heard back from them. |
This is the relevant part of the email from CRAN:
The error is apparently from this code block: |
@wch I installed r-devel (latest available via However! I noticed that the functions in that vignette collect data from remote online resources. By disconnecting my computer from the internet, I was able to reproduce the exact error, and the output gives a little more context:
|
@rhenkin Shiny 1.7.5.1 is on CRAN now, so you should be good to go. |
@wch this PR is mergeable now -- I think we'll want to do a merge commit (not squash+merge) so that the v1.7.5.1 tag (837307f) gets properly included into Also, it appears the routine failure in 481a692 is, again, due to shiny-workflows wanting to use the |
Yes, I think we're good to merge this now. One thing that I'm a little confused by is that the Files Changed view in this PR only shows that the NEWS.md file has changed. Is that because main also contained the fix, and main was merged in to this branch? |
Yep, this PR started by branching off of the |
Closes #3911.
This patch release branches off the
v1.7.5
tag to only include #3908 (because CRAN has requested a fix by Oct 14 and we're not in a position to release the rest of what's onmain
).