340/cran release/update version

[kristinawlai]

Updating version number, CRAN comments, and any issues ahead of submission

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Files with missing lines	Coverage Δ
R/graph.decay.curves.R	80.00% <ø> (ø)
R/sim.cs.R	0.00% <ø> (ø)

[github-actions]

📕 Preview documentation for this PR has been cleaned up.

[kristinawlai]

@d-morrison all checks pass, but I'm getting the following notes in check_win_devel(). The first one seems just informational and I added a note to cran_comments.Rd about the spelling and previously archived version. However, I'm not sure what to do with the second one. I see a {} in sim.cs.Rd, but I can't figure out where it is coming from in sim.cs.R.

*** checking CRAN incoming feasibility ... NOTE**
Maintainer: 'Kristina Lai [email protected]'

New submission

Package was archived on CRAN

Possibly misspelled words in DESCRIPTION:
Serological (3:40)
seroconversions (15:5)
seroincidence (16:28)

Unknown, possibly misspelled, fields in DESCRIPTION:
'Remotes'

CRAN repository db overrides:
X-CRAN-Comment: Archived on 2024-11-26 for policy violation.

On Internet access.

Suggests or Enhances not in mainstream repositories:
devtag

*** checking HTML version of manual ... NOTE**
Found the following HTML validation problems:
sim.cs.html:161:1 (sim.cs.Rd:76): Warning: trimming empty

[d-morrison]

see question below and notes in chat

[d-morrison]

Congrats on getting us back on CRAN! I added a couple more commits to implement the post-acceptance steps from https://r-pkgs.org/release.html#sec-release-post-acceptance, since those instructions don't quite map onto our current workflow.