Current status
The project has moved under the Stubborn organization. Spring Cloud Contract is being removed from Spring Cloud release trains, future ones and ones already shipped, so this is not a change you can wait out. The first Stubborn Contract release, including new Maven coordinates, package names, and migration instructions, is planned. Until then, existing users can continue using their current Spring Cloud Contract versions while preparing for the transition.
What happened?
Spring Cloud Contract is entering a new chapter as it transitions away from the Spring Cloud portfolio. Stubborn Contract is the official continuation of the project, led by Marcin Grzejszczak, one of its original creators. The repository transition has moved the project under the Stubborn organization.
What changes?
The project is moving toward Stubborn-branded Maven coordinates and a package rename from Spring namespaces (org.springframework.cloud) to Stubborn namespaces (sh.stubborn). This repackaging is planned but not yet complete. No artifacts have been renamed or republished yet.
Which Spring Cloud release trains are affected?
Spring Cloud Contract is being removed from future Spring Cloud release trains, and is also being pulled from release trains that already shipped it. If your organization currently pins a Spring Cloud BOM version, don't assume an existing pin protects you indefinitely, check Spring's own release notes for your train, and treat this as a "when," not "if," migration.
What stays the same?
The contract-testing approach, the core testing model, and the open-source license (Apache 2.0) remain unchanged. Existing Spring Cloud Contract users are not required to change anything today.
Current status
The project has moved under the Stubborn organization. The first Stubborn Contract release, including new Maven coordinates, package names, and migration instructions, is planned. Until then, existing users can continue using their current Spring Cloud Contract versions while preparing for the transition.
When can users migrate?
There is no fixed date yet. The roadmap is milestone-based rather than date-based; see the Roadmap page for what's planned and what's already in place. Migration will be possible once the first Stubborn-branded release ships with documented package and coordinate changes.
What should existing Spring Cloud Contract users do now?
Keep using your current Spring Cloud Contract version, nothing breaks today. But given that Spring Cloud Contract is coming out of release trains you may already be running, don't treat this as a someday problem. Watch this page and the Roadmap for updates, and if your production systems depend on contract testing staying reliable through this transition, an Enterprise Partnership is the fastest way to get migration timing, roadmap input, and direct support, rather than finding out on the community timeline.
Where will migration instructions appear?
Migration instructions, including new Maven coordinates and package names, will be published on this page and in the Stubborn Contract repository once the first Stubborn-branded release is available. Nothing is published yet. This page will be updated when it is.
Want to shape the transition?
Enterprise Partners help fund and prioritize migration tooling and roadmap work.