Open-source project
reactor/reactor avatar
reactor/reactor

Every example in reactor/reactor pins a milestone, and the version scheme is spelled two ways

Reactor Bill Of Materials (tracking reactor-core, reactor-netty and more)

3,693 stars483 forksUnknownApache-2.0

At a glance

What is it?
This repository is not a library. It hosts the Reactor bill of materials, a curated set of versions that are meant to be imported so that reactor-core, reactor-netty and the addons can be declared without one. The page documents three build-tool paths for that one import, and all three use a pre-release version.
Who is it for?
The repository fits a Maven or Gradle user who wants the Reactor artifacts aligned on one curated set instead of tracking versions by hand, and the import is two blocks of configuration. It does not fit someone who needs to know which versions a BOM actually pins without reading its contents, because the page never lists them.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 5 days ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • reactor/reactor3,693 ★ · +1
Star history
Repository2026-09-242026-11-14
reactor/reactor3.7k3.7k

1 Stars in the last 51 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The version scheme is MICRO in the heading and PATCH in the bullet

The BOM versioning section defines the scheme as YYYY.MINOR.MICRO-QUALIFIER. The bullets underneath then talk about .MINOR and .PATCH, and the YYYY bullet gives its example as the year of the first GA release in a cycle, illustrated with 3.4.0 for the 3.4.x line.

Three things do not line up. The third component has two names. The example under a scheme introduced as applying since Europium is a pre-Europium version, which is the numbering the page says was replaced. And 3.4.0 is not a year, so the illustration does not demonstrate the rule it is attached to.

The three rules that do hold are clear enough to use. YYYY is the year of the first general release in the cycle, MINOR is a counter starting at zero that increments per release cycle, and PATCH is a counter starting at zero that increments per service release, with the textual qualifier omitted for general releases. In practice the listed releases all sit at MINOR zero, 2025.0.7 and 2026.0.0-M2, which is what the rule predicts for a project that has one release train per year.

Every release train has a codename and the list stops at Europium

The page says each release train carries a codename taken from the periodic table in growing alphabetical order, and then lists five: Aluminium for 3.0.x, Bismuth for 3.1.x, Californium for 3.2.x, Dysprosium for 3.3.x, and Europium, annotated 2020.0, for 3.4.x.

That is the complete list on the page, and Europium is the generation where the year-based numbering starts. Every train since then is named only by its year, so the codenames for 2021, 2022, 2023, 2024, 2025 and 2026 are not written down anywhere here, even though the page states the codename exists for discussion purposes.

The page also preserves the older scheme for anyone reading an old pom. Up until Dysprosium the BOM was versioned with a codename and a qualifier, and the examples given are Aluminium-RELEASE for a first general release, Bismuth-M1, Californium-SR1 for a service release, Dysprosium-RC1, and Dysprosium-BUILD-SNAPSHOT for the snapshot that followed each patch. Those qualifiers have no equivalent in the current scheme, which is why the mapping is spelled out as what each one would be today.

The Gradle 4.x path uses a configuration later Gradle versions removed

Three code paths are offered for one import. Maven gets a dependencyManagement block with the import scope. Gradle 5.0 and later get one line inside the dependencies block:

groovy
dependencies {
     // import BOM
     implementation platform('io.projectreactor:reactor-bom:2026.0.0-M2')

     // add dependencies without a version number
     implementation 'io.projectreactor:reactor-core'
}

The third path is for Gradle 4.x and earlier, which have no core support for Maven BOMs. It applies Spring's dependency-management plugin, declares it at version 1.0.11.RELEASE with an instruction to check whether a newer one exists, imports the same BOM through a mavenBom entry, and then declares the dependency with the configuration named compile.

That last word is the problem. compile was removed from Gradle years ago, so the legacy snippet cannot be pasted into a Gradle that is old enough to need the plugin and new enough to install it. It documents a migration path for a toolchain that has been end-of-life for longer than any of the Reactor versions it pins.

The repository holds a Gradle build and no source directory

The tree is nine entries: .github/, .gitignore, LICENSE, README.md, build.gradle, gradle.properties, gradle/, gradlew, gradlew.bat and settings.gradle.

There is no src/ and no pom.xml, and the repository's own metadata gives no primary language at all. Both fit what the repository is for. The deliverable is a generated POM that pins versions, so there is no library code to write, and the build that produces it is Gradle with a wrapper checked in, which is why both gradlew and gradlew.bat are present for a project whose output is consumed by Maven.

So the artifact Maven downloads is built by a different tool than the one it is written for. Nothing on the page explains that indirection, and nothing lists the versions the generated POM contains. A reader who wants to know which reactor-netty build a given BOM pairs with has to open the published POM rather than this repository.

This repository takes the BOM and transverse issues, and sends everything else elsewhere

