nix-community.nixvim/version-info.toml

# DO NOT MODIFY!
# This file was generated by ci/version-info/default.nix
nixpkgs_rev = "fa0ef8a6bb1651aa26c939aeb51b5f499e86b0ec"
release = "25.11"
unstable = true

[versions."25.05"]
branch = "nixos-25.05"
channel = "nixos-25.05"
status = "stable"

[versions."25.11"]
branch = "main"
channel = "nixpkgs-unstable"
status = "rolling"
version-info: init 2025-05-22 17:29:36 +01:00			`# DO NOT MODIFY!`
ci: rename `update-scripts` → `ci` This changes how we think about this directory; it does not need to be exclusively for scripts related to updates, but should be a place for any scripts intended to be run by CI workflows. This mindset should make it easier to develop and test the business logic of workflows, without always needing to test "in production" on the nixvim repo or a fork. 2025-06-11 22:13:00 +01:00			`# This file was generated by ci/version-info/default.nix`
flake.lock: Update Flake lock file updates: • Updated input 'nixpkgs': 'github:NixOS/nixpkgs/be9e214982e20b8310878ac2baa063a961c1bdf6?narHash=sha256-HM791ZQtXV93xtCY%2BZxG1REzhQenSQO020cu6rHtAPk%3D' (2025-07-09) → 'github:NixOS/nixpkgs/fa0ef8a6bb1651aa26c939aeb51b5f499e86b0ec?narHash=sha256-2Kp9St3Pbsmu%2BxMsobLcgzzUxPvZR7alVJWyuk2BAPc%3D' (2025-07-17) 2025-07-18 12:18:25 +00:00			`nixpkgs_rev = "fa0ef8a6bb1651aa26c939aeb51b5f499e86b0ec"`
version-info: init 2025-05-22 17:29:36 +01:00			`release = "25.11"`
			`unstable = true`
update-scripts/version-info: get channel status for supported versions Fetch channel info from NixOS/infra, the canonical source of truth. 2025-05-25 04:36:42 +01:00
			`[versions."25.05"]`
			`branch = "nixos-25.05"`
			`channel = "nixos-25.05"`
			`status = "stable"`

			`[versions."25.11"]`
			`branch = "main"`
			`channel = "nixpkgs-unstable"`
			`status = "rolling"`