Recurrent: Release new version of SIMplyBee

[gregorgorjanc]

TODO:

A couple of points that we should do when releasing a new version:

Lots of good tips at https://devtools.r-lib.org/index.html and https://usethis.r-lib.org/reference/use_release_issue.html

• Revise the opened issue links in the code Recurrent: Revise the opened issue links in the code #458
• Use lintr and styler to check and format the code Make use of lintr and/or styler automatic (for every commit) #309 ???
• Update documentation devtools::document()
• Run tests devtools::test()
• Are many tests missing devtools::test_coverage()
• Check the package (R CMD check) devtools::check()
• Update the NEWS.md file and provide information, add links or IDs of issues/pull requests/commits Recurrent: Update NEWS file to summarise key changes between versions  #522
• Merge devel into main
• Release to CRAN: devtools::release()
• Address any CRAN comments
• Commit latest changes
• Tag the version using git tag -a "vx.y.z" -m "Version x.y.z"; git push origin vx.y.z (see docs at https://git-scm.com/book/en/v2/Git-Basics-Tagging)

[LStrachan]

This links to #522 to Update the NEWs file when updating package