[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

---

Description

Part of #1103, the whole-repository prose sweep, for the changelog slice. It follows the #719 rules: prose only, accuracy first, no churn and no timed context.

Entries:

• add 69 entries for merged changes the 1.5.0 file did not cite, most of
  them from fix(ipv6-opts): RPL option 0x23 raises AttributeError in _read_opt_unassigned #1196 on: the round-trip fixes, reassembly, the engines,
  registration, the config module, and the corekit moves
• add a pcapkit.interface section for its new registry helpers
• cover breaking changes the file had missed: AppType.proto,
  TransportProtocol's base, TLSKeyLabel's move, Method.get case, the
  sentinels, the all extra, IPv6_Ext and register_mh_extension

Accuracy:

• the ftp/http case-folding entry notes that Method.get matches case
• the construction-keyword entry says a keyword passed to from_data raises

Preamble:

• re-measure the citation figures and list the 1.5.0b4 to b12 prereleases
• drop the "as of this revision" snapshot wording

Markup:

• un-nest seven inline literals from bold, and close an unterminated literal
• regenerate CHANGELOG.md with util/changelog_md.py

Conventions:

• re-pin process.rst's changelog figures to 10 sections and 269 entries

Checks:

• An AST guard holds on every changed .py file.
• process.rst pin. This PR also re-pins the changelog figures in process.rst (lines 101–111) to the measured 269 entries and 10 sections. The docs PR edits only lines 45 and 320 of that file, so the two merge cleanly.
• tests/project gives 930 passed and 1 skipped, and every test that reads the edited paths passes.
• A merged Sphinx build of all nine slices adds no new warnings.
• A Sonnet cross-review sent this back once. After the fix round, a re-check returned GOOD TO GO.

Not covered here; a round-2 PR follows: about 80 uncited user-visible PRs from before #1195; the stale #759, #1016 and #417 (pycrate) entries; 1.5.0.rst lines 1100–2040 and 2220–2640; and changelog.rst.

Refs #1103

[JarryShaw]

Verdict: GOOD TO GO at 4ad13e42f. A Sonnet cross-review checked it (author: Opus), after one fix round.

• First review, two blocking findings: the all-extra entry said four engines; and process.rst was not re-pinned, which made two tests/project tests fail.
• Re-check: both are fixed.
  • The entry now names the three engines and two crawler packages that 1.4.x all carried, checked against all four 1.4.x tags.
  • process.rst is pinned to the measured 269 entries and 10 sections, and the two tests now pass.
  • CHANGELOG.md is in step with --check.
• Tests: tests/project gives 930 passed.
• Non-blocking: the protocols: implement NGAP over SCTP, decoding aligned PER through pycrate #417 entry says pycrate is excluded from all, but all now includes it; round 2 fixes it.