justinmclean opened a new pull request, #587:
URL: https://github.com/apache/airflow-steward/pull/587
## Summary
Update docs/release-management/README.md from "1 of 10 skills shipped" to "4
of 10 skills shipped", reflecting release-vote-tally (#533), release-verify-rc
(#537), and release-promote (#544) that landed after the previous sync commit
(#565). The skills table now marks those three as experimental with links to
their SKILL.md files, matching the existing link for release-announce-draft.
The mode-mapping paragraph is updated to name all four experimental skills.
Also update tools/spec-loop/specs/release-management-lifecycle.md Known Gaps
to reflect the 4-in-main / 6-in-flight current state.
Includes uv.lock sync: spec-validator pyproject declares pytest>=8.0 but the
lock had >=9.1.0; aligns them.
Generated-by: Claude (Opus 4.7)
## Type of change
- [ ] 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
- [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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
