If you ever updated your system.stateversion or home.stateversion (in home manager), what made you do it?

1

Since Firefox now supports XDG base directory spec, the firefox config and profiles directory is now $XDG_CONFIG_HOME/mozilla/firefox instead of ~/.mozilla/firefox. Using Firefox with Home Manager now shows this message:

You are currently using the legacy default (`".mozilla/firefox"`) because `home.stateVersion` is less than "26.05".
To silence this warning and keep legacy behavior, set:
programs.firefox.configPath = ".mozilla/firefox";
To adopt the new default behavior, set:
programs.firefox.configPath = "${config.xdg.configHome}/mozilla/firefox";
To migrate to the XDG path, move `~/.mozilla/firefox` to
`$XDG_CONFIG_HOME/mozilla/firefox` and remove the old directory.
Native messaging hosts are not moved by this option change.
1 Like
2

I did update it because it felt of to have an old number there.

I do regret the time spent walking through the config and manual back then. A single day for 2 bumps…

I just accepted the issue and let it where it is now.

If there will be ever a warning like this, I will explicitely set one of the defaults and make sure to migrate properly. It will not make me touch the stateversion.

3

I updated it one time as I was reinstalling NixOS onto a new SSD.

2 Likes
4

For me it was the changes in the defaults for programs.neovim.withPython3 and withRuby. I was rushing and decided to change home.stateVersion. In retrospect I should have left it alone and explicitly set the new defaults. I’m sorry if I explode the world because I mucked with stateVersion.