From 6bce014dcde3c91738f39de3226f743ef515fdc0 Mon Sep 17 00:00:00 2001 From: Matthijs Berends Date: Mon, 16 Nov 2026 12:31:52 +0100 Subject: [PATCH] (v3.1.0.9026) Add the release reference for the AMR for R Assistant to the release checklist --- DESCRIPTION | 2 +- NEWS.md | 2 +- release.md | 1 + 3 files changed, 3 insertions(+), 2 deletions(-) diff --git a/DESCRIPTION b/DESCRIPTION index 1cbdffac7..431c9ca45 100644 --- a/DESCRIPTION +++ b/DESCRIPTION @@ -1,5 +1,5 @@ Package: AMR -Version: 3.1.0.9025 +Version: 3.1.0.9026 Date: 2026-11-16 Title: Antimicrobial Resistance Data Analysis Description: Functions to simplify and standardise antimicrobial resistance (AMR) diff --git a/NEWS.md b/NEWS.md index 2beae2914..071fe83fc 100644 --- a/NEWS.md +++ b/NEWS.md @@ -1,4 +1,4 @@ -# AMR 3.1.0.9025 +# AMR 3.1.0.9026 This version fixes a critical bug in WISCA that biased all coverage estimates of `wisca()` and `antibiogram(..., wisca = TRUE)` downwards since AMR 3.0.0. Users are strongly advised to re-run their WISCA analyses. diff --git a/release.md b/release.md index 2eeea14a6..9e9b90e60 100644 --- a/release.md +++ b/release.md @@ -48,6 +48,7 @@ The pre-commit hook in `.github/prehooks/` sets the version to `X.Y.Z.9NNN` and ``` - [ ] `git fetch --tags` and check that `vX.Y.Z` points at the release commit +- [ ] Check that the workflow *Publish release reference* (`.github/workflows/website-release.yaml`), which publishing the GitHub release starts, succeeded. It publishes the reference of this version as Markdown at `https://amr-for-r.org/release/X.Y.Z/` for the AMR for R Assistant (https://amr-for-r.org/articles/chat.html), and adds the version to `https://amr-for-r.org/release/llms.txt`. To publish a version manually, start the workflow from the Actions tab with the tag as input, one version at a time: it shares the concurrency group `gh-pages` with the website workflow, and GitHub keeps only one waiting run per group, so a second waiting run cancels the first - [ ] Run `source("data-raw/microorganisms_files/build_mo_code_registry.R")` from the root of the repository (takes a few minutes; the tag must exist), then review the diff of `mo_code_registry.csv`: only new codes may be added, existing codes may only get a later `last_release`, and renamed codes must have their old name in `previous_names` (see `data-raw/microorganisms_files/README.md`) - [ ] `.github/ISSUE_TEMPLATE/1-bug-report.yml`: set the versions to `Latest CRAN version (X.Y.Z)` and `One of the latest GitHub versions (X.Y.Z.9xxx)` - [ ] `NEWS.md`: put a new line 1 `# AMR X.Y.Z.9001`, followed by an empty line, above `# AMR X.Y.Z`; without this, the hook overwrites the heading of the released section