[Release] Update version to 9.5.1

[elastic-vault-github-plugin-prod]

Updates references to the new release 9.5.1.

Merge after the release 9.5.0.

[infra-vault-gh-plugin-prod]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: d9127e2

Failed CI Steps

• check-ci

cc @elasticmachine

[github-actions]

TL;DR

check-ci failed because the version bump to 9.5.1 changed generated deployment artifacts, but the PR only commits version/version.go. Regenerate and commit the Helm chart, Kubernetes manifests, and Kubernetes integration fixture updates.

Remediation

• Run the generation steps from make check-ci after the version bump: GENERATEKUSTOMIZE=true make -C deploy/kubernetes generate-k8s, make -C deploy/kubernetes generate-k8s, mage -v helm:updateAgentVersion, mage -v helm:renderExamples, and mage -v integration:buildKubernetesTestData — or run make check-ci and keep the generated file changes.
• Commit the files reported as needs update, then rerun make check-ci or the failed Buildkite step.

Investigation details

Root Cause

This is generated artifact drift from the release version update. The PR diff changes only version/version.go from defaultBeatVersion = "9.5.0" to "9.5.1", but Makefile:45-50 regenerates Kubernetes manifests, Helm chart versions/rendered examples, and Kubernetes integration test data before Makefile:75-79 runs check-no-changes.

The generation code derives these files from the agent version:

• deploy/kubernetes/Makefile:5 reads BEAT_VERSION from version/version.go; deploy/kubernetes/Makefile:51, :118, :132, and :135-138 substitute it into generated Kubernetes and kustomize manifests.
• magefile.go:3938-3979 (helm:updateAgentVersion) updates deploy/helm/elastic-agent/Chart.yaml, deploy/helm/elastic-agent/values.yaml, and EDOT collector values from bversion.GetParsedAgentPackageVersion().CoreVersion().
• magefile.go:3842-3917 (helm:renderExamples) rewrites each Helm example rendered/manifest.yaml.
• magefile.go:2207-2239 (integration:buildKubernetesTestData) rewrites testing/integration/k8s/testdata/elastic-agent-kustomize.yaml.

Evidence

• Build: https://buildkite.com/elastic/elastic-agent/builds/42673
• Job/step: check-ci
• Key log excerpt:

deploy/helm/elastic-agent/Chart.yaml: needs update
deploy/helm/elastic-agent/values.yaml: needs update
deploy/helm/elastic-agent/examples/*/rendered/manifest.yaml: needs update
deploy/kubernetes/elastic-agent-managed-kubernetes.yaml: needs update
deploy/kubernetes/elastic-agent-standalone-kubernetes.yaml: needs update
testing/integration/k8s/testdata/elastic-agent-kustomize.yaml: needs update
make[1]: *** [Makefile:78: check-no-changes] Error 1
make: *** [Makefile:51: check-ci] Error 2

The diff shown immediately before the failure updates generated image references from docker.elastic.co/elastic-agent/elastic-agent:9.5.0 to :9.5.1, confirming the files need to be regenerated rather than hand-edited.

Verification

Not run locally; this workflow is read-only and the Buildkite git diff/needs update output already identifies the exact generated files that are dirty after check-ci regeneration.

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.