Skip to content

fix(ci): retain backend digests for release retries - #12160

Open
localai-org-maint-bot wants to merge 1 commit into
masterfrom
fix/ci-release-digest-retention
Open

localai-org-maint-bot wants to merge 1 commit into
masterfrom
fix/ci-release-digest-retention

Conversation

@localai-org-maint-bot

Copy link
Copy Markdown
Collaborator

Description

Keep backend digest artifacts for seven days instead of one. In the v4.10.0 release, the ace-step merge and VibeVoice merge ran just after the digest artifacts expired. Downloading zero artifacts left /tmp/digests absent and prevented publication despite successful image builds.

Notes for Reviewers

Parsed the changed workflow as YAML and checked both observed upload-to-merge intervals against the old and new retention periods: both exceeded one day and fit within seven days. git diff --check passes. Artifact names, digest contents, and publication logic are unchanged.

This prevents expiry on future runs; it does not restore expired v4.10.0 artifacts or explain the separate Bonsai artifact-listing failure.

Signed commits

  • Human DCO sign-off required.
  • Documentation update not applicable (CI configuration only).

The v4.10.0 ace-step and VibeVoice merge jobs started just after their
digest artifacts expired. Keep the small digest artifacts for seven
days so a multi-day release matrix can finish publishing its images.

Assisted-by: Codex:gpt-6

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant