Repository navigation
ci: pin maintenance workflow actions - #222
Conversation
Resolve the existing nine action refs to immutable commit SHAs across thirteen uses entries. Preserve action versions, workflow inputs, permissions and triggers.
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
Memory benchmarkCompared base
Interpretation: No metric shows a clear Base-to-PR difference beyond its measured run-to-run variation. Extension overhead above pi baseline
Values are medians of 6 alternating, paired runs. The value after Environment: pi
|
|
Final maintainer verification at updated head The earlier failure on The operator explicitly authorized merging this PR after the exact updated-head CI passed. No bypass, release, production update or billable inference is included. |
Summary
Pin 13
usesentries across the catalog-sync and memory-benchmark workflows to full commit SHAs. The nine distinct refs were resolved from their existing tags through the GitHub API, including annotated-tag dereferencing, and each pinned commit exposes anaction.ymlmanifest. Original versions are retained in comments.Only
.github/workflows/model-metadata.ymland.github/workflows/memory-benchmark.ymlchange. A parsed-YAML comparison confirms that exactly 13usesvalues changed; all other workflow values, inputs, scripts, permissions, triggers and job boundaries are identical to the base. No action version upgrade or runtime-provider change is included.Validation
git diff --check: PASS.unpinned-usesfindings on the changed files.Known baseline / scope
This is independent of the catalog refresh following #220. The base still carries the older model snapshot, so the live catalog/pricing checks can fail on current upstream drift until the separate catalog refresh #223 lands. This pin-only change does not claim to resolve that drift.
Existing credential-persistence (
artipacked) and ad-hoc-package warnings are unchanged. The guarded maintenanceworkflow_runworkflow is also unchanged. No global all-scanners-clean verdict is claimed; no suppressions were added. No billable inference was performed.Publication is for review/CI only, not an authorization to merge or release.
CI follow-up
At head
c21e19732854836ff17d626f17a1f367485298e4, all executed checks pass except catalog-synccheck(run 44052981565). Its logs confirm the known base drift: CLI 1.89.1 vs 1.89.2, plus missing Flint pricing on the 101-model API. Catalog PR #223 is green at773c9e374371e9b43a4bba177d86afb3b57b8aaf.Proposed integration order: review/merge #223 first when authorized, update this branch with main, then re-check the exact updated head. Do not bypass the failing check. No merge is being performed as part of this publication.