[JarryShaw]

Please follow the guide below

• You will be asked some questions, please read them carefully and answer honestly

• Put an x into all the boxes [ ] relevant to your pull request (like that [x])

• Use Preview tab to see how your pull request will actually look like

• Searched for similar pull requests

• Followed the coding style (make pylint, make mypy, make isort)

• make test passes, and a test case covers the change. Narrow runs only, listed below.

• Added a changelog entry under docs/source/changelog/ and regenerated CHANGELOG.md, if the change is user-visible: N/A — centralised in docs(changelog): shared 1.5.0 changelog — long-lived, merges last (#610, #616, #617, #618, #620) #657

What is the purpose of your pull request?

Tick the commit type your subject line carries.

• fix — corrects a defect
• feat — adds a feature
• perf — changes performance, not behaviour
• refactor — changes neither behaviour nor performance
• test — tests only
• docs — documentation only
• ci — workflows or build tooling
• release — bumps the version or rolls up a distribution
• chore — anything else

---

• release_status: the steady-state "Nothing to release" notice no longer
  states PyPI and Anaconda totals, which version_check derives from the
  tag's own tier file.
• conda-dist and the release conda leg: drop pip install -e .[all], and
  the release leg's pathlib2 typing_extensions. No later step imports
  pcapkit from setup-python's interpreter, and on macos-26-intel the extras
  pull a cryptography with no Intel wheel.
• Release conda leg: the build step exports host_package, and cron-conda's
  --smoke step runs before anything is uploaded.
• releasing.rst: re-point the create-release.yml citations the new steps
  shifted.
• tests/project: a regression test per issue, each failing without its fix.

Closes #1849
Closes #1854
Closes #1855

[JarryShaw]

Verdict: GOOD TO GO at 5d22e159d. A Sonnet cross-review (author: Opus) read every step after the removed installs in both conda jobs and confirmed:

• None of those steps needs pcapkit from setup-python's interpreter. pip download needs only pip, conda build and the recipe's import test run in conda's environments, and the version comes from job outputs.
• --smoke is stdlib-only on its path; it was run under -I -S with no packaging or pcapkit installed.
• The release smoke step mirrors cron-conda's. host_package is exported where cron does it, and the step sits after the build and before both uploads.
• The four shifted releasing.rst citations hold the same content. Nothing else cites into the shifted region, and TestDocCitationsResolve passes.
• All three new tests fail on main for the intended reasons. test_release_gates and the related workflow tests pass.

Unverified until a real run: the conda legs on macos-26-intel. Optional nit: pep.rst:541 still lists the release workflow among those that install .[all].