PowerShell

Microsoft's DSC v3.4.0-preview.2 just dropped hot 2 days ago, and oh boy, what a big list: github.com/PowerShell/DSC/releases/tag/v3.4.0-pre… Shoutout to Steve and Mikey for the amazing work they did! #dsc #microsoftdsc #configurationmanagement

Microsoft's DSC v3.4.0-preview.2 just dropped hot 2 days ago, and oh boy, what a big list: github.com/PowerShell/DSC/releases/tag/v3.4.0-pre… Shoutout to @Steve_MSFT and Mikey for the amazing work they did! #dsc #microsoftdsc #configurationmanagement

Syntax highlighting for PS7's null operators in VS Code I saw a comment on here earlier today about VS Code's syntax highlighting for PowerShell not being able to properly color PowerShell 7's null operators: ??, ??=, ?., and ?[]. I had never noticed this before because I've never even tried to do that, but it turns out that there is not built-in tokenization for these operators despite a 7 year old issue on the topic. I'd never written a VS Code extension before and this seemed like a fairly easy first task, so I wrote a small MIT-licensed extension that allows you to add syntax highlighting to these operators. Source code on GitHub here, install it from the VS Marketplace here. Was pretty fun to build, though I don't know how practical it'll be for me since I use pretty minimal syntax highlighting personally. But I got to learn how to build and publish a VS Code extension and I'm considering tackling that GitHub issue and getting this functionality into the official highlighter. No promises though lol --- I did use an LLM to help me find documentation, fix some errors in my JSON, and remind me how to write regex lookbehinds. I didn't use any agent system to write or publish the extension or documentation for me.

