Library
Mongock
Mongock, the Java/Spring change-management tool for MongoDB, stops feature development now and reaches end-of-life at the end of 2026; its makers point users to a successor, Flamingock
departs Date not announced
What this means for you
Mongock is the tool many Java and Spring Boot teams use to version and apply schema/data migrations ("change units") against MongoDB, the way Flyway or Liquibase work for SQL. Its maintainers have announced it is in maintenance mode as of this announcement and will reach end-of-life at the end of 2026. Until then it still receives critical bug fixes and security updates; after that the project stays downloadable but gets no more fixes, security patches, or features — all new development has moved to a successor, Flamingock, built by the same team. Nothing breaks the day you read this: an app that already depends on Mongock keeps running and keeps applying its existing change units. What ends is the maintenance track, so over 2027 an app pinned to Mongock accumulates unpatched issues in its migration layer and drifts off supported ground. No exact end-of-2026 date has been given, so treat "end of 2026" as the window, not a precise cutoff.
Where to go
The maintainers position Flamingock as the migration target and say it imports Mongock's existing audit history and recognises already-executed change units, so it continues where Mongock left off rather than re-running past migrations. They describe the typical move as a single dependency swap and a single annotation, leaving existing change units untouched — but it is a successor, not a drop-in, so validate it against your own migration suite in a non-production environment before trusting it in a deploy path. Teams that prefer to leave the Mongock ecosystem entirely can evaluate general-purpose migration tooling, though most MongoDB-specific change-management features are particular to this lineage.
- Flamingock — the maintainers' named successor, which imports Mongock audit history
- Liquibase (has a MongoDB extension) for teams standardising on one migration tool across databases
Mongock is one of those tools that is invisible until it is load-bearing: if your Java or Spring Boot service applies versioned changes to a MongoDB database, there is a good chance Mongock is what runs them on startup, in the same role Flyway and Liquibase play for relational databases. Its maintainers have now announced that it is entering maintenance mode and “will reach end-of-life at the end of 2026,” with all new development moving to a successor project, Flamingock, from the same team.
This is a soft sunset, not a switch-off. Between now and the end of 2026 Mongock still gets critical bug fixes and security updates, and after end-of-life the library stays published and downloadable — your existing builds will not stop resolving it. What stops is the forward maintenance: no new fixes, no security patches, no features. An application left on Mongock will keep applying its change units exactly as before, but its migration layer quietly moves from “maintained” to “frozen,” which is the kind of dependency that turns into an audit finding rather than an outage.
Because the maintainers gave a window (“the end of 2026”) rather than a specific day, this entry carries no exact countdown — inventing one would be a guess, and the honest status is that the plan is confirmed while the precise date is not. What is precise is the direction: feature work has already moved to Flamingock as of this announcement, so anyone starting new work today is starting on a deprecated library.
The maintainers’ recommended path is Flamingock, which they say imports Mongock’s audit history and recognises already-executed change units, so it picks up where Mongock stopped rather than replaying old migrations. They describe the move as roughly a dependency swap plus one annotation. That is a successor rather than a strict drop-in, so the useful thing to do with a year of runway is the unglamorous one: try the migration against your real change-unit suite in a staging environment now, while Mongock is still maintained and there is no pressure, rather than after the last security patch has shipped.
Entry changelog
- — last reviewed.
- — Entry created from the maintainers' announcement on flamingock.io. Surfaced via Layer-2 discovery (Hacker News), then written from the primary announcement, not the discussion thread.
Spot an error or a changed date? Tell us and it’s corrected the same night.