ci: add missing xtensa-amd_acp_7_3 toolchain and enable provenance attestation#18
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix workflow-level warnings and metadata issues seen in GitHub Actions annotations for container builds.
Changes
W4 — Split collapsed xtensa-amd_acp entry into two toolchains
In the GNU matrix, one entry incorrectly combined:
arch: xtensa-amd_acp_7_0_adsp_zephyr-elfnick: xtensa-amd_acp_7_3_adspThis effectively dropped the 7.3 toolchain and mislabeled the 7.0 image tag. Replaced with two explicit entries:
xtensa-amd_acp_7_0_adsp_zephyr-elf/xtensa-amd_acp_7_0_adspxtensa-amd_acp_7_3_adsp_zephyr-elf/xtensa-amd_acp_7_3_adspW5 — Enable provenance attestations
For all four jobs (
base,gnu,llvm,posix):provenance: false->provenance: trueattestations: writeid-token: writeThis resolves the build-push-action provenance warning while preserving existing build/push behavior.
Risk
Low. Changes are limited to workflow metadata and matrix entries; no Dockerfile or runtime logic changes.