[updatecli] update elastic stack version for testing 9.5.4-08d723b5-SNAPSHOT

[github-actions]

Bump elastic-stack to latest snapshot version

Update snapshot.yml

1 file(s) updated with "$1=9.5.4-08d723b5-SNAPSHOT": * dev-tools/integration/.env

GitHub Action workflow link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[github-actions]

TL;DR

Both failing Buildkite jobs are blocked by the same infrastructure issue: apt-get update inside Dockerfile.build fails because the Debian bullseye security repo metadata is expired. This is not caused by this PR’s code change.

Remediation

• Re-run the Buildkite build once the bullseye-security mirror metadata is refreshed (or update the builder/base image to a source with valid APT metadata).
• If this recurs, update the release test image path away from stale Debian 11 metadata (for example, by refreshing the golang-crossbuild base used in Dockerfile.build) and re-run .buildkite/scripts/release_test.sh.

Investigation details

Root Cause

Package x86_64 and Package aarch64 both fail at the same Docker build step in Dockerfile.build (RUN apt-get update && apt-get install ... around line 5). The error is an expired Debian repo Release file, which indicates repository/mirror staleness rather than a source-code regression.

The PR itself only updates dev-tools/integration/.env (snapshot version bump), so it does not modify packaging Dockerfiles or release test scripts.

Evidence

• Build: https://buildkite.com/elastic/fleet-server/builds/16686
• Jobs/steps: Package x86_64, Package aarch64
• Key log excerpts:
  • E: Release file for (deb.debian.org/redacted) is expired (invalid since 18h ...). Updates for this repository will not be applied.
  • ERROR: failed to build ... process "/bin/sh -c apt-get update && apt-get install ..." did not complete successfully: exit code: 100
  • Failure location reported in both logs: Dockerfile.build:5

Verification

• Not run locally in this environment (Docker-in-Docker unsupported).

Follow-up

• If a retry still fails with the same expiry message, treat as CI/base-image maintenance and refresh the Debian source/base image used by release packaging.

---

What is this? | From workflow: PR Buildkite Detective

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