Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Status Planned
Categories Atlas
Created by Guest
Created on Apr 1, 2025

Use Semantic Versioning

Hi, My problem is that the terraform provider doesn't use semantic versioning. This has caused me quite a few problems. Firstly - it's difficult when scrolling through your version releases to understand what's breaking and what's not (I lost an hour today having to check all the releases for updates, and then applying every couple of versions from an outdated provider to make sure there were no breaking changes). Secondly, it means I have to pin a specific version in my terraform provider rather than leaving it to auto-update to the latest minor version "~> 1.0". Lastly, it makes using dependabot/renovate much harder, as its not able to auto update the latest minor change. I saw there was already an issue that had some discussion but no follow up https://github.com/mongodb/terraform-provider-mongodbatlas/issues/2656 It would be great if you could get re-evaluate this feature request. Other terraform providers use semver and it'd be great if you did too. Thanks.
  • Attach files
  • Guest
    Apr 2, 2025
    Great to see! Thanks for the prompt response and looking forward to the new change :)
  • Guest
    Apr 2, 2025
    Thank you for the feedback and especially in sharing the challenges you have faced in how we've handled versioning. Based on feedback from our customers like yourself we are indeed moving to a release pattern much closer to sem ver in an upcoming major release, i.e. in a X.0.0 release. Until then we will continue to make it clear in our Information and Upgrade guides in the Registry what is breaking and keep the release pattern described in the issue you noted (https://github.com/mongodb/terraform-provider-mongodbatlas/issues/2656).