Yes good points. It wouldn’t break the old code but (perhaps worse) it would redefine what the output value means. As I write this I think it occurs to me to add another item in the output list with the new value which would mean a user to keep using it as before as well

What's the best way to go about this? I don't want to break old code, but this is based on updated best practice.

Is releasing it as a new version with an update in the NEWS enough?

@njtierney.bsky.social @bharrap.bsky.social ...

4/ lastly, ropensci's very own pkgcheck action.

This one is really interesting as it gives you a summary of points you've either hit or missed and summarises them in a new issue in your repo. Subsequent pushes show up as comments in the same issue thread.

docs.ropensci.org/pkgcheck/ind...

3/ pkgdown workflow

Not related to the ropensci submission, but very handy if you have a pkgdown website.

I adapted from the examples here github.com/r-lib/action.... It is great knowing the website is up to date with changes I've pushed and I didn't have to separately re-publish the website.

2/ I also set up an action to access my code coverage and report it on the readme. It's not as high as I'd like yet, but it's getting there!

To get this to work I first had to link the repo on codecov.io.

github.com/codecov/code...

1/ continuous integration

Compared to the last time I set up continuous integration, things are SO EASY now. I used the following:

github.com/r-lib/action...