fix(packaging): declare Python 3.14 and guard the classifiers in CI

3.14 already carries 3.11% of PyPI downloads -- 5.7% back in June -- but had
no classifier, so `pip install dashscope` reported no support for an
interpreter a material slice of users are actually on. Adding the classifier
alone would let the same gap reopen at 3.15, so the unit-test job now also
fails when a version carrying >=1% of downloads is undeclared, when the
declared versions have a hole in them, when the matrix tests something
setup.py does not claim, or when the python_requires floor sits above the
lowest classifier.

The guard lives in tests/unit/test_packaging_metadata.py rather than a
separate script and CI job, so it runs on every pull request with nothing
extra to keep in sync; PyYAML is already in requirements-test.txt. Only one
matrix interpreter queries pypistats, because four parallel requests invite a
429 that would skip the very check it is meant to run, and an unreachable
pypistats degrades to a skip rather than a failure -- a rate limit is not a
packaging defect.

scripts/ holds local PyPI investigation tooling that is deliberately not
shipped, so it is ignored.

Author: agentscope-ai-java

.github/workflows/unit_test.yml

@@ -16,7 +16,7 @@ jobs:
     strategy:
       matrix:
         os: [ ubuntu-latest ]
-        python-version: [ '3.9', '3.12', '3.13' ]
+        python-version: [ '3.9', '3.12', '3.13', '3.14' ]
 
 
     steps:

.gitignore

@@ -138,3 +138,6 @@ cython_debug/
 .pypirc
 
 /.acli/
+
+# Local PyPI investigation tooling; the CI guard lives in tests/unit/.
+/scripts/

dashscope/acli/__init__.py

@@ -3,7 +3,7 @@
 
 import uuid
 
-__version__ = "0.6.6"
+__version__ = "0.6.5"
 
 # Per-process identifier sent as x-dashscope-sdk-session-id so the
 # backend can group multi-turn requests from one CLI run.