Skip to content

chore(deps): bump go.opentelemetry.io/otel from 1.24.0 to 1.29.0 #4545

chore(deps): bump go.opentelemetry.io/otel from 1.24.0 to 1.29.0

chore(deps): bump go.opentelemetry.io/otel from 1.24.0 to 1.29.0 #4545

Triggered via pull request August 30, 2024 07:59
Status Failure
Total duration 2m 33s
Artifacts

lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 2 warnings
lint
cannot use (*recordingSpan)(nil) (value of type *recordingSpan) as ReadWriteSpan value in variable declaration: *recordingSpan does not implement ReadWriteSpan (missing method AddLink)
lint
cannot use nonRecordingSpan{} (value of type nonRecordingSpan) as "go.opentelemetry.io/otel/trace".Span value in variable declaration: nonRecordingSpan does not implement "go.opentelemetry.io/otel/trace".Span (missing method AddLink)
lint
impossible type assertion: p.(*recordingSpan)
lint
cannot use tr.newNonRecordingSpan(sc) (value of type nonRecordingSpan) as "go.opentelemetry.io/otel/trace".Span value in return statement: nonRecordingSpan does not implement "go.opentelemetry.io/otel/trace".Span (missing method AddLink)
lint
cannot use tr.newRecordingSpan(psc, sc, name, samplingResult, config) (value of type *recordingSpan) as "go.opentelemetry.io/otel/trace".Span value in return statement: *recordingSpan does not implement "go.opentelemetry.io/otel/trace".Span (missing method AddLink)
lint
Process completed with exit code 2.
helm
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@e9aba2c848f5ebd159c070c61ea2c4e2b122355e. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
helm
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78, actions/setup-python@e9aba2c848f5ebd159c070c61ea2c4e2b122355e. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/