When bugs that are fixed on canary are included in a stable version

[jakub-vaillant]

Summary

As in the title - there is a bug with tildes in chunks filenames #91832 that was merged into canary 3 weeks ago, but the current stable version from yesterday still doesn't include it. I don't know what's the approach in deploying such changes, and when should I expect this to be included. There is a vulnerability in nextjs that I can't overcome, because upgrading the nextjs version breaks the whole app due to the mentioned issue.

Additional information

No response

Example

No response

[icyJoseph]

That particular fix is not in any stable.

Patch releases are made by cherry-picking from canary, and adapting if necessary, code into the version release branch. That PR changed 500+ files, I don't know how plausible cherry-picking really is. I think in those cases, a patch can be cut from canary, but you know, we have to make sure it conforms with SEMVER.

I really wish Github's UI was more consistent. For some PR's it shows where they are included. However if applying a fix to the release branch, causes different git hashes, then yeah I guess, you wouldn't know from the original PR. I have a local project I could publish to to this, but yeah, it just feels like Github really needs to step up their game here.

Anyway, I do git tag --contains <hash>, but one can also look at: https://github.com/vercel/next.js/releases/tag/v16.2.4

[jakub-vaillant]

Yes, I checked these 2-3 recent patch versions with these descriptions, didn't see this ticket, that's why I posted this question. I'm aware that it's not yet there, I'm more asking WHEN can I expect it to be live, I guess I should wait for 16.3.0 instead of another patch versions?