New version: GLab.GLab version 1.23.1

[viktomas]

• 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 <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.2 schema?

Note: manifests/g/GLab/GLab/1.23.1 is the name of the directory containing the manifest you're submitting.

---

Apart from updating the package, this PR also changes the origin (ownership) of the manifest

GitLab is now the official maintainer of the glab package.

• Archived original repo: https://github.com/profclems/glab
• Announcement issue: Announcement: glab is being adopted by GitLab profclems/glab#983
• The new home for the project https://gitlab.com/gitlab-org/cli
• Release mentioned in this PR https://gitlab.com/gitlab-org/cli/-/releases/v1.23.0

I've made a similar PR for

• homebrew: glab 1.23.0 Homebrew/homebrew-core#116608
• scoop: [email protected] - move to GitLab and update version ScoopInstaller/Main#4168

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @viktomas,

The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.2 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct.

You could also try our Windows Package Manager Manifest Creator or the YamlCreate script.

For details on the specific error, see the details link below in the build pipeline.

Template: msftbot/validationError/manifest/metadata

[ghost]

Hello @viktomas,

The package manager bot determined changes have been requested to your PR.

Template: msftbot/changesRequested

[russellbanks]

As a side note, please update your clone of winget-pkgs. The YamlCreate you're using is a bit outdated.

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[viktomas]

As a side note, please update your clone of winget-pkgs. The YamlCreate you're using is a bit outdated.

@russellbanks Ok, I updated to the latest master but there have been only 4 commits in it since I cloned it half an hour ago.

[ghost]

Hello @wingetbot!

Because this pull request has the Validation-Completed label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

[ghost]

viktomas,

The check-in policies require a moderator to approve PRs from the community.

Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission.

Template: msftbot/requiresApproval/moderator

[russellbanks]

As a side note, please update your clone of winget-pkgs. The YamlCreate you're using is a bit outdated.

@russellbanks Ok, I updated to the latest master but there have been only 4 commits in it since I cloned it half an hour ago.

The YamlCreate in your fork is the correct version but this PR was created with 2.0.4 so I'm not sure

[ghost]

Hello viktomas,
Validation has completed.

Template: msftbot/validationCompleted

[ghost]

Hello viktomas,
Validation has completed.

Template: msftbot/validationCompleted

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.