ESR release notes link leads to 115, not 128

[martinbalfanz]

Description

When clicking the 'Release notes' link on https://www.mozilla.org/en-US/firefox/all/desktop-esr/ it sends me to the release notes of ESR 115 instead of ESR 128.

Steps to reproduce

• visit https://www.mozilla.org/en-US/firefox/all/desktop-esr/
• click 'Release notes' link

Expected result

I should see the release notes of the latest ESR (128)

Actual result

I see the release notes of ESR 115

Environment

Firefox Nightly 140 on OS X 15.5

[janbrasna]

This is interesting, might be due to the fact 115.x was shipped later on that channel than 128.x:

  "name": "Firefox-115.23.1esr-build1",
    "shippedAt": "2025-05-17T21:27:32.056369+00:00",
    "submittedAt": "2025-05-17T17:36:28.834908+00:00"

  "name": "Firefox-128.10.1esr-build1",
    "shippedAt": "2025-05-17T21:14:51.496456+00:00",
    "submittedAt": "2025-05-17T17:51:27.793386+00:00"

I'll look into how the "latest" is evaluated. (It's the same for system requirements etc.)

[janbrasna]

Funnily enough the site knows what's the latest version:

That one (used for outdated info, bouncer links etc.) comes from product-details data:

bedrock/bedrock/security/views.py

Line 50 in 817d07c

latest_version = product_details.firefox_versions["FIREFOX_ESR"]

The latest release for a channel to display for release-notes however comes from:

bedrock/bedrock/releasenotes/models.py

Lines 164 to 173 in 817d07c

	class ProductReleaseQuerySet(models.QuerySet):
	def product(self, product_name, channel_name=None, version=None):
	if product_name.lower() == "firefox extended support release":
	product_name = "firefox"
	channel_name = "esr"
	q = self.filter(product__iexact=product_name)
	if channel_name:
	q = q.filter(channel__iexact=channel_name)
	if version:
	q = q.filter(version=version)

and that, IIUC, would just draw the latest note published for a channel, and not differentiate between esr, esr-next, or esr-115 … 👀

[stevejalim]

@martinbalfanz @pascalchevrel This is fixed now and in production. Please let us know if there are any issues or other examples of unexpected behaviour.

Thanks for reporting @martinbalfanz!