but i'll ask @careful-area-84205 whether he is seeing significant release blockers that we might want to avoid cutting 1.26.0 before fixing

@hundreds-father-404 I’ll give you an update by Friday, thanks

might be good to call it EOD Thursday, so that he can cut Friday if need be

Hm, we ideally would release 1.26.0 before Friday so that I can remove the 1.27.0.dev0 deprecations well before I get to CA. Ideally, I’d love to release 1.26.0rc0 tomorrow or even today It’s fine if there are some release blockers in the rc, right? (Although not ideal)

just depends how large. but yea. the sooner the better

ok, I’ll give you an update by end of today to see how many validations are failing and how big they are.

Thank you Patrick!

🚢

Thank you!

fwiw, docs are always rendered from master, so they don’t block releases, i don’t think

True, but I want to send a dedicated email around the time of 1.26.0.rc0 about how to migrate to TOML + maybe mention it in the 1.26.x release notes page

Hi @hundreds-father-404, please go ahead and cut 1.26.rc. (our internal night ci doesn’t pass some validations, but it doesn’t seem like they’re big issues)

Thank you Patrick!