New Package: tastyworks.tastytrade version 2.3.1

[Trenly]

• Related to New version: tastyworks.tastyworks version 2.3.1 #111749
• Resolves [Update Request]: tastyworks/tastytrade #111718

Microsoft Reviewers: codeflow:open?pullrequest=#111750

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

No commit pushedDate could be found for PR 111750 in repo microsoft/winget-pkgs

[wingetbot]

/AzurePipelines run

[azure-pipelines]

No commit pushedDate could be found for PR 111750 in repo microsoft/winget-pkgs

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

[BrandonWanHuanSheng]

It look like you were max length with the schema. .

[Trenly]

@stephengillie - This needs a manual review using the latest 1.5 release since the pipelines haven’t been updated with the new client yet

[BrandonWanHuanSheng]

Remember, the yaml-language-server need to change 1.4.0 to 1.5.0
Also, I change on the ending header which is point to 1.5.0

[Trenly]

Remember, the yaml-language-server need to change 1.4.0 to 1.5.0
Also, I change on the ending header which is point to 1.5.0

Either way the validation will still fail, since 1.5 manifests will be kicked back by the pipeline as invalid. The CLI handles this case just fine, it's just the schema validation that fails using the 1.4 schema

[BrandonWanHuanSheng]

Remember, the yaml-language-server need to change 1.4.0 to 1.5.0
Also, I change on the ending header which is point to 1.5.0

Either way the validation will still fail, since 1.5 manifests will be kicked back by the pipeline as invalid. The CLI handles this case just fine, it's just the schema validation that fails using the 1.4 schema

Oh, I see.

[BrandonWanHuanSheng]

I just testing in draft to see. If the pipelines still happening. But I actually got a validation succeed coming from
winget validate --manifest "F:\manifests\t\tastyworks\tastytrade\2.3.1"
Manifest validation succeeded.

F:>winget
Windows Package Manager v1.5.1881

[microsoft-github-policy-service]

Trenly,

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

[stephengillie]

Automatic Validation ended with:

Manifest Error: Schema Error [Schema validation failed. Error context: [InstallationNotes] Description: String should be no more than 256 characters in length. Error context: Description: Failed to validate against schema associated with property name 'InstallationNotes'. ] File: tastyworks.tastytrade.locale.en-US.yaml

[Trenly]

Automatic Validation ended with:

Manifest Error: Schema Error [Schema validation failed. Error context: [InstallationNotes] Description: String should be no more than 256 characters in length. Error context: Description: Failed to validate against schema associated with property name 'InstallationNotes'. ] File: tastyworks.tastytrade.locale.en-US.yaml

@stephengillie - I'm aware of that; This has been resolved in the latest version of the CLI;
Thanks for the manual review!

[microsoft-github-policy-service]

Hello Trenly,
Validation has completed.

Template: msftbot/validationCompleted

[wingetbot]

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