Bump manifest version to 1.30

[Trenly]

📖 Description

Bumps the manifest version to 1.30, checkpointing the 1.28 manifests for use with the community repository. Used the new checkpoint script from #6280 and then had copilot add the AppInstallerCLITests

🔗 References

• Add manifest schema 1.28.0 documentation winget-pkgs#397446

🔍 Validation

Built and ran tests locally

✅ Checklist

• Signed the Contributor License Agreement
• Linked to an issue
• Updated Release Notes (if applicable)
• Updated documentation (if applicable)
• Updated Copilot instructions (if build, architecture, or conventions changed)

📋 Issue Type

• Bug fix
• Feature
• Task

Microsoft Reviewers: Open in CodeFlow

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[florelis]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[florelis]

Do you have any manifest changes in mind for 1.30? I can only think of the other PR for adding some patterns to the schema.

[Trenly]

Do you have any manifest changes in mind for 1.30? I can only think of the other PR for adding some patterns to the schema.

I have a few in mind such as adding additional ARP entries for better correlation, or a new installer switch specifically for agreements (such as when a package requires --accept-eula to install silently). However, the main factor for this PR was the desire to have 1.28 manifests checkpointed so they could be referenced at pkgs without latest breaking them as support for v1.28 manifests rolls out to the community repo.

If it's determined that v1.30 will have no manifest changes, this PR becomes an easy reference for a symbol change from 1.30.0 to 1.31.0 or whatever the next version ends up being that touches the schema

Regardless, before taking on too many other changes, I'd like to work some of my other PRs through reviews and either merge or closure just so that there is less to keep track of and fewer drains on the engineering time required to manage the PR backlog