Close #123 release 02

[jwang-lilly]

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral family codebase remains robust and consistent.

Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

• Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
• Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
• Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
• If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
• Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
• Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
• Address any updates needed for vignettes and/or templates
• Update NEWS.md under the header # admiral<ext> (development version) if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
• Build site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the Reference page.
• Address or fix all lintr warnings and errors - lintr::lint_package()
• Run R CMD check locally and address all errors and warnings - devtools::check()
• Link the issue in the Development Section on the right hand side.
• Address all merge conflicts and resolve appropriately
• Pat yourself on the back for a job well done! Much love to your accomplishment!

[github-actions]

Package	Line Rate	Health
admiralneuro	100%	✔
Summary	100% (64 / 64)	✔

[Copilot]

Pull request overview

This pull request prepares the admiralneuro package for its second CRAN release (version 0.2.1). The changes update package metadata and dependencies to reflect the new release status.

Changes:

• Updated version number from 0.1.0.9014 to 0.2.1
• Updated minimum dependency versions for admiral, admiraldev, and dplyr
• Added bug reporting URL to package documentation

Reviewed changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
DESCRIPTION	Updated package version to 0.2.1, added BugReports URL, and updated minimum versions for admiral, admiraldev, and dplyr dependencies
NEWS.md	Removed "(development version)" suffix from header to indicate release status
cran-comments.md	Updated release description from "first release" to "2nd release"
man/admiralneuro-package.Rd	Added bug reporting URL to package documentation
.Rbuildignore	Added doc directory to build ignore list

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Fanny-Gautier]

Version number to implement in NEWS.md (and to correct in DESCRIPTION?).

[Fanny-Gautier]

Why is it 0.2.1 while first release was 0.1.0? I believe it should be 0.2.0.

[jwang-lilly]

@Fanny-Gautier, I sent out 0.2.0 first but forgot to remove (development version) from the NEWS.md. It was too late to edit as admiralneuro hit CRAN right away, within an hour of submission. Therefore, I had to bump up to 0.2.1.

[Fanny-Gautier]

Hi @jwang-lilly ,
Could you please clarify the status of {admiralneuro}? It appears to be available on CRAN as version 0.2.1 since 2026‑02‑04, but the website is still showing the older version 0.1.0 because the PR has not yet been merged into the main branch.

Could you also confirm which version number will be (or is currently) used so that I can correctly reference it in the {pharmaverseadam} package for the addition of {admiralneuro} data?

Thank you.

[Fanny-Gautier]

The title of the PR should start with [skip vbump]; otherwise, the version number will continue incrementing when the PR is merged into main.

Also, to avoid last‑minute errors, it is preferable to have the package reviewed and approved before submitting it to CRAN. The merge should be done only after you receive the email confirming that it is on its way to CRAN.