... this seems to be the fault of pkgs.unstable.powershell. This is the relevant part of my overlay.nix: [ # powershellOverlay (final: prev: let __pwsh_profile = final.writeText "FIRST" '' # this file is managed by Nix # see the below file vv to make edits . /etc/net.helpimnotdrowning/pwsh/profile.ps1 ''; __pwsh_version = "7.6.7"; in { powershell = prev.powershell.overrideAttrs(old: rec { version = __pwsh_version; passthru.shellPath = old.passthru.shellPath; passthru.sources.x86_64-linux = prev.fetchurl { url = "https://github.com/PowerShell/PowerShell/releases/download/v${__pwsh_version}/powershell-${__pwsh_version}-linux-x64.tar.gz"; hash = "sha256-aJb546awo1S/Rwg1qW2nbS+AHNUNzwR618RWO/k79DE="; }; src = passthru.sources.x86_64-linux; postInstall = (old.postInstall or "") + '' install -Dm444 ${__pwsh_profile} $out/share/powershell/profile.ps1 ''; }); }) ] Using pkgs.powershell instead of pkgs.unstable.powershell (they are both overlayed) in my configuration.nix makes all of the issues go away. The PowerShell definition does take curl as an input (which would have been unstable's curl), but wouldn't nix/git/qemu/etc all use their appropriate curls instead of taking PowerShell's ? Do I misunderstand how this is supposed to work?

PowerShell: PowerShell for every system | GitHub Curated Picks | 2026-10-26 Chapters: 00:00 2026-10-26 | GitHub Curated Picks 00:05 Pick #1 PowerShell GitHub Curated Picks reviews 1 source-verified repositories selected for developer usefulness, not popularity position. Each pick is checked against its GitHub repository, README, release evidence, and recent commit; pick numbers are editorial order. The compact card keeps rank, signal, why it matters, and next check together while the ledger preserves direct URLs and release evidence. Treat the list as an educational review surface, not software endorsement, and verify license and maintenance before adoption. Published: 2026-10-26 Review window: daily Curated repository picks: - Pick #1 PowerShell | v7.6.9 Release of PowerShell | Update metadata.json for PowerShell releases (reference 28259) | PowerShell/PowerShell Chapters: 00:00 2026-10-26 | GitHub Curated Picks 00:05 Pick #1 PowerShell 00:28 Educational Use Only Top comment prompt: Which repository would you verify first, and what release or commit evidence matters most? Source ledger: Direct source URLs: - github.com/trending - api.github.com - github.com/PowerShell/PowerShell/blob/master/READ… - github.com/PowerShell/PowerShell/releases/tag/v7.… - github.com/PowerShell/PowerShell/commit/dad69345f… - PowerShell/PowerShell Informational and educational purposes only. Not investment advice, product endorsement, or professional guidance. Subscriber reason: Subscribe for the daily AI, GitHub, and market board. Tomorrow watchlist: Tomorrow, check the next tagged release, recent commit, and issue-health signals for the selected projects.

The paint on PowerShell release 7.6.8 had barely dried before v7.6.9 came along to replace it github.com/PowerShell/PowerShell/releases/tag/v7.…

Immich: High performance self-hosted photo; PowerShell | GitHub Curated Picks | 2026-10-22 Chapters: 00:00 2026-10-22 | GitHub Curated Picks 00:05 Pick #1 Immich 00:21 Pick #2 Go Whatsapp Web Multidevice 00:37 Pick #3 PowerShell 00:57 Pick #4 Megatron LM GitHub Curated Picks reviews 4 source-verified repositories selected for developer usefulness, not popularity position. Each pick is checked against its GitHub repository, README, release evidence, and recent commit; pick numbers are editorial order. The compact card keeps rank, signal, why it matters, and next check together while the ledger preserves direct URLs and release evidence. Treat the list as an educational review surface, not software endorsement, and verify license and maintenance before adoption. Published: 2026-10-22 Review window: daily Curated repository picks: - Pick #1 Immich | Latest commit | fix(mobile): keep header image when starting selection (reference 32356) | immich-app/immich - Pick #2 Go Whatsapp Web Multidevice | Latest commit | feat(cmd): add version command that prints only the version (reference | aldinokemal/go-whatsapp-web-multidevice - Pick #3 PowerShell | Latest commit | Localized file check-in by OneLocBuild Task: Build definition ID | PowerShell/PowerShell - Pick #4 Megatron LM | Latest commit | fix(ssm): batch-invariant Mamba decode without a z replay buffer | NVIDIA/Megatron-LM Chapters: 00:00 2026-10-22 | GitHub Curated Picks 00:05 Pick #1 Immich 00:21 Pick #2 Go Whatsapp Web Multidevice 00:37 Pick #3 PowerShell 00:57 Pick #4 Megatron LM 01:11 Watch Next 01:19 Educational Use Only Top comment prompt: Which repository would you verify first, and what release or commit evidence matters most? Source ledger: Direct source URLs: - github.com/trending - api.github.com - immich-app/immich - github.com/immich-app/immich/releases/tag/v3.3.5 - github.com/immich-app/immich/commit/745bdd2edf72c… - api.github.com - aldinokemal/go-whatsapp-web-multidevice - github.com/aldinokemal/go-whatsapp-web-multidevic… - github.com/aldinokemal/go-whatsapp-web-multidevic… - api.github.com - PowerShell/PowerShell - github.com/PowerShell/PowerShell/releases/tag/v7.… - github.com/PowerShell/PowerShell/commit/7962a6ae1… - api.github.com - github.com/NVIDIA/Megatron-LM/blob/main/README.md - github.com/NVIDIA/Megatron-LM/releases/tag/core_v… - github.com/NVIDIA/Megatron-LM/commit/aa46a5722999… - NVIDIA/Megatron-LM Informational and educational purposes only. Not investment advice, product endorsement, or professional guidance. Subscriber reason: Subscribe for the daily AI, GitHub, and market board. Tomorrow watchlist: Tomorrow, check the next tagged release, recent commit, and issue-health signals for the selected projects.

PowerShell 7.6.8 is released on GitHub and will be available via WinGet soon. It's a maintenance release that moves the .NET SDK to 10.0.402 and somewhat ironically removes the update notification feature from PowerShell, per customer feedback. 🗣️ 💾

PowerShell 7.6.8 is released on GitHub and will be available via WinGet soon. It's a maintenance release that moves the .NET SDK to 10.0.402 and somewhat ironically removes the update notification feature from PowerShell, per customer feedback. 🗣️ 💾 github.com/PowerShell/PowerShell/releases/tag/v7.…

You are aware that there exist people who can want the opposite? You can ask AI now to do it for you, you can probably find easily something somebody already did. It would have been nice if MS offered something that people can choose to install, but its far from a deal breaker like you seem to make it to be. There is nothing to test, you want collection of aliases, that is trivial. FWIW, they tried some things like PowerShell/Crescendo