Skip to content

fix(quality): point the provider-asset provenance manifest at the squash commit that landed notrack-web - #16055

Merged
diegosouzapw merged 2 commits into
release/v3.8.52from
fix/release-v3.8.52-basereds-1008l
Oct 9, 2026
Merged

diegosouzapw merged 2 commits into
release/v3.8.52from
fix/release-v3.8.52-basereds-1008l

Conversation

@diegosouzapw

Copy link
Copy Markdown
Owner

Every CI run on release/v3.8.52 fails npm run check:provider-asset-provenance (job Lint) with:

Provider asset provenance failed:
- auditedCommit object does not exist: 23f82836e438c95d21db90382a44b3539f81ba48

#12534 recorded the contributor's pre-squash commit as auditedCommit. That object is not an ancestor of the release branch, so a CI checkout (fetch-depth: 0 of the branch) never has it; it only passes on machines that happened to fetch the PR ref.

Fix: point it at the squash commit 57a9237b (#12534 as landed).

Evidence:

  • git merge-base --is-ancestor 23f82836 origin/release/v3.8.52 → false; 57a9237b → true.
  • git diff 23f82836 57a9237b -- public/providers → empty (byte-identical snapshot, so every recorded hash still holds).
  • node scripts/check/check-provider-asset-provenance.mjs on this branch: passed, 142/142 registered.

⚠️ base-red inherited: check:agent-skills-sync (generated SKILL.md drift since #15778; fix pending in #15945/#15948).

…ash commit that landed notrack-web

#12534 recorded the contributor's pre-squash commit (23f8283) as auditedCommit. That object is
not reachable from release/v3.8.52, so every CI checkout fails the provenance gate with
'auditedCommit object does not exist'. The squash commit 57a9237 carries a byte-identical
public/providers snapshot.
@diegosouzapw
diegosouzapw merged commit a470553 into release/v3.8.52 Oct 9, 2026
9 of 12 checks passed
@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

CI Coverage Report

  • Coverage job: skipped
  • PR test policy: success

Coverage artifact was not available for this run.

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