Sam Ko

@PatNeedham I think we're missing the test from the previous → https://github.com/Leonils/next.js/blob/697f99e1fd9d9e8bd3728e0872deb5dfcadeff5d/test/e2e/opentelemetry/opentelemetry.test.ts

@PatNeedham I can confirm the previously failed run were test flakes so that's fine (the Next.js team needs to fix this separately, but not blocking). No need to merge canary...

@zenzen-sol This is likely because the headers size was limited, so `next/font` was taking precedence. We expanded these headers → - https://github.com/vercel/next.js/releases/tag/v15.0.0-canary.99 - https://github.com/vercel/next.js/pull/67715 I am taking a look to...

@zenzen-sol Despite the headers size increase, I only see the `next-intl`'s link headers, which probably makes sense (React calculates what is the best items to add to the link headers)....

@zenzen-sol I am also seeing that on `next dev`. I think what is probably happening is these `i18n` headers are working differently in `next build`. (locally using `next build`, it...

@amannn Thank you for the clarification! I should have also checked `next-intl` when `next/font` wasn't present. When `next/font` isn't present, the `next-intl` Link Headers do show up in `next dev`....

@amannn There are still plans to fix this, we just did not get to this issue yet! We will get back to you when we have an update on this.

@neefrehman I am not seeing `null` in development. 

@brrock Taking a look!

@brrock Looks like there are still merge conflicts!