On November 10 the PowerShell team released 7.7.0, built on .NET 11, together with 7.6.10 for the 7.6 LTS line. The same day, 7.4 and 7.5 went out of support (see PowerShell 7.4 and 7.5 Retire on November 10).

On Friday evening a mail from Microsoft Azure came in: “Retirement notice: Migrate from Azure Blueprints by 31 January 2027”. It came through my own Service Health alert on my demo subscription, which surprised me: as far as I remembered, I never got round to using Blueprints.

Third roundup of the year, covering August and September, plus what October brought so far: three patch waves and the first 7.7 release candidate. The previous one ran up to the end of July. Pester had a busy summer too, with two feature releases in five weeks — more on that below.

A short public service announcement: PowerShell 7.4 (LTS) and PowerShell 7.5 both reach end of support on November 10, 2026. That’s less than two weeks from now, and as far as I can find there’s no PowerShell team blog post reminding anyone. So here’s one.

Not everyone can make it to PowerShell Conference Europe in person, and June is a long way off for the rest of the year. That’s what the PSConfEU MiniCon is for: a free, online, one-day edition. This year’s MiniCon is next week, on Tuesday, October 13.

Pester 6.2.0 was released on September 9 — the third feature release in the Pester 6 line in just over two months. The headline is setup files that apply per folder, but a few of the smaller changes might matter more to you day to day, including one that reverses a 6.0 breaking change.