Bumps [azure/cli](https://github.com/azure/cli) from 2 to 3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/azure/cli/releases">azure/cli's releases</a>.</em></p> <blockquote> <h2>GitHub Action for Azure CLI v3</h2> <h2>What's Changed</h2> <ul> <li>Updated to use node24 by <a href="https://github.com/thomas-temby"><code>@thomas-temby</code></a> in <a href="https://redirect.github.com/Azure/cli/pull/197">Azure/cli#197</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/Azure/cli/compare/v2.2.0...v3">https://github.com/Azure/cli/compare/v2.2.0...v3</a></p> <h2>GitHub Action for Azure CLI v3.0.0</h2> <h2>What's Changed</h2> <ul> <li>Updated to use node24 by <a href="https://github.com/thomas-temby"><code>@thomas-temby</code></a> in <a href="https://redirect.github.com/Azure/cli/pull/197">Azure/cli#197</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/Azure/cli/compare/v2.2.0...v3.0.0">https://github.com/Azure/cli/compare/v2.2.0...v3.0.0</a></p> <h2>GitHub Action for Azure CLI v2.2.0</h2> <h2>What's Changed</h2> <ul> <li>Mount <code>AZURE_CONFIG_DIR</code> folder instead of <code>~/.azure</code> by <a href="https://github.com/MoChilia"><code>@MoChilia</code></a> in <a href="https://redirect.github.com/Azure/cli/pull/176">Azure/cli#176</a></li> <li>FIX: Broken links by appended dot azcliversion errors by <a href="https://github.com/nselpriv"><code>@nselpriv</code></a> in <a href="https://redirect.github.com/Azure/cli/pull/178">Azure/cli#178</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/nselpriv"><code>@nselpriv</code></a> made their first contribution in <a href="https://redirect.github.com/Azure/cli/pull/178">Azure/cli#178</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/Azure/cli/compare/v2.1.0...v2.2.0">https://github.com/Azure/cli/compare/v2.1.0...v2.2.0</a></p> <h2>GitHub Action for Azure CLI v2.1.0</h2> <h2>What's Changed</h2> <ul> <li>docs: add yaml syntax highlighting to workflow examples by <a href="https://github.com/baysideengineer"><code>@baysideengineer</code></a> in <a href="https://redirect.github.com/Azure/cli/pull/141">Azure/cli#141</a></li> <li>Fix <a href="https://redirect.github.com/azure/cli/issues/153">#153</a>: Prevent stdout cutoff in Azure CLI versions by <a href="https://github.com/MoChilia"><code>@MoChilia</code></a> in <a href="https://redirect.github.com/Azure/cli/pull/154">Azure/cli#154</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/baysideengineer"><code>@baysideengineer</code></a> made their first contribution in <a href="https://redirect.github.com/Azure/cli/pull/141">Azure/cli#141</a></li> <li><a href="https://github.com/isra-fel"><code>@isra-fel</code></a> made their first contribution in <a href="https://redirect.github.com/Azure/cli/pull/151">Azure/cli#151</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/Azure/cli/compare/v2.0.0...v2.1.0">https://github.com/Azure/cli/compare/v2.0.0...v2.1.0</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Azure/cli/blob/master/ReleaseProcess.md">azure/cli's changelog</a>.</em></p> <blockquote> <p><strong>Releasing a new version</strong></p> <p>Semanting versioning is used to release different versions of the action. Following steps are to be followed :</p> <ol> <li>Create a new branch for every major version. <br /> Example, releases/v1, releases/v2.</li> <li>For every minor and patch release for a major version, update the corresponding release branch. <br /> Example, for releasing v1.1.1, update releases/v1.</li> <li>Create tags for every new release (major/minor/patch). <br /> Example,v1.0.0. , v1.0.1, v2.0.1, etc. and also have tags like v1, v2 for every major version release.</li> <li>On releasing minor and patch versions, update the tag of the corresponding major version. <br /> Example, for releasing v1.0.1, update the v1 tag to point to the ref of the current release. <br /> The following commands are to be run on the release\v1 branch so that it picks the latest commit and updates the v1 tag accordingly : (Ensure that you are on same commit locally as you want to release)</li> </ol> <ul> <li><code>git tag -fa v1 -m "Update v1 tag"</code></li> <li><code>git push origin v1 --force</code></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="9eb25b8360"><code>9eb25b8</code></a> Release v3.0.0 (<a href="https://redirect.github.com/azure/cli/issues/199">#199</a>)</li> <li><a href="c1ad80439a"><code>c1ad804</code></a> Add changes (<a href="https://redirect.github.com/azure/cli/issues/198">#198</a>)</li> <li><a href="41fca1b4f8"><code>41fca1b</code></a> Updated to use node24 (<a href="https://redirect.github.com/azure/cli/issues/197">#197</a>)</li> <li><a href="cbea6ec14d"><code>cbea6ec</code></a> change the assignee (<a href="https://redirect.github.com/azure/cli/issues/191">#191</a>)</li> <li>See full diff in <a href="https://github.com/azure/cli/compare/v2...v3">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Microsoft PowerToys
Microsoft PowerToys is a collection of utilities that help you customize Windows and streamline everyday tasks.
Installation · Documentation · Blog · Release notes
🔨 Utilities
PowerToys includes over 25 utilities to help you customize and optimize your Windows experience:
📋 Installation
For detailed installation instructions and system requirements, visit the installation docs.
But to get started quickly, choose one of the installation methods below:
Download .exe from GitHub
Go to the PowerToys GitHub releases, click Assets to reveal the downloads, and choose the installer that matches your architecture and install scope. For most devices, that's the x64 per-user installer.
| Description | Filename |
|---|---|
| Per user - x64 | PowerToysUserSetup-0.98.1-x64.exe |
| Per user - ARM64 | PowerToysUserSetup-0.98.1-arm64.exe |
| Machine wide - x64 | PowerToysSetup-0.98.1-x64.exe |
| Machine wide - ARM64 | PowerToysSetup-0.98.1-arm64.exe |
WinGet
Download PowerToys from WinGet. Updating PowerToys via winget will respect the current PowerToys installation scope. To install PowerToys, run the following command from the command line / PowerShell:
User scope installer [default]
winget install Microsoft.PowerToys -s winget
Machine-wide scope installer
winget install --scope machine Microsoft.PowerToys -s winget
Other methods
There are community driven install methods such as Chocolatey and Scoop. If these are your preferred install solutions, you can find the install instructions there.
✨ What's new?
To see what's new, check out the release notes.
🛣️ Roadmap
We are planning some nice new features and improvements for the next releases – PowerDisplay, Command Palette improvements and a brand-new Shortcut Guide experience! Stay tuned for v0.99!
❤️ PowerToys Community
The PowerToys team is extremely grateful to have the support of an amazing active community. The work you do is incredibly important. PowerToys wouldn't be nearly what it is today without your help filing bugs, updating documentation, guiding the design, or writing features. We want to say thank you and take time to recognize your work. Your contributions and feedback improve PowerToys month after month!
Contributing
This project welcomes contributions of all types. Besides coding features / bug fixes, other ways to assist include spec writing, design, documentation, and finding bugs. We are excited to work with the power user community to build a set of tools for helping you get the most out of Windows. We ask that before you start work on a feature that you would like to contribute, please read our Contributor's Guide. We would be happy to work with you to figure out the best approach, provide guidance and mentorship throughout feature development, and help avoid any wasted or duplicate effort. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you grant us the rights to use your contribution and that you have permission to do so. For guidance on developing for PowerToys, please read the developer docs for a detailed breakdown. This includes how to setup your computer to compile.
Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct.
Privacy Statement
The application logs basic diagnostic data (telemetry). For more privacy information and what we collect, see our PowerToys Data and Privacy documentation.

