4f0dadbf38
After final improvements to the official formatter implementation,
this commit now performs the first treewide reformat of Nix files using it.
This is part of the implementation of RFC 166.
Only "inactive" files are reformatted, meaning only files that
aren't being touched by any PR with activity in the past 2 months.
This is to avoid conflicts for PRs that might soon be merged.
Later we can do a full treewide reformat to get the rest,
which should not cause as many conflicts.
A CI check has already been running for some time to ensure that new and
already-formatted files are formatted, so the files being reformatted here
should also stay formatted.
This commit was automatically created and can be verified using
nix-build
|
||
|---|---|---|
| .. | ||
| 3.5 | ||
| 3.4.nix | ||
| README.md | ||
etcd
Upstream release cadence and support
The etcd project maintains release branches for the current version and previous release.
For example, when v3.5 is the current version, v3.4 is supported. When v3.6 is released, v3.4 goes out of support.
Reference: https://etcd.io/docs/v3.5/op-guide/versioning/
NixOS release and etcd version upkeep
Every major/minor version bump of etcd top-level alias in nixpkgs requires a notification in the next NixOS release notes scheduling the removal of the now unsupported etcd version.
After every NixOS release, the unsupported etcd versions should be removed by etcd maintainers.
User guidelines on etcd upgrades
Before upgrading a NixOS release, certify to upgrade etcd to the latest version in the current used release.
Manual steps might be required for the upgrade.
NixOS release notes might have instructions on how to proceed on upgrades.