better

Author: beabock

NEWS.md

@@ -1,4 +1,4 @@
-# CodeCarbonR (development version)
+# CodeCarbonR 0.0.0.9000
 
 ## New features
 

RELEASING.md

@@ -81,9 +81,18 @@ only pursue this if you specifically want CRAN's discoverability/CI
 guarantees on top. Frictions specific to this package:
 
 - **`R CMD check --as-cran` must stay clean.** Locally this package
-  currently passes with 0 errors/warnings/notes (validated 2026-08-04);
-  re-run with `--as-cran` specifically before submitting, since it enables
-  a few extra checks beyond a plain `R CMD check`.
+  currently passes with 0 errors, 0 warnings, and 1 NOTE (validated
+  2026-08-04); re-run with `--as-cran` specifically before submitting,
+  since it enables a few extra checks beyond a plain `R CMD check`. The
+  one NOTE is `CITATION.cff` living at the repo root ("Found the following
+  CITATION file in a non-standard place... Most likely 'inst/CITATION'
+  should be used instead") -- unavoidable while keeping both: `CITATION.cff`
+  has to live at the repo root for GitHub's "Cite this repository" button
+  and Zenodo to find it, and `inst/CITATION` (already added) is what makes
+  `citation("CodeCarbonR")` work from R. If a CRAN maintainer objects to
+  the NOTE, the fix is to drop `CITATION.cff` from CRAN's submission
+  tarball via `.Rbuildignore` -- but keep it in the GitHub repo itself so
+  Zenodo archiving still works.
 - **`setup_carbon_tracker()` installs software and touches the network.**
   CRAN's policy forbids examples/tests/vignettes that install software,
   write outside `tempdir()`, or require network access during