Release Planning: 7.5.3

[sirosen]

Update 2026-02-11:
v7.5.3 has shipped. Any follow-up discussion can happen here: #2333

Update 2026-02-10:
Our release workflow hit a snag, so we're going to need to retrigger the release as soon as we get it fixed.

Update 2026-02-09:
We had one additional bug come in at the last minute (#2325), which is getting fixed before we do the release, but we're otherwise ready.

---

We now have some valuable fixes in main, and I'd like to cut v7.5.3 with what we have.
I intend to move any unsolved issues to a new 7.5.4 milestone.

There are two items I see as needing confirmation:

• With 📝 Add highlights & afterword to Towncrier #2322 now on track, do we have highlights or an afterword to include?
• Any final items we want to address before release?

[sirosen]

We're going to include #2255

[sirosen]

I've moved the following issues to 7.5.4:

• [regression][6.10.0] pip-compile hangs on named pipes as input due to double-read #2232
• Refactor CI config such that a "run tests" reusable workflow contains one parametrizable job #2244
• Introduce an initial LLM Usage Policy #2318

[sirosen]

@webknjaz , I'd like to include #2257 . It's the last item in 7.5.3 .

Would you like me to pick it up for any changes which are needed? The only thing that I think we need to do is update it to say <= 26.0.

[webknjaz]

Yeah. Although, I was imagining it as a more complex change, integrating multiple ecosystems with a single source of truth.

[sirosen]

Oh! I wasn't clear on whether or not you wanted to do the initial change to add the extra separately.
I don't want to rush it. Why don't we let it sit for one more release cycle? We can do it in 7.5.4 no problem.

[webknjaz]

I'm fine with just adding the extra in 7.5.3. However, this would mean that the full integration must not be moved off of 7.5.4 (otherwise, this would mean extra manual work + potential for human error).

[webknjaz]

I suppose if we get to have an extra in this release, that could be mentioned in highlights. But no additional comments off the top of my head.

[sirosen]

👍 I agree. I tried to write a highlights PR and then I discarded it because nothing seemed worth calling out in addition to the normal changelog showing what we did. Per above, we can decide on the extra -- if we do include it, I think it's worth putting in highlights.

[webknjaz]

🔔 Notify upon release:

• chore(deps): bump pip from 25.3 to 26.0.1 pypi/warehouse#19467
• pip-tools: bump python resources Homebrew/homebrew-core#266530

[sirosen]

With #2333 open now for any follow-up discussion of the release, I'm going to close this.

I'll also create a v7.5.4 discussion. I'd like to try always having a "Release Planning" discussion open.

[webknjaz]

@sirosen let's also replace pinned discussions when we do this.