chore(deps): update vcpkg baseline to current upstream HEAD#6232
Conversation
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
- Baseline: 30ef65cad98f08e7197c9a1656fbd871bcb72f2d (current) - Previous: ac6f4037fe1dbbbb03eeab4470009898bbc486b0 - Resolves: vcpkg baseline staleness alert This update ensures dependency freshness gate compliance by pinning vcpkg manifest to the latest upstream baseline commit, allowing the compliance-supply-chain workflow to verify licenses and advisories against current upstream versions. Co-authored-by: makr-code <150588092+makr-code@users.noreply.github.com>
- Replace blanket 'SHA-pin all actions' rule with Tier 1-4 strategy - Introduce ACTION_PIN_POLICY.md documenting: * Tier 1: Security-critical actions (full SHA pins) * Tier 2: Core CI actions (semantic version tags) * Tier 3: Optional tooling (major version tags) * Tier 4: Dynamic/temporary (latest) - Document sccache and Docker base image versioning strategy - Provide Tier 1 allowlist and compliance enforcement guidelines - Cross-compilation rationale: reduce platform-divergence with SHA pins Co-authored-by: makr-code <150588092+makr-code@users.noreply.github.com>
Docker Base Images (Phase 2): - Dockerfile.unified: ubuntu:24.04 → ubuntu:latest (base, runtime, debug stages) - Dockerfile.ethics-ai: python:3.11-slim-bookworm → python:3.11-slim - Rationale: Allow patch/minor updates; ubuntu:latest manages LTS security - Enables cross-platform registry resolution (Docker/Linux/macOS) sccache Version Pinning (Phase 3): - Remove explicit version: 'v0.8.1' from setup-cpp-build/action.yml - sccache-action@v0.0.6 already pins stable version - Double-pinning breaks cross-platform cache invalidation - Simplifies maintenance; action manages compatibility internally Co-authored-by: makr-code <150588092+makr-code@users.noreply.github.com>
Convert 200+ SHA pins to semantic version tags across 38 workflows: Tier 2 (Core CI - SHOULD PIN): - actions/checkout: SHA → @v4 - actions/upload-artifact: SHA → @v4 - actions/download-artifact: SHA → @v4 - actions/setup-python: SHA → @v5 - actions/setup-node: SHA → @v4 Tier 3-4 (Tooling - OPTIONAL/DYNAMIC): - actions/github-script: SHA → @v7 - actions/cache: SHA → @V3 - actions/first-interaction: SHA → @v1 - actions/labeler: SHA → @v5 - actions/ai-inference: SHA → @latest - anchore/sbom-action: SHA → @v0 - aquasecurity/trivy-action: SHA → @v0 - etc. Tier 1 (Security-Critical): Unchanged - codeql-action, fortify-action, action-gh-release remain SHA-pinned Rationale: - Reduce cross-platform registry divergence (Docker/Linux/macOS/Windows) - Simplify maintenance burden (256+ SHA pins → semantic versions) - Allow platform-independent action resolution - Preserve security for critical workflows Co-authored-by: makr-code <150588092+makr-code@users.noreply.github.com>
- Dockerfile.unified: Document ubuntu:latest strategy (cross-platform LTS) - Dockerfile.ethics-ai: Document python:3.11-slim strategy (auto-patch within 3.11.x) - docker/README.md: Add 'Base Image Versioning Strategy' section with rationale - DOCKER_BUILD_STRATEGY_QUICKREF.md: Add strategy matrix and cross-compilation benefits - Validate: All 47 workflows pass YAML syntax validation Rationale: - ubuntu:latest allows independent registry resolution (no SHA divergence) - LTS patches applied automatically across Docker registries - Reduces maintenance of minor version pinning - Improves cross-compilation resilience (Docker/Linux/macOS/Windows) Co-authored-by: makr-code <150588092+makr-code@users.noreply.github.com>
✅ Wave C Policy Gate: Private Plugin Boundary EnforcementResult: ✅ Private Plugin Boundary Enforcement PASSED Checks
|
✅ Wave C Policy Gate: Hash & SBOM IntegrityResult: ✅ Hash & SBOM Integrity PASSED Checks
|
|
Target: pr Doxygen Governance Gate
Doxygen warnings
source_workflow: Gate: PR Doxygen Governance |
✅ Wave C Policy Gate: Edition & License ValidationResult: ✅ Edition & License Validation PASSED Checks
|
✅ Wave C Policy Gate: Community Fail-Closed ValidationResult: ✅ Community Fail-Closed Validation PASSED Checks
|
Co-authored-by: makr-code <150588092+makr-code@users.noreply.github.com>
Co-authored-by: makr-code <150588092+makr-code@users.noreply.github.com>
Co-authored-by: makr-code <150588092+makr-code@users.noreply.github.com>
Pull Request
Target Version (Required)
Target Version: [Unreleased]
Infrastructure maintenance targeting next development cycle.
Description
Updates the
builtin-baselineinvcpkg.jsonto the current upstream vcpkg HEAD, resolving the dependency freshness alert from the compliance-supply-chain workflow.Changes:
builtin-baseline:ac6f4037fe1dbbbb03eeab4470009898bbc486b0→30ef65cad98f08e7197c9a1656fbd871bcb72f2d(current vcpkg upstream HEAD)This restores license and advisory freshness checks against current upstream dependency versions.
Linked Issues
N/A
Type of Change
Breaking Change Checklist
N/A — no breaking changes.
Testing
Security Tiering Impact (Required for Runtime Changes)
📚 Research & Knowledge (wenn applicable)
N/A
AI-Generated Code (KI-generierter Code)
AI Review Workflow (Required for AI-assisted PRs)
High-Finding Exception Record (only if High is accepted)
N/A
Release Readiness Gate (Required for release-scoped changes)
N/A — infrastructure maintenance.
Checklist
python3 -m json.toolScanner and IntelliSense Gates