You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Automate dependency maintenance and prepare WinGet submission - #24
Cover NuGet projects, GitHub Actions, and the pinned .NET SDK with Dependabot, lock files, grouped critical package updates, dependency review, and CodeQL (including Dependabot PRs).
Monitor Terminal.Gui develop prereleases and WinGet stable/preview releases; create assigned, deduplicated issues with compatibility checks and Copilot review prompts.
Gate releases on tag/version validation, tests, x64/ARM64 AOT builds, required COM files, signing configuration, checksums, and provenance attestations. Reject reruns of published tags and prevent asset overwrites.
Publish the portable ZIPs as the initial WinGet package. Download the released ZIP bytes before generating the three-file community manifest set.
Document the current ZIP signing status, later signed MSIX path, Azure Artifact Signing setup, PATH behavior, and one-command manifest preparation.
Validation
311 .NET tests passed in the earlier PR update.
Node dependency-monitor test, actionlint, PowerShell script parse, and diff checks passed for this update.
Windows ARM64 and x64 Native AOT publish, COM companion checks, and mock startup passed in CI before this update.
winget validate accepted a generated manifest set from synthetic ZIP assets in the earlier PR update.
After merge
Cut a new versioned release. Its successful workflow run will provide winget-manifests-<version>; packaging/prepare-winget-submission.ps1 can regenerate the same manifest set from the published ZIPs. Test install, upgrade, and uninstall in Windows Sandbox before submitting the YAML files to microsoft/winget-pkgs.
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.
What Enabling Code Scanning Means:
The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.
For more information about GitHub Code Scanning, check out the documentation.
This guard skips both CodeQL analyses on every Dependabot PR, including Actions updates. GitHub permits SARIF uploads from pull_request runs with Dependabot's read-only token; the push-event restriction does not apply here. Allow pull-request runs through the guard so dependency updates receive security analysis before merging.
The reason will be displayed to describe this comment to others. Learn more.
Warning
Copilot's review of this pull request may be incomplete because some of the changed files are excluded by your Copilot content exclusion settings. See Excluding content from Copilot for details.
Copilot review overview
🟡 Changes recommended
Release publication and draft recovery remain unsafe, and MSIX builds bypass locked dependency restoration.
The reason will be displayed to describe this comment to others. Learn more.
Warning
Copilot's review of this pull request may be incomplete because some of the changed files are excluded by your Copilot content exclusion settings. See Excluding content from Copilot for details.
Copilot review overview
🔵 Needs a closer look
Release publication, signing, and WinGet installation and upgrade behavior need final human validation on Windows.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Validation
winget validateaccepted a generated manifest set from synthetic ZIP assets in the earlier PR update.After merge
Cut a new versioned release. Its successful workflow run will provide
winget-manifests-<version>;packaging/prepare-winget-submission.ps1can regenerate the same manifest set from the published ZIPs. Test install, upgrade, and uninstall in Windows Sandbox before submitting the YAML files to microsoft/winget-pkgs.