Adjust upstream version filtering to allow Rapid Releases again

[tianon]

Also, remove 6.0 as it's now EOL upstream (and encode explicit EOL dates into the update logic so they can be automatically applied over time).

See also:

• https://www.mongodb.com/docs/manual/reference/versioning/#std-label-release-version-numbers
  • especially:

    Starting with MongoDB 8.2, minor releases will also be available for on-premises deployments (MongoDB Community and Enterprise) for specific use cases, such as Search, Vector Search, and enhanced Queryable Encryption capabilities.

• https://www.mongodb.com/docs/manual/release-notes/8.2/
  • especially:

    Starting with MongoDB 8.2, minor releases are available for on-premises deployments (MongoDB Community and Enterprise) for specific use cases.

• https://www.mongodb.com/legal/support-policy/lifecycles (EOL dates)

[tianon]

Diff:

$ diff -u <(bashbrew cat mongo) <(bashbrew cat <(./generate-stackbrew-library.sh))
--- /dev/fd/63	2025-10-27 13:50:39.728153551 -0700
+++ /dev/fd/62	2025-10-27 13:50:39.728153551 -0700
@@ -1,6 +1,33 @@
 Maintainers: Tianon Gravi <[email protected]> (@tianon), Joseph Ferguson <[email protected]> (@yosifkit)
 GitRepo: https://github.com/docker-library/mongo.git
 
+Tags: 8.2.1-noble, 8.2-noble
+SharedTags: 8.2.1, 8.2
+Architectures: amd64, arm64v8
+GitCommit: 930645872a8eb6651cb1a27bfda9e0500c58fbfd
+Directory: 8.2
+
+Tags: 8.2.1-windowsservercore-ltsc2025, 8.2-windowsservercore-ltsc2025
+SharedTags: 8.2.1-windowsservercore, 8.2-windowsservercore, 8.2.1, 8.2
+Architectures: windows-amd64
+GitCommit: 930645872a8eb6651cb1a27bfda9e0500c58fbfd
+Directory: 8.2/windows/windowsservercore-ltsc2025
+Constraints: windowsservercore-ltsc2025
+
+Tags: 8.2.1-windowsservercore-ltsc2022, 8.2-windowsservercore-ltsc2022
+SharedTags: 8.2.1-windowsservercore, 8.2-windowsservercore, 8.2.1, 8.2
+Architectures: windows-amd64
+GitCommit: 930645872a8eb6651cb1a27bfda9e0500c58fbfd
+Directory: 8.2/windows/windowsservercore-ltsc2022
+Constraints: windowsservercore-ltsc2022
+
+Tags: 8.2.1-nanoserver-ltsc2022, 8.2-nanoserver-ltsc2022
+SharedTags: 8.2.1-nanoserver, 8.2-nanoserver
+Architectures: windows-amd64
+GitCommit: 930645872a8eb6651cb1a27bfda9e0500c58fbfd
+Directory: 8.2/windows/nanoserver-ltsc2022
+Constraints: nanoserver-ltsc2022, windowsservercore-ltsc2022
+
 Tags: 8.0.15-noble, 8.0-noble, 8-noble, noble
 SharedTags: 8.0.15, 8.0, 8, latest
 Architectures: amd64, arm64v8
@@ -54,30 +81,3 @@
 GitCommit: d828bd4b9677891b7b4a5a2259d939f7a5cb3377
 Directory: 7.0/windows/nanoserver-ltsc2022
 Constraints: nanoserver-ltsc2022, windowsservercore-ltsc2022
-
-Tags: 6.0.26-jammy, 6.0-jammy, 6-jammy
-SharedTags: 6.0.26, 6.0, 6
-Architectures: amd64, arm64v8
-GitCommit: d9efcb7f46c4a17da2fdc9dbb4ef644f4f92053d
-Directory: 6.0
-
-Tags: 6.0.26-windowsservercore-ltsc2025, 6.0-windowsservercore-ltsc2025, 6-windowsservercore-ltsc2025
-SharedTags: 6.0.26-windowsservercore, 6.0-windowsservercore, 6-windowsservercore, 6.0.26, 6.0, 6
-Architectures: windows-amd64
-GitCommit: 0bd4b9bbe4bb9b85a56b851516a6c36a4629743b
-Directory: 6.0/windows/windowsservercore-ltsc2025
-Constraints: windowsservercore-ltsc2025
-
-Tags: 6.0.26-windowsservercore-ltsc2022, 6.0-windowsservercore-ltsc2022, 6-windowsservercore-ltsc2022
-SharedTags: 6.0.26-windowsservercore, 6.0-windowsservercore, 6-windowsservercore, 6.0.26, 6.0, 6
-Architectures: windows-amd64
-GitCommit: 0bd4b9bbe4bb9b85a56b851516a6c36a4629743b
-Directory: 6.0/windows/windowsservercore-ltsc2022
-Constraints: windowsservercore-ltsc2022
-
-Tags: 6.0.26-nanoserver-ltsc2022, 6.0-nanoserver-ltsc2022, 6-nanoserver-ltsc2022
-SharedTags: 6.0.26-nanoserver, 6.0-nanoserver, 6-nanoserver
-Architectures: windows-amd64
-GitCommit: 0bd4b9bbe4bb9b85a56b851516a6c36a4629743b
-Directory: 6.0/windows/nanoserver-ltsc2022
-Constraints: nanoserver-ltsc2022, windowsservercore-ltsc2022

[tianon]

So the real Question Of The Day is whether latest should point to 8.2 now.

[yosifkit]

So the real Question Of The Day is whether latest should point to 8.2 now.

Given that https://www.mongodb.com/docs/manual/release-notes/ calls it the "Current Stable release" versus the "Current Major Release" of 8.0, I'd say yes, it should be latest.