Skip to content

build: add Python 3.15 classifier to v2 release pipeline - #379

Merged
Gavin Aguiar (gavin-aguiar) merged 1 commit into
devfrom
vrdmr-release-py315-classifier
Nov 16, 2026
Merged

Gavin Aguiar (gavin-aguiar) merged 1 commit into
devfrom
vrdmr-release-py315-classifier

Conversation

@vrdmr

Copy link
Copy Markdown
Member

Summary

  • Add 'Programming Language :: Python :: 3.15' to the V2 pythonClassifiers in eng/ci/library-release.yml.
  • The V2 bump stage (eng/templates/official/release/bump-version.yml) replaces the classifier block in pyproject.toml with this list. 2.4.0 added the 3.15 classifier by hand after the bump in build: update Azure Functions Python Library V2 version to 2.4.0 #377, which is why PyPI 2.4.0 lists 3.13–3.15. Without this change, the next V2 release would drop 3.15 again.
  • V1 classifiers and requires-python values are unchanged.

Validation

  • library-release.yml parses as YAML.
  • I reran the pipeline's requires-python and classifier regex replacement in Python against pyproject.toml from dev and from the 1.26.0 tag:
    • V2: >=3.13, classifiers 3.13, 3.14, 3.15. Running it on dev's pyproject.toml leaves the file unchanged.
    • V1: >=3.10,<3.13, classifiers 3.10, 3.11, 3.12 (unchanged).
  • git diff --check is clean.

Not included

The CI test and build matrices (eng/templates/jobs/ci-tests.yml, eng/templates/jobs/build.yml) still cover 3.10–3.14 only. 3.15 is declared but not tested in CI. That can be a follow-up once 3.15 is available on the build agents.

The v2 release bump rewrites pyproject.toml classifiers from
library-release.yml. 2.4.0 added the 3.15 classifier by hand after the
bump, so the next v2 release would have dropped it again.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@gavin-aguiar
Gavin Aguiar (gavin-aguiar) merged commit 522bc17 into dev Nov 16, 2026
18 checks passed
@gavin-aguiar
Gavin Aguiar (gavin-aguiar) deleted the vrdmr-release-py315-classifier branch November 16, 2026 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants