Open bms63 opened 2 hours ago
Hello @bms63! As far as I know this has to be done manually after verifying that CRAN submission was successful and the changes are merged to the main.
You can check out the release process we follow in the teal package outlined in the issue template's release section.
I think it's not a big deal to have tag and release automation for this package. It only becomes important when you have some workflow that depends on observing the tag event to do some internal release like what we do for the teal package. I think we can just outline the CRAN release process in an issue template so we can make sure we do not forget this step.
@averissimo do you have something to add?
oooh i like this!!! Thanks @vedhav you are always amazing!
@vedhav and @averissimo
Is there a way to automate a release? I forgot to do the release for 0.4.1 onto GitHub. Not a huge deal...but was wondering if there was some way to not have to do this manually.
CRAN is the only issue - sometimes I don't know if the package will pass or not and can do it immediately once I submit to CRAN! urgh!