You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "justinmclean (via GitHub)" <gi...@apache.org> on 2026/06/21 02:16:40 UTC
[PR] docs(spec-loop): sync specs with contributed functionality [airflow-steward]
justinmclean opened a new pull request, #539:
URL: https://github.com/apache/airflow-steward/pull/539
## Summary
- triage-mode: add issue-stale-sweep (now shipped), security-issue-triage, security-issue-import-from-scan, security-issue-import-via-forwarder, contributor-activity-sweep, committer-onboarding to Where it lives; update Known gaps to remove resolved stale-issue gap and fix contributor-growth cross-reference
- mentoring-mode: add mentoring-welcome (3rd Mentoring skill) to Where it lives and Validation; update acceptance criteria and Known gaps to reflect it shipped; remove first-contact welcome from unbuilt list
- release-management-lifecycle: reflect release-announce-draft shipped (experimental, Step 11); update Known gaps and Validation accordingly
- overview: update Mentoring to "3 skills"; add release-announce-draft to Drafting experimental row
- meta-and-quality-tooling: update skill-and-tool-validator description to include eval-coverage soft check and Python license-header check; update spec-validator description to include SPDX header, Known gaps, Validation code block, and path-existence checks
Generated-by: Claude (Opus 4.7)
## Type of change
<!-- Tick all that apply. -->
- [ ] Skill change (`.claude/skills/<name>/`) — eval fixtures updated below
- [ ] Tool / bridge contract (`tools/<system>/*.md`)
- [ ] Python package (`tools/*/` with `pyproject.toml`)
- [ ] Groovy reference impl
- [ ] Cross-cutting (RFC, AGENTS.md, sandbox, privacy-LLM)
- [X] Documentation (`docs/`, `README.md`, `CONTRIBUTING.md`)
- [ ] Project template (`projects/_template/`)
- [ ] CI / dev loop (`prek`, workflows, validators)
- [ ] Other:
## Test plan
<!--
How you verified the change. Be specific. The reviewer reads this to
decide what to spot-check vs trust. Empty "ran the tests" doesn't help.
-->
- [X] `prek run --all-files` passes
- [ ] For Python packages touched: `uv run pytest` / `ruff check` / `mypy` passes
- [ ] For Groovy bridges touched: command-line invocation tested end-to-end
- [ ] For skill changes: eval suite passes for the affected skill
(`PYTHONPATH=tools/skill-evals/src python3 -m skill_evals.runner tools/skill-evals/evals/<skill>/`)
- [ ] For skill *behaviour* changes: a new or updated eval fixture is included in this PR
(a regression test for the bug fixed / the behaviour added — see CONTRIBUTING.md)
- [ ] Other:
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] docs(spec-loop): sync specs with contributed functionality [airflow-steward]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #539:
URL: https://github.com/apache/airflow-steward/pull/539
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] docs(spec-loop): sync specs with contributed functionality [airflow-steward]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on PR #539:
URL: https://github.com/apache/airflow-steward/pull/539#issuecomment-4814828318
Rebased this onto current `main` and folded in an additional sync commit — heads-up on what changed.
**Rebase:** one conflict, in `release-management-lifecycle.md` "Known gaps". `main`'s side was already newer than this branch's, so I took `main`'s text there.
**Why a fold-on sync was needed:** this branch's sync point (`.last-sync`) was `296b72f`, but `main` has shipped **7 skills** since, so several specs were already stale the moment this landed — and `.last-sync` was ~30 commits behind `main`. I synced them in a second commit:
- **`repo-health-family.md`** — family is now three skills deep: `workflow-security-audit` and `dependency-audit` shipped alongside `ci-runner-audit` (was "one skill deep").
- **`triage-mode.md`** — added `issue-deduplicate` + `issue-backlog-stats` to the inventory; retired the "no general-issue dedup / backlog dashboard" gap and the "repo-health one-off" gap (both now false).
- **`release-management-lifecycle.md`** — 4 of 10 skills shipped (`release-announce-draft`, `release-verify-rc`, `release-vote-tally`, `release-promote`); status `proposed → experimental`.
- **`overview.md`** — release-management line now reflects experimental (4/10 shipped).
- **`.last-sync`** — bumped to the current `main` tip.
Verified with `spec-validate` (OK, no violations).
To stop this class of drift recurring, I also opened #583 — an `AGENTS.md` convention requiring a spec-sync pre-check before pushing a functionality PR (or a rebase of one onto a moved `main`). Thanks for keeping the specs honest with this one.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org