Skip to content

Release laminr 1.2.0 #222

@lazappi

Description

@lazappi

Follow the steps in this checklist to create a new {laminr} release. Update the list when you complete a step and link to any related PRs etc.

Prepare for release:

  • Check PRs are complete and merged
  • Create release/vX.Y.Z branch and open draft PR
  • Check if any deprecation processes should be advanced, as described in Gradual deprecation
  • Check current CRAN check results
  • Run checks and fix issues
    • urlchecker::url_check()
    • devtools::check(remote = TRUE, manual = TRUE)
    • devtools::check_win_devel()
    • rhub::rhub_check(platforms = rhub::rhub_platforms()$name) (optional, it is expected some platforms will fail, check the output for why)
  • Update cran-comments.md (usethis::use_cran_comments())
  • Bump version on release branch usethis::use_version('minor')
    • Update version in CHANGELOG
  • Set release PR ready for review
  • Review and approve release PR (but don't merge!)
  • Open a PR to update the main changelog

Submit to CRAN:

  • Submit to CRAN devtools::submit_cran()
  • Approve email
  • Address any comments and resubmit if needed

Wait for CRAN...

  • Accepted 🎉
  • Merge the release PR
  • Create a GitHub release usethis::use_github_release()
  • Bump devel version usethis::use_dev_version(push = TRUE) on main branch
  • Merge the main changelog PR
  • Close this issue

Metadata

Metadata

Assignees

No one assigned

    Labels

    🔖 releaseIssues for creating a new release

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions