Document GitHub 0.2.2 publication

README.md

@@ -83,9 +83,9 @@ also apply when Zenodo captures a GitHub release.
 
 ## Development status
 
-Version 0.2.2 is available on CRAN. The latest published GitHub release is
-0.2.1; the 0.2.2 GitHub release is still being prepared. All require
-R 4.2 or newer. The 0.2.2 update makes search initialization explicit and
+Version 0.2.2 is available on CRAN and is the latest published
+[GitHub release](https://github.com/jakeberv/bifrost/releases/tag/v0.2.2).
+It requires R 4.2 or newer. The 0.2.2 update makes search initialization explicit and
 corrects progress-related random-stream and numerical-thread handling, with
 console-display refinements. These changes can affect results relative to
 earlier releases; see the initialization and reproducibility notes in NEWS.

tools/releases/0.2.2.md

@@ -1,7 +1,7 @@
-# bifrost 0.2.2 publication record and GitHub preparation
+# bifrost 0.2.2 publication record
 
-CRAN published 0.2.2 on October 17, 2026. The GitHub release remains pending;
-its draft body and remaining steps are recorded below. This file is excluded
+CRAN and GitHub published 0.2.2 on October 17, 2026. Release evidence and
+the published GitHub notes are recorded below. This file is excluded
 from package and GitHub source archives by the existing `tools/` rules.
 
 ## CRAN publication
@@ -14,13 +14,30 @@ The maintainer submitted a fresh rebuild, so this published archive is separate
 from the locally checked archive recorded below. `cran-comments.md` retains
 the submitted comments as a historical record.
 
-The latest published GitHub release remains v0.2.1. No v0.2.2 GitHub release
-or Zenodo version archive is claimed here.
+## GitHub and Zenodo publication
 
-## Draft GitHub release body
+[GitHub v0.2.2](https://github.com/jakeberv/bifrost/releases/tag/v0.2.2) was
+published at `2026-10-17 07:35:33 UTC` (3:35 a.m. EDT) from commit
+`f627fc27857273f52c4537a9d43d335ba4599f78`. The tag resolves to that exact commit.
+All five R CMD checks, coverage, both parallel smoke jobs, pkgdown build and
+deployment, and the advisory audit succeeded. Actual coverage was exactly 100%
+with zero uncovered rows; Windows reported `Status: OK` and clean temporary files.
+The audit's known console-rendering and documentation findings remain advisory;
+missing method examples are tracked in #253. Issue #231 remains deferred.
 
-Copy the text between the markers into the release description only after
-the final checks and publication approval.
+The downloaded GitHub tar archive matched the preflight export file-for-file;
+its SHA-256 is `e702bb14633896b63a1ece9e8f28752f5c8464708aae323269970beafd1addf1`.
+The package code, tests, help files, installed resources, and namespace match
+the final locally checked package. Later changes were release documentation.
+
+Zenodo archived v0.2.2 under the existing
+[concept DOI](https://doi.org/10.5281/zenodo.23268805). For release provenance,
+the version record is `23432953` (DOI `10.5281/zenodo.23432953`); its ZIP MD5 is
+`f5cab34d656f417ad2c919a4daec8afc`. Both the checksum and extracted file contents
+were verified against the GitHub release. Evidence is preserved locally in
+`output/github-release-0.2.2/`.
+
+## Published GitHub release body
 
 <!-- release-body:start -->
 This update makes search initialization explicit and corrects progress-related
@@ -53,10 +70,10 @@ is deferred ([#231](https://github.com/jakeberv/bifrost/issues/231)).
 
 See the [changelog](https://jakeberv.com/bifrost/news/index.html) and
 [release-status page](https://jakeberv.com/bifrost/articles/development-status.html)
-for details. GitHub publication does not update CRAN automatically.
+for details. Version 0.2.2 is also [available on CRAN](https://CRAN.R-project.org/package=bifrost).
 <!-- release-body:end -->
 
-## Remaining publication checklist
+## Publication checklist
 
 - [x] Preparation PR #250 merged as
   `30e58e82af46f6f0ef35ebf69f3a563f8b459774`; all 11 post-merge jobs passed,
@@ -88,14 +105,12 @@ for details. GitHub publication does not update CRAN automatically.
 - [x] Retain the documented deferral of #231; this preparation does not fix it.
   Keep the initialization/convergence follow-up (#242) and RRphylo dependency
   work (#247) separate from this release.
-- [ ] Review the remaining advisory findings and final check notes before
-  GitHub publication. The advisory job's success is not a clean-audit claim.
-- [ ] Obtain explicit approval before creating a tag or publishing the
-  GitHub release. CRAN publication does not authorize either action.
-- [ ] At approved GitHub publication, select and verify the commit for `v0.2.2`
-  and use the release body above. Verify the GitHub archive and any Zenodo record after
-  publication; never describe an unverified archive/DOI as available.
-- [ ] Apply the GitHub publication-time documentation edits below through a PR.
+- [x] Review the advisory findings and final check notes before publication.
+  The advisory job's success is not a clean-audit claim.
+- [x] The maintainer explicitly authorized publication of GitHub v0.2.2.
+- [x] Publish the verified commit and release body; verify the GitHub archive
+  and Zenodo version archive as recorded above.
+- [ ] Merge the follow-up documentation PR reflecting GitHub publication.
 
 ## Latest check: PR #255 author-metadata correction
 
@@ -215,34 +230,9 @@ These local artifacts are not committed or published. V8 was subsequently
 reinstalled in the maintainer's user library as a separate authorized
 environment repair; it did not change this archive or the check results.
 
-## GitHub publication-time documentation edits (staged text, not applied)
-
-After GitHub 0.2.2 is published, replace the opening two sentences under
-`README.md`'s **Development status** with:
-
-> Version 0.2.2 is the latest published GitHub release; CRAN currently distributes
-> 0.2.2. All require R 4.2 or newer.
-
-Recheck the CRAN version at that time. Leave the remaining initialization and
-reproducibility text in place.
-
-In `vignettes/articles/development-status.Rmd`:
-
-- Change the description and introductory paragraph from release preparation
-  to published GitHub 0.2.2 availability.
-- Replace the published GitHub 0.2.1 row and planned 0.2.2 row with this row:
-
-  | Distribution | Version | Installation | Best for |
-  |---|---:|---|---|
-  | [GitHub](https://github.com/jakeberv/bifrost/releases/tag/v0.2.2), published release | 0.2.2 | `remotes::install_github("jakeberv/bifrost@v0.2.2")` | Explicit initialization and reproducibility corrections |
-
-- Replace the paragraph saying the tag is unavailable with:
-
-  > Versions 0.2.0, 0.2.1, and 0.2.2 require R 4.2 or newer. Version 0.2.2 is
-  > published on GitHub. Publishing a GitHub release does not change the version
-  > installed from CRAN.
-
-- Retain the historical 0.2.1 and 0.2.0 change summaries and current caveats.
+## Post-publication documentation
 
-CRAN submission and publication are complete. Preserve `cran-comments.md`
-as the submitted record; do not resubmit as part of GitHub release preparation.
+The follow-up documentation PR updates README and the release-status article
+to show 0.2.2 on both CRAN and GitHub. Historical release summaries and the
+#231 caveat remain intact. Preserve `cran-comments.md` as the submitted record;
+no CRAN resubmission is needed for these repository documentation updates.

vignettes/articles/development-status.Rmd

@@ -1,24 +1,23 @@
 ---
 title: "Release Status"
-description: "CRAN availability and GitHub release preparation for bifrost 0.2.2."
+description: "CRAN and GitHub availability for bifrost 0.2.2."
 ---
 
-This page describes `bifrost` 0.2.2, published on CRAN on October 17, 2026,
-the planned 0.2.2 GitHub release, and the relationship between package source
-archives and the fuller documentation maintained in the repository.
+This page describes `bifrost` 0.2.2, published on CRAN and GitHub on
+October 17, 2026, and the relationship between package source archives
+and the fuller documentation maintained in the repository.
 
 ## At a glance
 
 | Distribution | Version | Installation | Best for |
 |---|---:|---|---|
 | [CRAN](https://CRAN.R-project.org/package=bifrost) | 0.2.2 | `install.packages("bifrost")` | Current published CRAN release |
-| [GitHub](https://github.com/jakeberv/bifrost/releases/tag/v0.2.1), published release | 0.2.1 | `remotes::install_github("jakeberv/bifrost@v0.2.1")` | Citation, documentation, and archive updates |
-| [GitHub](https://github.com/jakeberv/bifrost), planned release | 0.2.2 | `remotes::install_github("jakeberv/bifrost@v0.2.2")`, after the tag is published | Explicit initialization and reproducibility corrections |
+| [GitHub](https://github.com/jakeberv/bifrost/releases/tag/v0.2.2), published release | 0.2.2 | `remotes::install_github("jakeberv/bifrost@v0.2.2")` | Explicit initialization and reproducibility corrections |
 | [GitHub](https://github.com/jakeberv/bifrost), development source | Version on `main` | `remotes::install_github("jakeberv/bifrost")` | Latest merged development source |
 
 Versions 0.2.0, 0.2.1, and 0.2.2 require R 4.2 or newer. Version 0.2.2 is
-available on CRAN; its GitHub release and tag are still pending. CRAN and
-GitHub releases are published separately.
+available on both CRAN and GitHub. CRAN and GitHub releases are published
+separately.
 
 ## What 0.2.2 adds