Skip to content

Agentic Workflow: Update Python versions using JSON endpoint #388

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
edvilme merged 2 commits into from
Feb 24, 2026
Merged

Agentic Workflow: Update Python versions using JSON endpoint #388

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3aa2e48
Update agent to use json endpoint
edvilme Feb 20, 2026
39447ea
AW: Recompile
edvilme Feb 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions .github/workflows/check-python-versions.lock.yml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

15 changes: 10 additions & 5 deletions .github/workflows/check-python-versions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,11 @@
---
description: >
Annual check of the latest supported Python versions from devguide.python.org.
Annual check of the latest supported Python versions from peps.python.org.
Creates a PR to add newly released versions and remove end-of-life versions
from CI workflows, actions, Azure Pipelines, and source code.
strict: false
engine:
id: copilot
on:
schedule:
- cron: "0 12 15 10 *"
Expand All @@ -15,7 +18,9 @@ tools:
toolsets: [default]
network:
allowed:
- defaults
- python
- "peps.python.org"
safe-outputs:
create-pull-request:
draft: true
Expand All @@ -35,9 +40,9 @@ This repository is a VS Code extension that supports all actively maintained Pyt

### Step 1: Fetch current supported Python versions

Fetch `https://devguide.python.org/versions/` and parse the **Supported versions** table.
Fetch `https://peps.python.org/api/release-cycle.json` and parse the JSON response.

Extract all versions that have a status of **bugfix** or **security**. These are the released, actively supported versions. Ignore versions with status **feature** or **prerelease** (these are not yet released).
Each key in the JSON object is a Python version (e.g., `"3.13"`), and its value contains a `"status"` field. Extract all versions where the status is **`security`**, **`bugfix`**, or **`feature`**. Ignore versions with status **`end-of-life`** (or any other status).

Build a sorted list of supported versions (e.g., `['3.10', '3.11', '3.12', '3.13', '3.14']`). The lowest is the minimum supported version, the highest is the newest.

Expand Down Expand Up @@ -94,7 +99,7 @@ Create a pull request with all the changes using the `create-pull-request` safe
- **Title**: `Update supported Python versions`
- **Body**: Include:
- A summary of what changed (versions added/removed, minimum version update if applicable)
- A link to https://devguide.python.org/versions/ as the source of truth
- A link to https://peps.python.org/api/release-cycle.json as the source of truth
- The list of files modified
- A note to verify CI passes before merging

Expand All @@ -104,4 +109,4 @@ Create a pull request with all the changes using the `create-pull-request` safe
- Preserve the quoting style in YAML files (single quotes around version strings)
- Keep the matrix list sorted in ascending version order
- The `PYTHON_VERSION` / `PythonVersion` / `PYTHON_MINOR` values represent the **minimum** supported version and should only be updated if that version has gone end-of-life
- Do not include pre-release Python versions (status `feature` or `prerelease`) in any updates
- Do not include pre-release Python versions (status `feature` or `prerelease`) in any updates
Loading