Skip to content

THRIFT-6473: Raise the WinGet manifest version to 1.28.0 - #4068

Draft
Jens-G wants to merge 1 commit into
apache:masterfrom
Jens-G:THRIFT-6473
Draft

Jens-G wants to merge 1 commit into
apache:masterfrom
Jens-G:THRIFT-6473

Conversation

@Jens-G

@Jens-G Jens-G commented Oct 30, 2026

Copy link
Copy Markdown
Member

THRIFT-6473

Draft until a wingetcreate release supports manifest version 1.28.0. The submit job runs the latest release, 1.12.13.0. Its validation (WinGetUtil 1.12.350) checks a 1.28.0 manifest against the 1.12.0 schema and rejects the $schema comment, by its source; wingetcreate submit then opens no pull request, and the job fails. microsoft/winget-create#711 added 1.28.0 to wingetcreate's main on 2026-10-26; no release has it yet.

winget-pkgs flagged the 0.25.0 submission, microsoft/winget-pkgs#445370, on 2026-10-30: manifest version 1.12.0 is deprecated, and 1.28.0 is to be used instead. The templates here still name 1.12.0, so the 0.26.0 submission would be flagged the same way. The manifests in that pull request have been moved to 1.28.0 on its branch.

Changes

  • The three templates in build/windows/winget/: ManifestVersion and the $schema comment move to 1.28.0. No field changes: of the three schemas the package uses, only the installer schema gains a field between 1.12.0 and 1.28.0, the optional DesiredStateConfiguration, which the package does not use.
  • test-winget-manifests.ps1 checks that each $schema comment names the type and version of the manifest under it, and that the three manifests share one version. WinGet's validation rejects a manifest whose comment and fields disagree, so a bump that misses one of the six lines now fails here first.
  • build/windows/README.md: where the version is set, and to raise it only to a version the latest wingetcreate release knows.

Verification

  • All 28 checks of test-winget-manifests.ps1 pass, on master's templates and on the raised ones (24 before this change). With only ManifestVersion raised in Apache.Thrift.yaml.in, two checks fail; with only the installer's $schema comment raised, one fails.
  • Rendered for 0.25.0 with -InstallerSource github, the three manifests pass validate_manifests.py against the WinGet 1.28.0 schemas. Parsed, they match the manifests now in Apache.Thrift version 0.25.0 microsoft/winget-pkgs#445370, apart from MinimumVersion: '14.51' (THRIFT-6401, which came after that submission).
  • The wingetcreate point above is read from the sources of wingetcreate v1.12.13.0 and winget-cli v1.12.350, not run: wingetcreate needs Windows.

🤖 Generated with Claude Code

Client: build

winget-pkgs flags manifest version 1.12.0 as deprecated and asks for
1.28.0, as it did for the 0.25.0 submission. The three templates move
to 1.28.0, in ManifestVersion and in the $schema comment. No field
changes: of the three schemas the package uses, only the installer
schema gains a field, the optional DesiredStateConfiguration, which
the package does not use.

test-winget-manifests.ps1 now checks that each $schema comment names
the type and version of the manifest under it, and that the three
manifests share one version, as WinGet's own validation requires.
build/windows/README.md says where the version is set and what to
check before raising it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mergeable mergeable Bot added the build and general CI cmake, automake and build system changes label Oct 30, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build and general CI cmake, automake and build system changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant