From 7ea6ce0ad3884770de5af3d4686ccd02d8930d73 Mon Sep 17 00:00:00 2001 From: Pavel Kuznetsov Date: Sat, 7 Nov 2026 12:06:30 +0200 Subject: [PATCH 1/2] docs(ci): record verified immutable first-party GitHub Actions pins --- ACTIONS_PINS.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 ACTIONS_PINS.md diff --git a/ACTIONS_PINS.md b/ACTIONS_PINS.md new file mode 100644 index 0000000..5c665ec --- /dev/null +++ b/ACTIONS_PINS.md @@ -0,0 +1,25 @@ +# Official GitHub Actions pins + +This file is the 4FusionLab source of truth for first-party GitHub Actions used in CI, add-in packaging and (manual) GitHub Pages publishing. Check the upstream repository tag ref before changing any SHA. Pin to an immutable **40-character commit SHA**, not `@vN`, `@main` or an abbreviated hash. + +| Action | Reviewed version | Immutable commit SHA | +| --- | --- | --- | +| `actions/checkout` | `v7.0.1` | `3d3c42e5aac5ba805825da76410c181273ba90b1` | +| `actions/setup-python` | `v7.1.0` | `6d4fd22b20465ccc0f7354476588e8df7c9ca0e0` | +| `actions/setup-node` | `v6` | `249970729cb0ef3589644e2896645e5dc5ba9c38` | +| `actions/upload-artifact` | `v7.0.2` | `cf430e030ddbb5b0abf93d22962f4752f3646cd9` | +| `actions/download-artifact` | `v8.0.2` | `9000827ccba6bdab643e8b6fd33ac0654aef8333` | +| `actions/configure-pages` | `v5` | `983d7736d9b0ae728b81ab479565c72886d7745b` | +| `actions/upload-pages-artifact` | `v3` | `56afc609e74202658d3ffba0e8f6dda462b719fa` | +| `actions/deploy-pages` | `v4` | `d6db90164ac5ed86f2b6aed7e0febac5b3c0c03e` | + +Reviewed on **2026-11-07** against each upstream `refs/tags/` using the GitHub REST API. This document intentionally does **not** claim these versions are the latest forever. + +## Maintenance contract + +1. Keep the existing architecture and OS-specific product CI intact. A first-party Action upgrade is infrastructure-only and must **not** change `.github/release-paths.txt` or ship a GitHub Release by itself. +2. Update Actions together where practicable, using one reviewable PR per repository. Before merging, verify actual PR CI, including ZIP and SHA-256 contracts; then check `main` runs and skipped publishing steps. +3. Only project release jobs need `contents: write`. Leave normal CI `contents: read`; set `persist-credentials: false` in checkout steps unless a specific authorized write requires otherwise. +4. Do not automatically deploy the Filamentra-DataSource GitHub Pages demo as part of a pin update. Its workflow is intentionally manual. +5. Shared 4FusionLab composite Actions are separate: consumers pin `4FusionLab/.github/.github/actions/*` to the reviewed platform commit SHA. GitVersion.Tool remains `6.8.2`. +6. When changing a pin, resolve the tag through upstream GitHub, read breaking changes, update this table and the consumer PRs, and keep version comments next to pinned `uses:` lines. From 002e80986ec54e53e607867d80567f32d230263f Mon Sep 17 00:00:00 2001 From: Pavel Kuznetsov Date: Sat, 7 Nov 2026 12:06:37 +0200 Subject: [PATCH 2/2] docs(ci): reference central verified GitHub Actions pins --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index d62770b..1c2651e 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -13,6 +13,7 @@ This repository holds reusable, **read-only** CI building blocks and organizatio - Preserve each repository's `.github/release-paths.txt` as its reviewed release-eligibility allowlist. Pure README, docs, test, workflow, policy and AGENTS.md changes must not create a GitHub Release. - GitVersion.Tool is pinned to **6.8.2**. Full Git history is required. Published tags, releases and uploaded assets are immutable; never retarget tags, clobber artifacts or downgrade a prerelease to Stable. - Core shared Actions live at `.github/actions/` and must be pinned by their exact commit SHA in consuming projects. Do not reference the moving `main` branch in production release jobs. +- Pin first-party `actions/*` usages to the exact reviewed SHAs in [`ACTIONS_PINS.md`](ACTIONS_PINS.md). Verify upstream tags before updating; do not use floating major-version tags in product workflows. - Only publishing jobs need `contents: write`; package tests, metadata inspection and PR jobs run with least-privilege read permissions. - A passing offline build or Python test **does not** imply Autodesk Fusion CAD acceptance. Preserve native platform evidence and security/compatibility gates.