aio-libs / multidict / 40075347346

86%

master: 86%

push

github

Keep the sdist in the deploy group that makes the Release (#1822)

<!-- Thank you for your contribution! -->

## What do these changes do?

The v7.2.0 deploy, the first with the four-way split from #1768, failed
in all four groups and published nothing. `aio-libs/create-release` in
group 1 reads the version from the sdist in `dist/`, but the byte-order
sort put `multidict-7.2.0.tar.gz` after every wheel, 151st of 151, so it
went to group 3. Group 1 hit `assert tarball_path is not None` and the
other groups timed out waiting for the Release.

The group selection now lists the sdist first, then the wheels in byte
order, so the sdist always lands in group 1. The shares stay disjoint
and deterministic across re-runs. The changelog reference goes into
#1768's entry in the unreleased 7.2.0 section, so the tag can be moved
onto this commit.

## Are there changes in behavior for the user?

No.

## Is it a substantial burden for the maintainers to support this?

No.

## Related issue number

N/A

## Checklist

- [x] I think the code is well written
- [ ] Unit tests for the changes exist N/A, CI-only change
- [ ] Documentation reflects the changes N/A
- [ ] If you provide code modification, please add yourself to
`CONTRIBUTORS.txt` N/A
- [ ] Add a new news fragment into the `CHANGES/` folder N/A, reference
added to the 7.2.0 section of `CHANGES.rst` directly
- [x] `make doc-spelling` passes and any new technical words are added
to `docs/spelling_wordlist.txt`

Drafted with Claude Code (Claude Opus 5.5); reviewed by @asvetlov.

<details>
<summary>Agent run details (optional, for reviewers)</summary>

Failed run:
https://github.com/aio-libs/multidict/actions/runs/39958656139 (group 1
"Make Release": `AssertionError` in `get_releasenote.py`
`analyze_dists`; group 3 log lists `dist/multidict-7.2.0.tar.gz`).
Simulation: the new step script, extracted from the workflow, run
against the 151 file names from that run's logs for each of the four
groups: 38/38/38/37 files... (continued)

842 of 1684 branches covered (50.0%)

Branch coverage included in aggregate %.

9800 of 10709 relevant lines covered (91.51%)

1.83 hits per line