🔗 Linked issue

Resolves #1789

🧭 Context

When expanding a dist-tag row, versions newer than the dist-tag version could be silently dropped when the dist-tag does not point to the latest version in its major.

📚 Description

Taking @types/node as an example, ts5.1 -> 24.1.0, but the latest 24.x is 24.11.0.

channelVersions is sorted by semver descending, so [0] is always the newest version in the channel, not the dist-tag version:

tagVersions['ts5.1'] = [
  { version: '24.11.0' },  // newest, but NOT the dist-tag version
  { version: '24.10.15' },
  ...
  { version: '24.1.0' },   // actual dist-tag version, shown in row header
]

The old code used .slice(1) to exclude the primary version from the expanded list, assuming [0] was always the primary version. This assumption only holds when the dist-tag points to the latest version in its major.

The fix replaces getFilteredTagVersions + .slice(1) with getExpandedTagVersions, which filters out the primary version by version string match instead of by array position.

Before	After