Skip to content

Bump github.com/elastic/opentelemetry-collector-components/processor/elasticinframetricsprocessor from 0.3.0 to 0.4.0 #10355

Bump github.com/elastic/opentelemetry-collector-components/processor/elasticinframetricsprocessor from 0.3.0 to 0.4.0

Bump github.com/elastic/opentelemetry-collector-components/processor/elasticinframetricsprocessor from 0.3.0 to 0.4.0 #10355

Workflow file for this run

name: golangci-lint
on:
#push:
# branches:
# - main
# - 8.*
# - 7.17
pull_request:
permissions:
contents: read
# Optional: allow read access to pull request. Use with `only-new-issues` option.
pull-requests: read
jobs:
golangci:
strategy:
matrix:
os: [ ubuntu-latest, macos-latest, windows-latest ]
name: lint
runs-on: ${{ matrix.os }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version-file: .go-version
- name: golangci-lint
uses: golangci/golangci-lint-action@v6
with:
# Optional: version of golangci-lint to use in form of v1.2 or v1.2.3 or `latest` to use the latest version
version: v1.55.2
# Give the job more time to execute.
# Regarding `--whole-files`, the linter is supposed to support linting of changed a patch only but,
# for some reason, it's very unreliable this way - sometimes it does not report any or some
# issues without linting the whole files, so we have to use `--whole-files`
# which can lead to some frustration from developers who would like to
# fix a single line in an existing codebase and the linter would force them
# into fixing all linting issues in the whole file instead.
args: --timeout=30m --whole-files
# Optional: show only new issues if it's a pull request. The default value is `false`.
only-new-issues: true