# QIIME 2 2025.10 is now available! **URL:** https://forum.qiime2.org/t/qiime-2-2025-10-is-now-available/33760 **Category:** Announcements **Tags:** release **Created:** [November 3, 2025, 6:23pm UTC](https://forum.qiime2.org/t/qiime-2-2025-10-is-now-available/33760 "2025-11-03T18:23:39Z") **Posts on this page:** 5 **Page:** 1
### Author: ![q2d2](https://forum.qiime2.org/user_avatar/forum.qiime2.org/q2d2/32/613_2.png) [@q2d2](https://forum.qiime2.org/u/q2d2) #### Post date: [November 3, 2025, 6:23pm UTC](https://forum.qiime2.org/t/qiime-2-2025-10-is-now-available/33760/1 "2025-11-03T18:23:39Z")
## Hello QIIME 2 Community! πŸ‘‹πŸΌ Our second full release for 2025 is now available! πŸ₯³ _Huge_ thanks to everyone for all of their hard work; this is a large release with lots of new and exciting features, bug fixes, and more! πŸ™ŒπŸΌ * * * ## 🚨 Important Announcements 🚨 ### Job announcement πŸ“’ - [Northern Arizona University](https://nau.edu) is hiring one or more Assistant Professors for the academic year beginning in Fall 2026. We are specifically interested in people who have a background in building and deploying ML/AI methods in support of microbiome research. Have you deployed ML/AI tools in QIIME 2 plugins? That's a plus! Come to NAU and help us lead in microbiome data science! [Learn more here.](https://careers.nau.edu/jobs/assistant-professor-multiple-positions-applications-of-artificial-intelligence-and-machine-learning-ai-ml-flagstaff-arizona-united-states) ### β€Ό Interface Changes coming in QIIME 2 2026.1 β€Ό - We're planning a broad update to plugins to more consistently refer to metadata, such that many metadata parameters will be renamed to `metadata`. This will impact a lot of actions, but will result in more consistent naming so should ultimately make QIIME 2 more convenient for users. - [q2-dada2](https://github.com/qiime2/q2-dada2) - [q2-feature-classifier](https://github.com/qiime2/q2-feature-classifier) - [q2-feature-table](https://github.com/qiime2/q2-feature-table) - [q2-taxa](https://github.com/qiime2/q2-taxa) * * * ### Developer Announcements 🧱 Starting in 2026, we’ll update our Python version **at most once per year** , and **only in the April full release** (when needed). This gives plugin developers ample time to keep their plugins current and reduces the internal time spend for our team to make these changes each year. **How we decide if we're upgrading our Python version dependency πŸ€”** - **After each October release** we assess whether a Python update is possible, based on the availability of compatible conda packages for our dependencies, and/or require, based on the [end-of-life timeline](https://devguide.python.org/versions/) for our current version. - If an update is planned for April, we start testing immediately so there’s ample time to solve environments and address any API-related test failures. **What this means for developers 🫡🏼** - If you maintain a plugin, plan your compatibility work between **Oct β†’ Apr** (when a Python bump is announced). - No Python bumps will occur in January, July, or October releases. **What this means for users** - Not much. The details of which version of Python QIIME 2 users isn't something users need to be too concerned with. More details on the schedule and policy can be found [here](https://develop.qiime2.org/en/latest/framework/references/dev-cycle-structure.html#python-version-updates) 🐍 * * * ## ✨ Here are the Highlights of the Release! ✨ * * * **[QIIME 2 View Updates](https://view.qiime2.org)** πŸ” - @Oddant1 added provenance-based error reporting to QIIME 2 View. We are now maintaining a database of known issues with plugin versions, so that we can alert users if problems arise (including information on the severity of issues). If you load a Result in QIIME 2 View that is affected by any known issues, the _Provenance_ view will show which nodes are affected and by what issues. Here's an example: - @Oddant1 enabled more informative viewing of QIIME 2 Artifacts (i.e., `.qza` files, as opposed to Visualizations or `.qzv` files) in QIIME 2 View. Now, if you load an Artifact, you'll get a preview of and download links for the data they contain. This provides additional transparency on our `.qza` file format (remember, it's [just a fancy zip file](https://develop.qiime2.org/en/latest/framework/references/archive-versions.html)), as well as another easy way to export data from QIIME 2 if you'd like to do that. Here's an example: - @jacobs found and fixed a bug in q2view that prevented it from loading URLs with uuids in them [here](https://github.com/qiime2/q2view/pull/57) πŸ”’ * * * **[Distribution Updates](https://github.com/qiime2/distributions)** πŸ“¦ - **amplicon** - **moshpit** * * * **[Framework (i.e., `rachis`) Updates](https://github.com/qiime2/qiime2)** πŸ‡ - The QIIME 2 Framework (sometimes referred to as Q2F) is being re-branded as `rachis`. This won't impact users or developers, but will help us improve clarity in our documentation and is intended to convey generality of Q2F as we explore expanded directions for the project. Learn more in our [_News_ post](https://forum.qiime2.org/t/announcing-rachis-a-rebrand-of-the-qiime-2-framework-q2f/33749). - @ebolyen added a new visualization type called **`Report`** , which enables combining of multiple QIIME 2 Visualizations into a single report that can be shared. This can be accessed using the new `qiime tools make-report` command, which takes a collection of `.qzv` files as input. It can also be [accessed through the Python API](https://gist.github.com/ebolyen/4773c744400072215ebc3161f197956d). Interact with an example of this on QIIME 2 View [here](https://view.qiime2.org/visualization/?src=https://raw.githubusercontent.com/caporaso-lab/q2view-visualizations/main/g2s-report.qzv), or see this screenshot. Happy Reporting! πŸ“ˆ - @Oddant1 fixed an issue with recycling output collections when only part of the collection is present. Previously, it would cause an error, now it will only warn then run the action to recreate the collection ⚠ - @Oddant1 changed the extent of detail in the logs written by actions when run in parallel. These no longer contain `debug`-level information, as this was very verbose and made it harder to find relevant information. πŸͺ΅ - @Oddant1 made the behavior of adding multiple copies of the same Result (Results with the same UUID) with different Annotations to the Cache consistent. The Annotations will now be merged in the Cache, and the cached version of the Result will contain all Annotations from all copies πŸ–¨ - @lizgehret added a new `migration` warning that can be used for actions or vizualizers that are being moved from one plugin to another. This is a new parameter on the `register_plugin` action, with syntax is as follows: - @lizgehret created the new Archive v7.1 Format, which includes support for cryptographic signing of QIIME 2 Results. This leverages a new Annotation sub-type πŸ“œ `Signature`, that can be used to self-sign Artifacts or Visualizations, thus allowing confirmation of who created a particular QIIME 2 Result. This provides a path to secure sharing of QIIME 2 Results that contain executable code, such as AI/ML models, that users may want to apply to their private data (for example, taxonomic classifiers or sample classifiers). πŸͺͺ * * * **Interface Updates** πŸ“Ί - [q2cli](https://github.com/qiime2/q2cli) - [q2templates](https://github.com/qiime2/q2templates) * * * **Plugin Updates** πŸ”Œ - [q2-dada2](https://github.com/qiime2/q2-dada2) - [q2-demux](https://github.com/qiime2/q2-demux) - [q2-diversity](https://github.com/qiime2/q2-diversity) - [q2-diversity-lib](https://github.com/qiime2/q2-diversity-lib) - [q2-feature-table](https://github.com/qiime2/q2-feature-table) - [q2-phylogeny](https://github.com/qiime2/q2-phylogeny) - [q2-taxa](https://github.com/qiime2/q2-taxa) - [q2-types](https://github.com/qiime2/q2-types) - [q2-vizard](https://github.com/qiime2/q2-vizard) - [RESCRIPt](https://github.com/bokulich-lab/RESCRIPt) * * * **Community Plugin Updates** πŸ”Œ - [plugin template](https://github.com/caporaso-lab/plugin-template) - @cduvallet fixed a [small πŸͺ²](https://github.com/caporaso-lab/plugin-template/pull/37) * * * **Docker Container Updates** πŸ«™ - @Oddant1 created a workflow to make publishing Galaxy Docker containers for the amplicon distribution easier, so expect to see those on [quay](https://quay.io/repository/qiime2/q2galaxy?tab=tags) ⭐ ---
### Author: ![lizgehret](https://forum.qiime2.org/user_avatar/forum.qiime2.org/lizgehret/32/17128_2.png) [@lizgehret](https://forum.qiime2.org/u/lizgehret) #### Post date: [November 3, 2025, 6:25pm UTC](https://forum.qiime2.org/t/qiime-2-2025-10-is-now-available/33760/2 "2025-11-03T18:25:38Z")
---
### Author: ![lizgehret](https://forum.qiime2.org/user_avatar/forum.qiime2.org/lizgehret/32/17128_2.png) [@lizgehret](https://forum.qiime2.org/u/lizgehret) #### Post date: [November 3, 2025, 7:03pm UTC](https://forum.qiime2.org/t/qiime-2-2025-10-is-now-available/33760/3 "2025-11-03T19:03:27Z")
---
### Author: ![lizgehret](https://forum.qiime2.org/user_avatar/forum.qiime2.org/lizgehret/32/17128_2.png) [@lizgehret](https://forum.qiime2.org/u/lizgehret) #### Post date: [November 3, 2025, 7:03pm UTC](https://forum.qiime2.org/t/qiime-2-2025-10-is-now-available/33760/4 "2025-11-03T19:03:38Z")
---
### Author: ![q2d2](https://forum.qiime2.org/user_avatar/forum.qiime2.org/q2d2/32/613_2.png) [@q2d2](https://forum.qiime2.org/u/q2d2) #### Post date: [November 11, 2025, 9:40am UTC](https://forum.qiime2.org/t/qiime-2-2025-10-is-now-available/33760/5 "2025-11-11T09:40:21Z")
Hello QIIME 2 community! πŸ‘‹πŸΌ We have just released a patch for the 2025.10 release to address a few bugs/last minute improvements. If you've already installed any distribution for 2025.10 prior to this patch, please re-install πŸ™πŸ» All of the changes included in this patch are listed below. [Framework (i.e., `rachis`) Updates](https://github.com/qiime2/qiime2) 🌿 - @lizgehret fixed a couple of bugs within the new `Signature` functionality: - When attempting to run either `annotation_list` or `annotation_fetch` on a Result with a Signature in either QIIME 2 2025.4 or 2025.7, an unexpected error was raised (due to no `annotation_type` found). - The new Archive Format v7.1 wasn't added into the Archiver, thus not correctly 'stamping' new Results (of 2025.10) as 7.1 (as opposed to 7.0). [q2-boots](https://github.com/qiime2/q2-boots) 🎿 - @lizgehret added `xdist` to allow for the test suite to be run in parallel, improving runtime (thanks @andrewsanchez for this idea πŸ’‘). [q2-diversity](https://github.com/qiime2/q2-diversity) πŸ“Š - @colinvwood improved runtime on the `alpha-diversity` test suite. [RESCRIPt](https://github.com/bokulich-lab/rescript) πŸ“œ - @lizgehret fixed a πŸͺ² preventing one of our tests from fetching an artifact from the SILVA database. Thanks to everyone for getting these fixes out so quickly; please don't hesitate to reach out with any questions!