chore(deps): update go module directive to v1.27.1 (main)

[renovate-sh-app]

This PR contains the following updates:

Package	Type	Update	Change
go (source)	golang	minor	1.26.5 → 1.27.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

Need help?

You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.

[renovate-sh-app]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 15 additional dependencies were updated

Details:

Package	Change
github.com/davecgh/go-spew	v1.1.2-0.20180830191138-d8f796af33cc -> v1.1.2-0.20180830191138-d8f796af33cc
github.com/hashicorp/go-hclog	v1.6.3 -> v1.6.3
github.com/opentracing-contrib/go-grpc	v0.1.2 -> v0.1.2
github.com/opentracing/opentracing-go	v1.2.0 -> v1.2.0
github.com/pierrec/lz4/v4	v4.1.26 -> v4.1.26
github.com/pkg/errors	v0.9.1 -> v0.9.1
go.yaml.in/yaml/v2	v2.4.4 -> v2.4.4
golang.org/x/net	v0.58.0 -> v0.58.0
google.golang.org/genproto/googleapis/rpc	v0.0.0-20260630182238-925bb5da69e7 -> v0.0.0-20260630182238-925bb5da69e7
github.com/Microsoft/go-winio	v0.6.2 -> v0.6.2
github.com/aws/aws-sdk-go-v2/internal/v4a	v1.4.36 -> v1.4.36
github.com/google/jsonschema-go	v0.4.2 -> v0.4.2
github.com/hashicorp/golang-lru/v2	v2.0.7 -> v2.0.7
go.opentelemetry.io/contrib/exporters/autoexport	v0.69.0 -> v0.69.0
gopkg.in/ini.v1	v1.67.2 -> v1.67.2

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: Lint fails because the pinned tempo-ci-tools image (main-3f54f1c-20260716-212549, built from golang:1.26.5) ships a golangci-lint that refuses configs targeting go 1.27.0 — a toolchain-image mismatch, not a lint rule violation. Human next step: bump TEMPO_CI_TOOLS_IMAGE in Makefile (and build/tools.mk) to a tempo-ci-tools tag built on Go >=1.27, similar to PR #7643.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: The pinned TEMPO_CI_TOOLS_IMAGE (main-3f54f1c-20260716-212549) has golangci-lint built with Go 1.26, but this PR bumps go.mod and tools/go.mod to 1.27.1, so golangci-lint refuses to run ("the Go language version (go1.26) used to build golangci-lint is lower than the targeted Go version (1.27.1)"). A human needs to merge the tools/go.mod bump so docker-ci-tools.yml publishes a fresh tempo-ci-tools image built with Go 1.27, then bump TEMPO_CI_TOOLS_IMAGE in the Makefile to that new tag (either in this PR after the image exists, or in a follow-up).

[renovate-sh-app]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: Lint fails because the CI-tools Docker image pinned via TOOLS_IMAGE_TAG in build/tools.mk bundles a golangci-lint built with Go 1.26, which refuses to load its config against this PR's Go 1.27.1 target. Fixing requires merging the pending tools/Dockerfile bump to golang:1.27.1-alpine so docker-ci-tools.yml publishes a new image tag, then updating TOOLS_IMAGE_TAG in build/tools.mk to that new tag — a coordinated release step, not a code change on this PR.

[tempo-ci-app]

🤖 fix-renovate-prs failed_to_fix: Lint fails because the pinned tempo-ci-tools image (build/tools.mk: main-3f54f1c-20260716-212549) contains a golangci-lint built with Go 1.26, which refuses to run against this PR's Go 1.27.1 code even though tools/Dockerfile has been bumped. A maintainer needs to publish a new tempo-ci-tools image from this PR's tools/Dockerfile (docker-ci-tools.yml only auto-builds on push to main under tools/**) and then bump TOOLS_IMAGE_TAG in build/tools.mk to that new tag, as described in the repo's update-go-version skill.