Add gitlab-runner

[zanseb]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• Have you validated your manifest locally with winget validate <manifest>, where <manifest> is the name of the manifest you're submitting?
• Have you tested your manifest locally with winget install -m <manifest>?

---

#1381

Microsoft Reviewers: Open in CodeFlow

[KevinLaMS]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

zanseb The package manager bot determined there was an issue with the pull request. Make sure the ID is of the form publisher.appname and that the folder structure is publisher\appname.
For details on the error, see the details link below in the build pipeline.

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

This submission has moved to manual review.

[ghost]

During installation testing, this app triggered a Microsoft Defender SmartScreen error.

We are notifying [email protected] for investigation.

[KevinLaMS]

There are 2 issues with this install.

1. you must be an admin. by default it fails with exit code 1.
2. it seems to be an executable that runs, rather than a true installer.

[zanseb]

@KevinLaMS, thanks for the feedback. Is it mandatory for the package to use a true installer, or is it planned to support such scenarios too?

[denelon]

It should be covered under microsoft/winget-cli#194 or microsoft/winget-cli#182.

[denelon]

@zanseb this PR is blocked by the .exe feature. It will also fail now as we have updated the manifest schema to v1.0. I'm not sure if you'd like to update the manifest or close this PR until we have support for standalone executables.

[zanseb]

@denelon I am fine w/ both options. What would you prefer?

[denelon]

I think you've already done some of the heavy lifting to get the meta-data for the installer. If you don't mind updating the schema (knowing that it will fail validation), the community would benefit. The issue will be properly tagged so we can validate it once we have support for standalone executables, and nobody would need to go through the effort to gather the meta-data and submit a duplicate entry. Ultimately, it's up to you 😄

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Trenly]

Should be updated to the multi-manifest format

[zanseb]

I tired to split them. Have some trouble validating them locally (winget validate). Can you hint me a resource in which the multi-manifest format is described? I only found https://docs.microsoft.com/en-us/windows/package-manager/package/manifest?tabs=minschema%2Cinstaller-example#multiple-manifest-files

[ghost]

Hello @zanseb,
The package manager bot determined changes have been requested to your PR.

Template: msftbot/changesRequested

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ItzLevvie]

Close with reason: Replaced by PR 70732 which is available at #70732;

[Trenly]

Apologies for over-topping your PR; Given that portable applications are still so new, we are still trying to figure out best-practices for all of the metadata in them to control how the version and name of the package gets mapped into the Add & Remove Programs table.

I've used the data you included here in #70733. Thank you for your contribution and help!

[zanseb]

No worries!