Release lintr 3.3.0

[MichaelChirico]

Prepare for release:

• 3.3.0 milestone
• Update version number in DESCRIPTION and at top of NEWS
• Re-read and refine the entire NEWS for the release
• Ensure backport_linter() covers all released R versions
• Check URLs: urlchecker::url_check() or tools:::check_url_db(tools:::url_db_from_package_sources("."))
• Run the R-CMD-check GHA on all released R versions on Ubuntu, Mac, and Windows. See Check which versions of R touch the while() loop in get_source_expressions() #2501 for reference
• devtools::check(remote = TRUE, manual = TRUE, force_suggests = TRUE)
• devtools::check_win_devel() or devtools::check_win_devel(email = "your@email")
• rhub::check_for_cran() no longer works #2720
• Run revdepcheck::revdep_check(dependencies = c("Depends", "Imports"))
• Run .dev/revdep_get_repos.R and .dev/revdep_compare_releases.R

Submit to CRAN:

• usethis::use_version('minor')
• devtools::submit_cran()
• Approve email

Wait for CRAN...

• Update cran-comments.md
• Accepted 🎉
• usethis::use_github_release()
• usethis::use_dev_version()
• Toot/Tweet

[Bisaloo]

Could we also include #1805 in the 3.3.0 milestone?

It's been bothering me for a while and I believe it reduces the package usability for users that are least familiar with R package development, when they are quite likely to heavily benefit from linting.

I can either push directly to one of the open PR to get it over the finish line or start from scratch.

[MichaelChirico]

Added it to the milestone. Awesome if you want to take up the flag -- both pending PRs are pretty stale.

I'll let you decide if it's easiest to push to an existing PR or just start from scratch.

[MichaelChirico]

@Bisaloo @AshesITR @IndrajeetPatil there will be a required update of {lintr} in the coming weeks due to a breaking change coming from {testthat}.

It would be nice to try and finish these PRs in that time, anyone is available for some review bandwidth? :)

https://github.com/r-lib/lintr/pulls?q=is%3Aopen+is%3Apr+milestone%3A3.3.0