windows-release

Summary On Windows Server 2025, returns instead of . This regression was introduced in v7.0.0. In v6.1.0, the correct value was returned. Details returns on both v6.1.0 and v7.0.0+. In v6.1.0, returns . From v7.0.0 onward, returns . Build number 26100 is shared by both Windows 11 24H2 and Windows Server 2025. The function relies on runtime server detection to distinguish between them before falling back to build number-based classification. In v6.1.0, server detection used / , which worked correctly. In v7.0.0+, the server detection method was changed, and it appears to no longer successfully detect Windows Server 2025, causing the function to fall through to the build number check, which classifies build 26100 as Windows 11. Steps to Reproduce 1. Run on a Windows Server 2025 machine (e.g., GitHub Actions ) 2. Call without arguments 3. returns 4. Result: (expected: ) Expected Behavior should return on Windows Server 2025, as it did in v6.1.0. Environment windows-release v7.1.0 Windows Server 2025 (build 26100) :

I know this repo being sync server a purpose, but an async API would be a great addition IMO. Perhaps something like this? WMIC can be veeeery slow in some cases.

I am trying to get the archive link from my node js application.This is working fine in my local machine but i am getting error in azure private app service. octokit.repos.getArchiveLink({owner:owner,repo:sourceRepoName,archive_format:'zipball',ref:branch}) on executing this command in azure private app service I am getting the following error { Error: Command failed: wmic os get Caption Access is denied. at makeError (D:\home\site\wwwroot\node_modules\execa\index.js:172:9) at Function.module.exports.sync (D:\home\site\wwwroot\node_modules\execa\index.js:341:15) at module.exports.release (D:\home\site\wwwroot\node_modules\windows-release\index.js:34:24) at module.exports (D:\home\site\wwwroot\node_modules\os-name\index.js:39:18) at getUserAgentNode (D:\home\site\wwwroot\node_modules\universal-user-agent\index.js:6:51) at restEndpoint (D:\home\site\wwwroot\node_modules@octokit\rest\lib\endpoint\index.js:27:48) at restRequest (D:\home\site\wwwroot\node_modules@octokit\rest\lib\request\index.js:7:26) code: 1, stdout: '', stderr: 'Access is denied.\r\n', failed: true, signal: null, cmd: 'wmic os get Caption', timedOut: false } So on diving deep into the error I noticed that the wmic command in this package is throwing this error. I contacted with azure team and they said that windows commands execution is denied in azure app service. Can you provide any alternative for this as this was working fine when I was using your earlier module 'win-release'.