feat(siren): create alert support urn #338
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
10 errors and 2 warnings
validate:
gotocompany/siren/provider/v1beta1/provider.proto#L14
Field name "namespaceID" should be lower_snake_case, such as "namespace_id".
|
validate:
gotocompany/siren/provider/v1beta1/provider.proto#L15
Field name "namespaceURN" should be lower_snake_case, such as "namespace_urn".
|
validate:
gotocompany/siren/provider/v1beta1/provider.proto#L22
Field name "namespaceURN" should be lower_snake_case, such as "namespace_urn".
|
validate:
gotocompany/siren/provider/v1beta1/provider.proto#L37
Field name "providerID" should be lower_snake_case, such as "provider_id".
|
validate:
gotocompany/siren/provider/v1beta1/provider.proto#L38
Field name "namespaceID" should be lower_snake_case, such as "namespace_id".
|
validate
buf found 5 lint failures.
|
validate:
gotocompany/siren/v1beta1/siren.proto#L730
Field "2" on message "CreateAlertsRequest" changed type from "uint64" to "string". See https://developers.google.com/protocol-buffers/docs/proto3#updating for wire compatibility rules.
|
validate:
gotocompany/siren/v1beta1/siren.proto#L740
Field "2" on message "CreateAlertsWithNamespaceRequest" changed type from "uint64" to "string". See https://developers.google.com/protocol-buffers/docs/proto3#updating for wire compatibility rules.
|
validate:
gotocompany/siren/v1beta1/siren.proto#L742
Field "4" on message "CreateAlertsWithNamespaceRequest" changed type from "uint64" to "string". See https://developers.google.com/protocol-buffers/docs/proto3#updating for wire compatibility rules.
|
validate
buf found 3 breaking changes.
|
validate
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, bufbuild/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
validate
No github_token supplied, API requests will be subject to stricter rate limiting
|