Description
Nixvim has used main for unstable and nixos-YY.MM for stable versions for a long time.
This correlates to an extent with nixpkgs. However most other projects use "release-YY.MM", "stable-YY.MM", or simply "YY.MM" because including "nixos" in your branch name kinda implies that either you are NixOS or you only work with NixOS.
Nixvim doesn't require NixOS. It only requires an instance of nixpkgs.
I would propose using release-YY.MM going forward, and creating alias branches for the last few stable versions.
We could add a warning to the nixos-25.05 branch that users should switch to release-25.05 using builtins.warn.
We could maybe add a builtins.trace to nixos-24.11 so it doesn't trip on --abort-on-warn.
Such warnings would only affect users who attempt to update their inputs. Users who stay pinned on an old revision of a nixvim nixos-YY.MM branch would be unaffected by warnings. This makes sense to me, since it is only users who want updates that'd be affected by the change anyway.