You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: two versionchanged:: 1.3.3 directives describe behaviour that shipped long before 1.3.3 #1933
Two directives name a release later than the one that shipped the behaviour they describe:
pcapkit/corekit/infoclass.py:320, versionchanged:: 1.3.3: iterating an instance skips __excluded__.
pcapkit/protocols/data/misc/raw.py:19, versionchanged:: 1.3.3: the Raw constructor takes protocol and error only.
A probe during #1911's directive audit found the first behaviour present continuously since v1.0.0b1, and the second since v0.16.2. Both are identical in v1.3.1.post28 and v1.3.3. The directives came in with #1808 (20323b042) and #1800 (c49e4e3bb). This is an inference from tag contents, so check it against git show <tag>:<path> before editing.
The fix is to date each directive to the release that first shipped the change, as ruled on #1911: a post-release change is marked with its own post-release or the next release, never the parent. If the behaviour predates any directive-worthy change, drop the directive.
Activity
docs: date the __excluded__ and Raw directives to the release that sh…