fix(ui): respect semver filter when showing latest tag

The 'latest' tag was unconditionally added to visible results even when
it didn't match the active semver filter. This caused versions like 7.6.0
to appear when filtering by ranges like '^7.5 <7.6'.

Remove the special case handling for the 'latest' tag and let it flow
naturally through the filtering logic. This makes the behavior more
predictable and fixes the bug where non-matching versions were displayed.

Author: joshuaisaact

app/components/Package/Versions.vue

@@ -210,14 +210,7 @@ const visibleTagRows = computed(() => {
           getTagVersions(row.tag).some(v => filteredVersionSet.value.has(v.version)),
       )
     : rowsMaybeFilteredForDeprecation
-  const first = rows.slice(0, MAX_VISIBLE_TAGS)
-  const latestTagRow = rows.find(row => row.tag === 'latest')
-  // Ensure 'latest' tag is always included (at the end) if not already present
-  if (latestTagRow && !first.includes(latestTagRow)) {
-    first.pop()
-    first.push(latestTagRow)
-  }
-  return first
+  return rows.slice(0, MAX_VISIBLE_TAGS)
 })
 
 // Hidden tag rows (all other tags) - shown in "Other versions"

test/nuxt/components/Package/Versions.spec.ts

@@ -1281,6 +1281,21 @@ describe('PackageVersions', () => {
         expect(text).not.toContain('0.5.0')
       })
     })
+
+    it('does not show latest tag when it does not match the filter', async () => {
+      const component = await mountSuspended(PackageVersions, { props: multiVersionProps })
+
+      const input = component.find('input[type="text"]')
+      await input.setValue('^1.0.0 <2.0.0')
+
+      const versionLinks = component.findAll('a').filter(isVersionLink)
+      const versions = versionLinks.map(l => l.text())
+
+      // 3.0.0 is latest but does NOT match the filter
+      expect(versions).not.toContain('3.0.0')
+      // 1.0.0 does match
+      expect(versions).toContain('1.0.0')
+    })
   })
 
   describe('error handling', () => {