Route legacy OpenAI completion builds through prefixed tags - #9507
Route legacy OpenAI completion builds through prefixed tags#9507yaroslavyaroslav wants to merge 6 commits into
Conversation
|
I don't understand why do it this way. |
|
This PR changes OpenAI completion. Review for OpenAI completion develop-fb34836-2026.08.04.15.26.53Unhandled exception in 'check' routine
OSError: [Errno 39] Directory not empty: '/tmp/pkg-rev-git-nkwbz4hq/.git/objects' 4 warnings:
|
|
This PR changes OpenAI completion. Review for OpenAI completion develop-fb34836-2026.08.04.15.26.53
No failures 4 warnings:
|
|
That's not what I meant. Use prefixed tags for older builds. I don't think the use of branches is recommended anymore. EDIT: Sorry, I actually meant prefixed tags and not a dedicated branch in my previous comment. |
|
This PR changes OpenAI completion. Review for OpenAI completion develop-fb34836-2026.08.04.15.26.53
No failures 4 warnings:
|
What changed
Split OpenAI completion releases by Sublime Text's plugin-host runtime:
py38-The legacy
py38-6.1.0tag points to the existing 6.1.0 release commit (f7ed5211bad22942ed13162e87ac07ede37f5d95).Why
Sublime Text 4205 replaces the Python 3.8 plugin host with Python 3.14. Prefixed tags keep the legacy package line fixed while allowing new releases to retain the normal
6.2.0,6.3.0, … tag format.The release sources do not overlap:
py38-*tagsValidation
uv run pytest -q: 33 passeduv run -m tools.format_package_control_channel repository/o.json --checkrepository/o.jsonwithpython3 -m json.toolpy38-6.1.0to version6.1.0and excludes prefixed tags from the unprefixed source