The contributing section is unusually direct about scope. The repository is for hosting the BOM and for transverse issues only, and the page says that if you are opening an issue or a pull request it should usually go to the repository for the specific artifact involved.

The shared contributing guidelines are not in this repository either. They live in a separate reactor/.github repository, and the same file is linked for the question-answering section. So the repository that holds the bill of materials holds neither the contribution rules nor the support documentation.

The project catalogue is on the page as well, one section per artifact: reactor-core for the reactive foundations with Mono for a single element and Flux for many, reactor-netty for the TCP and HTTP client and server, and the addons, where reactor-adapter adapts to and from other libraries, mainly RxJava 2, and reactor-extra holds retry and math utilities. Each entry links an API documentation path under the same docs site.

A BOM exists because the artifact versions are not aligned with each other

The reason the bill of materials is curated by hand is stated once and it is the load-bearing sentence on the page: the different artifact versions are not necessarily aligned, so the BOM represents a release train with a heterogeneous range of versions curated to work together.

That is what the import mechanism is for. In Maven the BOM goes into dependencyManagement with the import scope, and in Gradle the platform keyword does the equivalent job inside the dependencies block. Either way the effect is that reactor-core and reactor-test are then declared with no version element at all, and the versions come from the train rather than from the build file.

The mechanism is not symmetric across tools, and that is worth knowing before copying. Maven needs two nested blocks and a type of pom; Gradle needs one line. The page also notes that importing provides defaults only when a dependency is added without an explicit version, so a build file that pins its own version overrides the train silently.

A milestone of one train and a service release of another shipped 116 seconds apart

The three most recent releases are 2026.0.0-M1 on 2026-08-24 at 03:34:08, 2025.0.7 on 2026-08-24 at 03:32:12, and 2026.0.0-M2 on 2026-09-24. The first two are two minutes apart on the same day, one a milestone of the 2026 train and the other a service release of the 2025 train, which is the shape the scheme predicts: patch releases continue on the previous cycle while the next cycle is in milestone.

Every code sample on the page imports 2026.0.0-M2, so a reader copying any of the three snippets verbatim gets a milestone rather than a general release. The most recent general release in the list is 2025.0.7.

The last push to main is dated 2026-09-28, four days after the M2 tag, so the branch has moved past what the samples point at. The page also carries a Maven Central badge that reads the published version of io.projectreactor/reactor-bom, which is the one place the page shows a version resolved from outside the repository.

Editorial conclusion

The repository fits a Maven or Gradle user who wants the Reactor artifacts aligned on one curated set instead of tracking versions by hand, and the import is two blocks of configuration. It does not fit someone who needs to know which versions a BOM actually pins without reading its contents, because the page never lists them. Check three things before you import it. Whether you want a milestone or a general release, since every snippet on the page uses 2026.0.0-M2 while 2025.0.7 is the most recent general release listed. Which build tool path you follow, since the Gradle 4.x instructions use a configuration later Gradle versions removed. And where your issue belongs, because this repository is for the BOM and cross-project questions only.

Frequently asked questions

What is the reactor-bom for?

It is a bill of materials holding a curated set of compatible versions for the Reactor projects, reactor-core, reactor-netty and addons such as reactor-extra and reactor-pool. You import it and then declare those projects with no version of your own.

Which reactor-bom version should I import?

Every example on the page imports 2026.0.0-M2, which is a milestone rather than a general release. The three most recent releases are 2026.0.0-M2 on 2026-09-24, 2026.0.0-M1 on 2026-08-24 and 2025.0.7 on 2026-08-24.

How do I use reactor-bom in Maven?

Import it inside a dependencyManagement block with groupId io.projectreactor, artifactId reactor-bom, type pom and scope import. Then add reactor-core, and reactor-test with test scope, without any version element.

How do I use reactor-bom in Gradle?

On Gradle 5.0 and later, use the platform keyword inside the dependencies block and then add the artifacts with no version. Older Gradle versions have no core support for Maven BOMs, so the page points at Spring's gradle-dependency-management plugin at version 1.0.11.RELEASE and imports the BOM through mavenBom.

Where should I file an issue about reactor-bom?

The page says this repository hosts the BOM and transverse issues only, and that an issue or pull request usually belongs in the repository for the specific artifact. The shared contributing guidelines live in a separate reactor/.github repository.

What does the reactor-bom version scheme mean?

YYYY is the year of the first general release in a release cycle, MINOR is a zero-based counter that increments per release cycle, and PATCH is a zero-based counter that increments per service release, with the textual qualifier omitted for general releases. The scheme applies from the Europium generation onward.

Official sources

  1. License: Apache-2.0
  2. Project website
  3. reactor/reactor on GitHub
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/reactor-reactor.svg)](https://hysenlabs.com/projects/reactor-reactor)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/reactor-reactor.svg)](https://hysenlabs.com/projects/reactor-reactor)

Was this useful?