[updatecli] update elastic stack version for testing 9.6.0-153c69d9-SNAPSHOT

[github-actions]

Bump elastic-stack to latest snapshot version

Update snapshot.yml

1 file(s) updated with "$1=9.6.0-153c69d9-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 (Package x86_64 and Package aarch64) fail before repository code is built or tested. The immediate action is to rerun once the upstream Debian bullseye-security apt metadata expiry is resolved, or refresh the build image/repo configuration used by Dockerfile.build.

Remediation

• Update the packaging build environment to avoid stale bullseye-security metadata (e.g., rebuild/refresh the golang-crossbuild base image or move to a supported Debian release/security repo).
• Re-run the two package jobs after the repo metadata issue is resolved; no PR code change is indicated by current evidence.

Investigation details

Root Cause

The Docker build in .buildkite/scripts/release_test.sh fails at Dockerfile.build step RUN apt-get update && apt-get install ... due to expired Debian security repository metadata, which is an infrastructure/environment failure rather than a PR logic/test regression.

• PR scope is only dev-tools/integration/.env version bump (changed_files: 1), not packaging Docker logic.
• Both architectures fail with the same apt error in the same Dockerfile step, indicating shared external environment breakage.

Evidence

• Build: https://buildkite.com/elastic/fleet-server/builds/16685
• Jobs/steps:
  • Package x86_64 (.buildkite/scripts/release_test.sh)
  • Package aarch64 (.buildkite/scripts/release_test.sh)
• Key log excerpt (both jobs):

  E: Release file for (deb.debian.org/redacted) is expired (...). Updates for this repository will not be applied.
  ERROR: failed to solve: process "/bin/sh -c apt-get update && apt-get install --no-install-recommends -y zip && apt-get clean" did not complete successfully: exit code: 100
  

Verification

• Not run locally in this workflow (read-only detective pass based on Buildkite artifacts/logs).

Follow-up

If this recurs after rerun, track as CI infrastructure/image maintenance (base image/repository freshness), not as a code bug in this PR.

---

What is this? | From workflow: PR Buildkite Detective

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