Files
neovim/runtime/doc
Evgeni Chasnovski f8c94bb8cf fix(pack): only use tags that strictly comply with semver spec #39342
Problem: Using `version=vim.version.range(...)` in plugin specification
  is meant to use semver-like tags. Whether a tag is semver-like was
  decided by a plain `vim.version.parse` which is not strict by default.
  This allowed treating tags like `nvim-0.6` (which is usually reserved
  for the latest revision compatible with Nvim<=0.6 version) like semver
  tags and resulted in confusing behavior (preferring `nvim-0.6` tag
  over `v0.2.2`, for example).

Solution: Use `vim.version.range(x, { strict = true })` to decide if the
  tag name is semver-like or not. This allows tags like both `v1.2.3`
  and `1.2.3` while being consistent in what Nvim thinks is a semver
  string.

  This is technically not a breaking change since it was documented that
  only tags like `v<major>.<minor>.<patch>` will be recognized as
  semver.
2026-04-23 11:14:06 -04:00
..
2026-04-01 07:59:51 +08:00
2026-04-16 10:48:11 -04:00
2026-04-20 07:09:37 -04:00
2026-02-12 13:46:45 +01:00
2024-05-15 23:19:26 +02:00
2026-04-18 15:38:59 -04:00
2026-04-20 07:09:37 -04:00
2026-04-16 10:48:11 -04:00
2026-04-18 15:38:59 -04:00
2025-12-06 20:33:02 -05:00
2023-06-25 17:14:28 +02:00
2026-04-18 15:38:59 -04:00
2026-01-27 17:14:57 -05:00
2026-04-10 11:08:26 -05:00
2026-04-18 15:38:59 -04:00
2026-03-29 20:53:24 -04:00
2026-04-18 15:38:59 -04:00
2025-12-15 13:55:15 -05:00
2026-03-16 10:29:58 +01:00
2026-02-12 13:46:45 +01:00
2026-04-16 10:48:11 -04:00
2025-09-28 20:57:59 -07:00
2026-03-24 00:14:55 +01:00
2025-12-15 13:55:15 -05:00
2026-04-12 14:17:50 +02:00
2026-03-22 01:57:28 +01:00
2026-04-16 10:48:11 -04:00
2026-04-22 18:25:07 -04:00
2026-03-18 20:40:20 +01:00
2026-01-07 08:11:42 +08:00
2026-03-24 00:14:55 +01:00
2025-12-06 20:33:02 -05:00
2026-04-12 14:17:50 +02:00
2026-04-12 14:17:50 +02:00
2026-03-11 12:39:49 +01:00
2025-12-15 13:55:15 -05:00
2026-04-16 10:48:11 -04:00