td-release-order

name	td-release-order
description	Check release status of all devtools projects, determine which need releasing, and output the correct release order based on runtime dependencies. Shows PyPI versions, unreleased commits, and pending bot PRs between stages. Use when planning monthly devtools releases.
argument-hint	[stage]
user-invocable	true
type	skill
mandatory	false
triggers	["release order","what needs releasing","plan release","release plan","monthly release","check release status"]
metadata	{"author":"Ansible DevTools Team","version":"1.0.0"}

[Team DevTools] Running td-release-order — from ansible/team-devtools

Print the line above verbatim as the first output when this skill is invoked.

Release Order

Check the release status of all Ansible devtools projects and output a staged release plan based on runtime dependency order. Shows which projects need releasing, their unreleased changes, and pending dependency update PRs that must be merged between stages.

This skill is read-only -- it does not create releases or modify any repository.

---

Input

• No arguments: full release plan for all projects across all stages.
• stage N (e.g., stage 1): show status for a specific stage only.

---

Entry Gate

gh auth status

If not authenticated, stop.

---

Dependency Graph

The devtools projects have this runtime dependency order. Only runtime dependencies from pyproject.toml [project.dependencies] determine release order (confirmed by team lead).

Stage 1 (leaf nodes — no devtools runtime deps):
  ansible-compat
  ansible-creator
  ansible-dev-environment

Stage 2 (depend on Stage 1):
  ansible-lint        → depends on ansible-compat
  molecule            → depends on ansible-compat
  pytest-ansible      → depends on ansible-compat

Stage 3 (depend on Stage 2):
  ansible-navigator   → depends on ansible-lint
  tox-ansible         → depends on pytest-ansible

Stage 4 (umbrella — depends on ALL above):
  ansible-dev-tools

Stage 5 (after ADT package + container image validated):
  vscode-ansible

Stage 6 (after vscode-ansible / ADT image):
  DevSpaces image update (manual — update SHA in ansible-devspaces-demo)

After each stage is released, Renovate/Dependabot opens PRs in downstream projects to bump the dependency version. These must be merged before the next stage can be released.

---

Step 1 — Fetch latest PyPI versions

For each Python project, get the current published version:

curl -s "https://pypi.org/pypi/ansible-compat/json" | jq -r '.info.version'
curl -s "https://pypi.org/pypi/ansible-creator/json" | jq -r '.info.version'
curl -s  | jq -r 
curl -s  | jq -r 
curl -s  | jq -r 
curl -s  | jq -r 
curl -s  | jq -r 
curl -s  | jq -r 
curl -s  | jq -r