by committing the tarballs and recombining history

There are some changes which aren't released yet, for example #1

As pytest-dev/pytest#8274 shows, in that particular example we show two instances which are supposed to be different, however they both end up with the same address which is confusing.

Perhaps regendoc could be more sophisticated here, keeping track of memory addresses used in the code but generating a fixed memory address based on the contents somehow?

leaving them as is is incompatible with the pre commit whitespace fixing in pytest

there are no tags vor v0.6 and v0.6.1 - investigate if its just the tags missing, or actual commits

Currently, regendoc runs all commands from docs that start with $:

In order to workaround this feature, the commands not desired regenerating are prepended with extra charters (such as . or #) in pytest documentation. This works (such lines are not regenerated), however such characters remains in the rendered HTML docs and are visible to the reader.

See pytest-dev/pytest#5153

A better way (invisible to the user) to mark code snippet as skip-regenerating should probably be invented. A rst comment or directive might do.