-
-
Notifications
You must be signed in to change notification settings - Fork 15k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove end-of-life mongodb versions #195448
Comments
@pacien Do you plan to work on this before the branch-off? |
Related #155121 |
I want the following gone before the 23.05 branch-off:
All of these have reached their end of life, and we cannot keep them around |
I'll have a look at it later on 👍 |
@mweinelt |
Here we are again, MongoDB 4.4 will go EOL in NixOS 23.11 release. Please inline the MongoDB versions 4.4 inside your expressions if you want to keep using UniFi in nixpkgs. |
I tested Unifi Controller 7 and 8 with different MongoDB versions, and: For Unifi 7:
For Unifi 8:
This means that it should be possible for us to remove MongoDB 4.4. We probably also want to remove unifiLTS, unifi5, unifi6 as well. Disclaimer: When I say "it works", it means that I tested basic functionalities, I can't guarantee full compatibility. |
I've been running unifi 8.1.113 with mongodb 6 for a few weeks now with no issues. Upgraded mongodb 4.4 -> 5.0 -> 6.0 and the database as well in each step. |
MongoDB 4.4 has been dropped on master. Existing UniFi 7 and 8 users on the unstable branches, who do not have expressions inlined, will have MongoDB upgraded to 5.0 in the next bumps. Please consult the official upgrade instructions if necessary. MongoDB 5.0 will go EOL in NixOS 24.05 release, so the same instructions in #195448 (comment) still apply. |
UniFi Network Application 8.1 and newer now officially support MongoDB up to 7.0. |
Support for mongodb 5.0 ends after 2024-10-31 and must be removed for the NixOS 24.11 release. |
https://endoflife.date/mongodb
all of the above should be remove before branch-off.
@bluescreen303 @offlinehacker @cstrahan @pacien
The text was updated successfully, but these errors were encountered: