1.15 Release Tracking Issue

[wesleywright]

I'll be cutting a new release branch today with a tentative goal of releasing in the next couple of weeks. Please share any tickets that you'd like to make sure are included in this release!

Tickets to include (planning to branch off from at least c4e2eb7):

• [regression] isinstance complains about parametrized generics with any use of TypeAlias #18488
• [stubgen] Improve dataclass init signatures #18430
• Walk up for all config files and handle precedence #18482
• Fix literal context for ternary expressions (for real) #18545
• Prevent crash on generic NamedTuple with unresolved typevar bound #18585

[wesleywright]

#18488 seems like a regression, detected while dogfooding latest master on Dropbox's internal Python repo

[cdce8p]

It would be great if #18430 could be included. It fits well with the other dataclass / dataclass_transform improvements in stubgen this cycle.

[hauntsaninja]

Very excited for this release! Would be good for #18482 to be merged

[wesleywright]

I caught a few dozen errors when dogfooding against Dropbox's internal Python codebase, so cutting the release branch is taking a little while; I'm hoping I can do it by today or tomorrow.

[wesleywright]

I cut release-1.15 from commit 68cffa7 (which should include #18430). Will cherry pick any other PRs as they land.

[wesleywright]

Cherry picked #18482.

[wesleywright]

Cherry picked #18512, so all relevant tickets are now cherry picked. We still need to dogfood this release for a few more days within Dropbox before release; if anyone else has more tickets to request, please feel free to chime in :-)

[Dreamsorcerer]

#18545 would be great for us.

[wesleywright]

cherry picked 16e19f8 to release branch

[wesleywright]

I'm going to let the changes bake for another few days on Dropbox's internal code base to check for any last issues while I prepare the changelog. I'm aiming to publish the final release early next week.

[wesleywright]

Changelog updates (which will also be used for the official release blogpost) are up for review at #18583. Please let me know if you spot any issues :-)

[hauntsaninja]

Could be good to cherry pick #18585 . It fixes a crash that has a dozen +1's

[wesleywright]

#18585 is a good call; I left a comment on that PR about cherry-picking it: #18585 (comment)