From ec24b406de7e3a033ba46c5d491ba7e1575ca4ad Mon Sep 17 00:00:00 2001 From: sayakpaul Date: Tue, 29 Sep 2026 15:28:41 +0530 Subject: [PATCH 1/5] document release philosophy --- docs/source/en/conceptual/contribution.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/source/en/conceptual/contribution.md b/docs/source/en/conceptual/contribution.md index 285613641d53..a2c3040b1a95 100644 --- a/docs/source/en/conceptual/contribution.md +++ b/docs/source/en/conceptual/contribution.md @@ -343,6 +343,16 @@ build powerful generative AI applications. By adding a new model, pipeline, or scheduler you might enable a new powerful use case for any of the user interfaces relying on Diffusers which can be of immense value for the whole generative AI ecosystem. +#### When new model or pipeline support is released + +New model / pipeline support can warrant a new release only if it is well coordinated with the Diffusers team in advance. + +A release does not happen automatically when a model or pipeline pull request is merged. Maintainers first check that the integration is complete and that the release tests pass. + +New model or pipeline support normally goes into the next minor release. We merge the integration into `main` and create the release branch from `main`. The release therefore contains all changes merged since the previous release, rather than only the model or pipeline integration. + +Release notes highlight the new model or pipeline and also summarize the other changes included in the release. Patch releases are normally reserved for fixes to an existing release. + Diffusers has a couple of open feature requests for all three components - feel free to gloss over them if you don't know yet what specific component you would like to add: - [Model or pipeline](https://github.com/huggingface/diffusers/issues?q=is%3Aopen+is%3Aissue+label%3A%22New+pipeline%2Fmodel%22) From c5933a773fa0feaf0a92c1c05cecf15a76c7edd1 Mon Sep 17 00:00:00 2001 From: Sayak Paul Date: Wed, 30 Sep 2026 09:39:20 +0530 Subject: [PATCH 2/5] Update docs/source/en/conceptual/contribution.md Co-authored-by: Steven Liu <59462357+stevhliu@users.noreply.github.com> --- docs/source/en/conceptual/contribution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/en/conceptual/contribution.md b/docs/source/en/conceptual/contribution.md index a2c3040b1a95..81cfb162ea30 100644 --- a/docs/source/en/conceptual/contribution.md +++ b/docs/source/en/conceptual/contribution.md @@ -345,7 +345,7 @@ By adding a new model, pipeline, or scheduler you might enable a new powerful us #### When new model or pipeline support is released -New model / pipeline support can warrant a new release only if it is well coordinated with the Diffusers team in advance. +A new model or pipeline may be included in a release if you coordinate the integration with the Diffusers team in advance. [add how to coordinate with team here] A release does not happen automatically when a model or pipeline pull request is merged. Maintainers first check that the integration is complete and that the release tests pass. From 97158de5ecfcd2619f9dac59e132b2b7222fd9a5 Mon Sep 17 00:00:00 2001 From: Sayak Paul Date: Wed, 30 Sep 2026 09:39:55 +0530 Subject: [PATCH 3/5] Update docs/source/en/conceptual/contribution.md Co-authored-by: Steven Liu <59462357+stevhliu@users.noreply.github.com> --- docs/source/en/conceptual/contribution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/en/conceptual/contribution.md b/docs/source/en/conceptual/contribution.md index 81cfb162ea30..f0331a4855ee 100644 --- a/docs/source/en/conceptual/contribution.md +++ b/docs/source/en/conceptual/contribution.md @@ -347,7 +347,7 @@ By adding a new model, pipeline, or scheduler you might enable a new powerful us A new model or pipeline may be included in a release if you coordinate the integration with the Diffusers team in advance. [add how to coordinate with team here] -A release does not happen automatically when a model or pipeline pull request is merged. Maintainers first check that the integration is complete and that the release tests pass. +A release does not happen automatically when a model or pipeline pull request is merged. Before a release, maintainers first check that the integration is complete and that release tests pass. New model or pipeline support normally goes into the next minor release. We merge the integration into `main` and create the release branch from `main`. The release therefore contains all changes merged since the previous release, rather than only the model or pipeline integration. From 976477e6bf384dd96e476d953d64a8e5bccd20cd Mon Sep 17 00:00:00 2001 From: Sayak Paul Date: Wed, 30 Sep 2026 09:40:07 +0530 Subject: [PATCH 4/5] Update docs/source/en/conceptual/contribution.md Co-authored-by: Steven Liu <59462357+stevhliu@users.noreply.github.com> --- docs/source/en/conceptual/contribution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/en/conceptual/contribution.md b/docs/source/en/conceptual/contribution.md index f0331a4855ee..627e457b252d 100644 --- a/docs/source/en/conceptual/contribution.md +++ b/docs/source/en/conceptual/contribution.md @@ -349,7 +349,7 @@ A new model or pipeline may be included in a release if you coordinate the integ A release does not happen automatically when a model or pipeline pull request is merged. Before a release, maintainers first check that the integration is complete and that release tests pass. -New model or pipeline support normally goes into the next minor release. We merge the integration into `main` and create the release branch from `main`. The release therefore contains all changes merged since the previous release, rather than only the model or pipeline integration. +New model or pipeline support normally goes into the next minor release. The integration is merged into `main` and the release branch is created from it. The release contains all changes merged since the previous release, rather than only the model or pipeline integration. Release notes highlight the new model or pipeline and also summarize the other changes included in the release. Patch releases are normally reserved for fixes to an existing release. From d6cb211ea081e842c6655aefb24f345889933f23 Mon Sep 17 00:00:00 2001 From: sayakpaul Date: Wed, 30 Sep 2026 09:42:29 +0530 Subject: [PATCH 5/5] clarify how folks can reach out to coordinate a release. --- docs/source/en/conceptual/contribution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/en/conceptual/contribution.md b/docs/source/en/conceptual/contribution.md index 627e457b252d..d13f4cee1a11 100644 --- a/docs/source/en/conceptual/contribution.md +++ b/docs/source/en/conceptual/contribution.md @@ -345,7 +345,7 @@ By adding a new model, pipeline, or scheduler you might enable a new powerful us #### When new model or pipeline support is released -A new model or pipeline may be included in a release if you coordinate the integration with the Diffusers team in advance. [add how to coordinate with team here] +A new model or pipeline may be included in a release if you coordinate the integration with the Diffusers team in advance. Feel free to reach out to us, either via an issue on the Diffusers repository or by emailing to `diffusers@huggingface.co`. A release does not happen automatically when a model or pipeline pull request is merged. Before a release, maintainers first check that the integration is complete and that release tests pass.