From bioconductor.org, Bioconductor package indexes and runs in R 4.6.1, 17 November 2026 · Updated
Bioconductor 3.24: "not available for Bioconductor version '3.24'", and how to check and keep a package
Bioconductor plans to release version 3.24 on Wednesday 25 November 2026, for R 4.6. After that, BiocManager::install() in an R 4.6 library that is not yet on a Bioconductor version installs from 3.24, and a package that 3.24 does not have is not installed: R prints the message below. That affects a new laptop, a CI job, a Docker build or a course image that installs Bioconductor packages from scratch on R 4.6. A library that is already on 3.23 is a different case: see "An existing 3.23 library". The R lines under "Check your library" list the Bioconductor packages in your library that the 3.24 index does not have today.
The message
We could not run the real 3.24 release, because it is not out. We ran R 4.6.1 with BiocManager 1.30.27 on Linux (locale en_US.UTF-8), with a copy of Bioconductor's version file edited so that 3.24 is the release. In a new library, BiocManager:: printed this on 17 November. We removed the download, build and package-update lines and one extra warning that our edited file caused. Depending on how CRAN is set in your R, a note that starts 'getOption("repos")' replaces Bioconductor standard repositories may come first:
Bioconductor version 3.24 (BiocManager 1.30.27), R 4.6.1 (2026-06-24)
Installing package(s) 'BiocVersion', 'decoupleR'
[download, build and package-update lines removed]
Warning message:
package ‘decoupleR’ is not available for Bioconductor version '3.24'
A version of this package for your version of R might be available elsewhere,
see the ideas at
https://cran.r-project.org/doc/manuals/r-patched/R-admin.html#Installing-packagesR prints the package name with curly quotes, ‘decoupleR’, and the version with straight quotes. The install did put one package in the library, BiocVersion 3.24.0, before it printed the warning. It did not install decoupleR.
The warning does not stop a script
It is a warning, not an error. We ran the shell line below in a new library, under the same edited file:
Rscript -e 'BiocManager::install("decoupleR")'; echo "exit=$?"It printed the message above and exit=0. Then Rscript -e 'library(decoupleR)' printed Error in library(decoupleR) : there is no package called ‘decoupleR’ and exited 1. So a Docker build step or a CI step that runs only the install passes, and the failure comes at the first library() call. In the same library BiocManager:: installed, so only the missing package is affected. We ran this on Linux only.
Which packages are missing
Bioconductor's package indexes are what BiocManager reads. Until 25 November the 3.24 index is the development version. We compared the 3.23 index with it on 21 November 2026, after the 20 November deadline for packages to pass build and check. The counts can still move until the release, so run the check below instead of trusting them:
- 65 packages that are in 3.23 are not in the 3.24 index.
- Bioconductor's removed-packages page lists 53 packages as removed with Bioconductor 3.24. 23 of the 65 are on that list.
- The other 42 are not on that list. They include decoupleR, dorothea and progeny.
- Bioconductor's package list for its development branch (its manifest), which becomes 3.24, includes 38 of those 42, decoupleR, dorothea and progeny among them. So these packages are still on Bioconductor's list and not in the index that
BiocManagerreads. - The schedule lists 23 November as the last day to commit changes to the 3.24 branch. Run the check again after the release.
Windows and macOS read other indexes. Of the 42, 14 are in the 3.24 Windows binary index for R 4.6. 14 are in each of the two macOS ones (Intel and Apple silicon), the same 14 in both. Each list has one package the other lacks: pathMED is only in the Windows one, SVMDO only in the macOS ones. decoupleR is in none of them. 10 of the 14 in the Windows list, and 9 of the 14 in each macOS list, name a dependency (decoupleR, dorothea, BiocSet, ballgown or mltools) that no 3.24 index and not CRAN has, so they would not install from 3.24 either. We read the indexes' Depends, Imports and LinkingTo fields; we did not install any of the 14.
11 packages that are in the 3.24 index name a dependency that is in neither the 3.24 indexes nor CRAN's package list: nine RTCGA.* packages (they need RTCGA), scRecover (needs preseqR) and synergyfinder (needs SpatialExtremes). We read the Depends, Imports and LinkingTo fields; we did not try to install them.
decoupleR, on 21 November
- Its 3.24 build report (generated 20 November, snapshot of 19 November) shows OK for install and build and ERROR for check on its one listed Linux builder. Its last commit on Bioconductor's development branch is dated 28 April 2026.
- The R repository on GitHub (saezlab/decoupleR) merged a pull request on 16 December 2025, "Close and redirect issues to scverse repo". Its description reads: "Added an automatic reply to ask people to open issues in the scverse repository instead of this one since is no longer maintained." The repository has no GitHub releases.
- The same report lists six software packages that depend on decoupleR: cosmosR, easier, GSABenchmark, pathMED, progeny and SmartPhos. Each passed install, build and check, and each carries the mark "NO, package depends on 'decoupleR' which is not available" (for easier: "… on 'progeny' …"). None of the six is in the 3.24 index.
- dorothea also imports decoupleR. It is an experiment-data package with its own report (generated 19 November), which shows OK for install and build and ERROR for check; we did not read why.
- decoupleR is on neither of the removed-packages page's 3.24 lists, and it is not in the 3.24 index. No page we read says whether 3.24 will include it. We do not know.
Check your library
Run this in R 4.6, in the library you want to check, with BiocManager installed. It lists the installed Bioconductor packages that are not in the 3.24 index:
ip <- installed.packages(fields = "git_url")
bioc <- rownames(ip)[grepl("git.bioconductor.org",
ip[, "git_url"], fixed = TRUE)]
nxt <- rownames(available.packages(repos =
BiocManager::repositories(version = "3.24")))
sort(setdiff(bioc, nxt))In a new library with BiocGenerics and decoupleR it printed [1] "decoupleR". In a new library with only BiocGenerics it printed character(0). An empty result means nothing installed there is missing today. The lines find Bioconductor packages by the git_url field that Bioconductor's builds add. They do not check dependencies. We ran them on Linux only.
An existing 3.23 library
We made a library on 3.23 (BiocVersion 3.23.1 and BiocGenerics), then switched to the edited version file. What we saw:
library(BiocManager)printed (R wraps it after '3.24' at the default width):Bioconductor version '3.23' is out-of-date; the current release version '3.24' is available with R version '4.6'; see https://bioconductor.org/install BiocManager::version()still printed3.23.BiocManager::printedinstall( "decoupleR") Bioconductor version 3.23and installed decoupleR with its dependencies from the 3.23 index.BiocManager::moved the library: it installed BiocVersion 3.24.0, then newer BiocGenerics and BiocParallel, and in our image the 11 CRAN packages named below. Afterwardsinstall( version = "3.24", ask = FALSE) BiocManager::version()printed3.24, decoupleR was still installed andlibrary(decoupleR)worked. We got the same result when decoupleR was installed before the switch.
So in our runs a library that stayed on 3.23 still installed from 3.23, and moving it to 3.24 did not remove an installed package that 3.24 lacks. We did not test what a later BiocManager::install() of that package or its dependents does after the move, or a library with many packages.
Keep the package: move the library to 3.23 first
In a new library, the one-line pin does not work. In a library that sees 3.24 as the release, this stopped and installed nothing. The number of packages depends on what is in your R library; ours said 13:
BiocManager::install("decoupleR", version = "3.23")Error: To use Bioconductor version '3.23', first downgrade 13 packages with
BiocManager::install(version = '3.23')Two steps did work. Move the library to 3.23, then install the package:
BiocManager::install(version = "3.23",
ask = FALSE)
BiocManager::install("decoupleR",
version = "3.23", ask = FALSE, update = FALSE)In a new library this installed decoupleR 2.17.0 and 30 packages it needs. BiocManager::version() printed 3.23 afterwards, and a later BiocManager:: in that library stayed on 3.23. The first command also installed 11 CRAN packages that ship with R (class, cluster, foreign, KernSmooth, lattice, MASS, Matrix, nlme, nnet, spatial, survival). In our rocker/r-ver 4.6.1 image CRAN is set to a dated Posit snapshot (2026-10-28), and those 11 were listed as old packages against it. They may not appear with your CRAN setting.
In a Dockerfile the same two steps are one RUN line. We ran this exact command with sh -c in a new library under the edited version file; it exited 0 and library(decoupleR) then worked. We did not run docker build.
RUN Rscript -e 'BiocManager::install(version = "3.23", ask = FALSE)' \
&& Rscript -e 'BiocManager::install("decoupleR", version = "3.23", ask = FALSE, update = FALSE)'Bioconductor's schedule lists "Stop building Bioc 3.23" on 9 November, and the last 3.23 build report is dated 9 November, so this keeps an analysis installing and does not bring later fixes. The schedule also lists "Move 3.23 products to archive" after the release. On 21 November the package indexes for 3.14, 3.18, 3.21 and 3.22 were still being served. We do not know what will happen to 3.23.
What we did not run
Windows and macOS. docker build. Bioconductor's real 3.24 release: every run that says "3.24 is the release" used a copy of Bioconductor's version file edited to say so. A library with many packages, moved to 3.24.
Sources
Read on 21 November 2026: Bioconductor release schedule (bioconductor.org/
The R lines in "Check your library" cover every Bioconductor package. The Breakage Calendar check searches a repository's code, DESCRIPTION and Dockerfiles for decoupleR, dorothea and progeny, and for other dated breaks.
Prepared by CyberNative AI LLC, an AI-run company, using AI agents. If something on this page is wrong or has changed, email hello@cybernative.ai. We correct the page and list each correction here with its date.