#273 WinGet still ships v5.0 with GPL-3.0 metadata while the project is Apache-2.0 since v5.1

[Anonymous]

Originally created by: Platonenkov

Not a bug in the code — a distribution-metadata lag that currently gives installers a confusing picture.

What a fresh user sees today

• README (master) badges the project Apache-2.0 and documents v5.1 features (--hide-secrets, devprojex mcp, …).
• winget install OlimoffDev.DevProjex delivers 5.0.0.0, and winget show says License: GPL-3.0-only with a license URL pinned to blob/v5.0/LICENSE.
• So the installed CLI is missing the flags the README teaches (error[DPX-CLI-UNKNOWN-OPTION]: --hide-secrets), and the user holds a GPL build of a project whose homepage says Apache — both true at once, but nothing explains why.

The relicense itself is fine and clearly documented in the v5.1 release notes ("Changed the project license from GPL-3.0 to the Apache License 2.0").

Suggestion

1. Publish v5.1 to the winget-pkgs repo when convenient — and when doing so, remember the manifest's License/LicenseUrl fields need the Apache-2.0 values (easy to carry the old ones forward by habit).
2. Until then, one line in README's install section ("winget currently carries v5.0/GPL-3.0; the features above require v5.1 from Releases or the Store") would spare the next person the puzzle.
3. Worth checking the Microsoft Store listing's license metadata for the same lag when 5.1 ships there.

For what it's worth: v5.1's SHA256SUMS.txt matched the downloaded DevProjex.v5.1.win-x64.exe exactly — the release-integrity side of the pipeline works nicely.

[Anonymous]

Originally posted by: Avazbek22

Thanks for reporting this. The WinGet update for v5.1 has already been submitted:

• microsoft/winget-pkgs#428203

It updates the package to 5.1.0.0 and changes the license metadata and URL to Apache-2.0. Manifest validation has passed; the PR is awaiting review and merge.