potiuk opened a new pull request, #67422:
URL: https://github.com/apache/airflow/pull/67422

   Cherry-pick of #67412 onto v3-2-test. Catches v3-2-test up to the latest 
steward state after the framework adoption (#67420) just landed.
   
   ### What changes
   
   - Bumps the apache-steward framework snapshot to apache/airflow-steward 
\`b19ac36\` (4 commits beyond the prior \`b9e1967\` pin).
   - Re-syncs the committed \`setup-steward\` skill byte-for-byte to match the 
framework snapshot.
   - **Drops the per-file SPDX header** that the previous adopt added on top of 
every framework skill file under \`.github/skills/setup-steward/\` — the header 
was airflow-specific decoration on framework-owned content; reconciliation with 
future framework updates is cleaner without it.
   - Updates the agentic-markdown \`insert-license\` prek hook to exclude 
\`.github/skills/setup-steward/\` so the header is not auto-re-added.
   - Adds two \`.gitignore\` entries surfaced by \`/setup-steward verify\`:
     - \`/.claude/settings.local.json\` (per-machine sandbox-allowlist file).
     - \`/.claude/skills/issue-*\` (Pattern-B mirror of the existing 
\`/.github/skills/issue-*\` entry).
   
   ### What does not change
   
   - No new opt-in framework families wired (still pr-management only).
   - The \`lychee\` prek hook does not exist on v3-2-test, so the corresponding 
lychee-exclude hunk from the main commit is N/A here.
   
   ### After merge
   
   \`/setup-steward verify\` runs clean against the v3-2-test snapshot pin.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 4.7)
   
   Generated-by: Claude Code (Opus 4.7) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to