[sirosen]

For free-threading tests, 3.14t is replaced with 3.15t.

Contributor checklist

• Included tests for the changes.
• A change note is created in changelog.d/ (see changelog.d/README.md
  for instructions) or the PR text says "no changelog needed".

Maintainer checklist

• If no changelog is needed, apply the bot:chronographer:skip label.
• Assign the PR to an existing or new milestone for the target version
  (following Semantic Versioning).

[read-the-docs-community]

Documentation build overview

📚 pip-tools | 🛠️ Build #35202393 | 📁 Comparing 057fa22 against latest (ab9b075)

  🔍 Preview build  

1 file changed

± changelog/index.html

[webknjaz]

I usually add a packaging change note declaring official support, when adding a new trove classifier.

[sirosen]

"Feature" seems to me best for a pure python project, but it's not a strong opinion.
I put it in the merge queue, but if you'd rather I move the fragment to "packaging", let me know and I'll do a tiny PR to fix that. 😁

(I'm merging on the theory that you would probably not have approved right away if you felt strongly about it.)

[webknjaz]

I guess feature's fine too. I just associate changing the core packaging metadata with... packaging, in my mind. Though, it's also because I give a signal to the downstream packagers saying that "yes, we actually test that this is supposed to work upstream officially, not by chance".