Release 6.16.0 #1137
Annotations
1 error and 11 warnings
Publish package to NuGet
Process completed with exit code 127.
|
Publish package to NuGet
The target framework 'netcoreapp2.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
|
Publish package to NuGet:
src/Twilio/Rest/Conversations/V1/Conversation/MessageResource.cs#L631
XML comment has badly formed XML -- 'Whitespace is not allowed at this location.'
|
Publish package to NuGet:
src/Twilio/Rest/Accounts/V1/Credential/AwsOptions.cs#L31
XML comment has badly formed XML -- 'End tag 'summary' does not match the start tag 'AWS_SECRET_ACCESS_KEY'.'
|
Publish package to NuGet:
src/Twilio/Rest/Accounts/V1/Credential/AwsOptions.cs#L32
XML comment has badly formed XML -- 'Expected an end tag for element 'AWS_ACCESS_KEY_ID'.'
|
Publish package to NuGet:
src/Twilio/Rest/Accounts/V1/Credential/AwsOptions.cs#L32
XML comment has badly formed XML -- 'Expected an end tag for element 'summary'.'
|
Publish package to NuGet:
src/Twilio/Rest/Accounts/V1/Credential/AwsOptions.cs#L42
XML comment has badly formed XML -- 'End tag 'param' does not match the start tag 'AWS_SECRET_ACCESS_KEY'.'
|
Publish package to NuGet:
src/Twilio/Rest/Accounts/V1/Credential/AwsOptions.cs#L43
XML comment has badly formed XML -- 'Expected an end tag for element 'AWS_ACCESS_KEY_ID'.'
|
Publish package to NuGet:
src/Twilio/Rest/Accounts/V1/Credential/AwsOptions.cs#L43
XML comment has badly formed XML -- 'Expected an end tag for element 'param'.'
|
Publish package to NuGet:
src/Twilio/Rest/Conversations/V1/Service/Conversation/MessageResource.cs#L662
XML comment has badly formed XML -- 'Whitespace is not allowed at this location.'
|
Publish package to NuGet:
src/Twilio/Rest/Accounts/V1/Credential/AwsResource.cs#L78
XML comment has badly formed XML -- 'End tag 'param' does not match the start tag 'AWS_SECRET_ACCESS_KEY'.'
|
Build and Push image
The target framework 'netcoreapp2.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
|
The logs for this run have expired and are no longer available.
Loading