New version: Keybase.Keybase version 6.2.4

[orgcontrib]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• 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.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

• Resolve [Update Request]: Keybase v6.2.4 #135227

[orgcontrib]

@microsoft-github-policy-service agree

[mdanish-kh]

@wingetbot run

[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).

[stephengillie]

Hi @orgcontrib,

This PR's version number 6.2.4 has 3 parameters (sets of numbers between dots - major, minor, etc), which is less than the current manifest's version 6.1.0.4, which has 4 parameters.

Is this intentional?

(Automated response - build 629)

[orgcontrib]

Hi @orgcontrib,

This PR's version number 6.2.4 has 3 parameters (sets of numbers between dots - major, minor, etc), which is less than the current manifest's version 6.1.0.4, which has 4 parameters.

Is this intentional?

(Automated response - build 629)

Yes and No. I want to keep it simple, and since this is a community effort, SymVer or SemVer matters less for me as long as there is no direct integration between upstream repo and this one. I'm a simple user of this app, and the main reason why I decided to contribute to its pkg refresh here is the recent problem with an expired x509 certificate.

[stephengillie]

Edit: Automation getting away from me, sorry.

[wingetbot]

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